Just the creation of a device will not touch the media at all. NW will only delete the contents if you (re-)label the volume. NEVER do this if you want to scan/recover later.
Also make sure that you set the retention period for the client(s) long enough. Otherwise NW will scan the save set but later see that it has passed the retention date and delete it during its internal cleanup processes. So you better set the media write protected or the device to read only.
To recover backups from an obsolete client, you can also add the hostname as a fake entry in the hosts file. Then just run a 'directed recovery' to restore the files to the new machine.
Thank you! I am able to do a directed restore and that is working now. I think you are correct, I might have labeled the adv_file and that was the cause for the mass delete. At least I have something now that is working.
bingo.1
2.4K Posts
0
September 23rd, 2020 14:00
Just the creation of a device will not touch the media at all. NW will only delete the contents if you (re-)label the volume. NEVER do this if you want to scan/recover later.
Also make sure that you set the retention period for the client(s) long enough. Otherwise NW will scan the save set but later see that it has passed the retention date and delete it during its internal cleanup processes. So you better set the media write protected or the device to read only.
To recover backups from an obsolete client, you can also add the hostname as a fake entry in the hosts file. Then just run a 'directed recovery' to restore the files to the new machine.
ThomasL66
2 Posts
0
September 23rd, 2020 15:00
Thank you! I am able to do a directed restore and that is working now. I think you are correct, I might have labeled the adv_file and that was the cause for the mass delete. At least I have something now that is working.