NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
tccack
Jan 29, 2012Aspirant
wbadmin, wireless and failures
Hi there... I am having a really frustrating time trying to create a windows complete backup on my NV+. I found out that network drives are not visible to the GUI method of the complete backup in Vi...
quickly_now
Feb 04, 2012Apprentice
Pretty much all backup systems have a common problem: file locking. When a file is open in an application it gets locked, and this means some other application can't open it to read it. In order to make a backup, you need to open the file to read it (and copy it somewhere else).
Windows VSS solves this by making a snapshot of the drive, and you can then copy from this (stable) snapshot. There is all manner of clever magical stuff goes on but the essence of it is that the drive looks like it has become 2 drives: the one which is normally in use, and new one which is a snapshot copy of the one in use, but which is read-only. Of course, there are not actually 2 drives. The snapshot copy is the same drive with some clever software sitting in between which effectively says "while the fake new drive exists the data you want for file X is located at AAAAA", and at the same time the original drive beig updated by some applicaiton is being told "the data you want for that same file X is located at BBBBB".
Windows VSS manages this.
As a rough generalisation, pulling a backup makes it more difficult to use windows VSS. Running backup s/w on the PC means that it can create the windows VSS snapshot, copy files from that snapshot to the back, and release the snapshot when it is done.
[Obligatory disclaimer: my backup s/w does all these things. It runs on the PC and does not rely on the NAS pulling things down from the PC. If you are further interested, check out QuickShadow Backup - there are other postings on this forum which describe it and give the download URL.]
Windows VSS solves this by making a snapshot of the drive, and you can then copy from this (stable) snapshot. There is all manner of clever magical stuff goes on but the essence of it is that the drive looks like it has become 2 drives: the one which is normally in use, and new one which is a snapshot copy of the one in use, but which is read-only. Of course, there are not actually 2 drives. The snapshot copy is the same drive with some clever software sitting in between which effectively says "while the fake new drive exists the data you want for file X is located at AAAAA", and at the same time the original drive beig updated by some applicaiton is being told "the data you want for that same file X is located at BBBBB".
Windows VSS manages this.
As a rough generalisation, pulling a backup makes it more difficult to use windows VSS. Running backup s/w on the PC means that it can create the windows VSS snapshot, copy files from that snapshot to the back, and release the snapshot when it is done.
[Obligatory disclaimer: my backup s/w does all these things. It runs on the PC and does not rely on the NAS pulling things down from the PC. If you are further interested, check out QuickShadow Backup - there are other postings on this forum which describe it and give the download URL.]
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!