1 Rookie
•
8 Posts
0
2485
November 21st, 2019 14:00
Recover old backup data from Data Domain to a new Networker Server
Hi, this is a continuation from a previous post because I want to check all my options.
Can I build a new Networker 8.2 server and scan an old Data Domain full of old backups and recover that data in a stand-alone environment? So I will not be transferring any NSR logs, files or databases. The data on the old data domain is still recoverable and browsable.
How can I accomplish this?
Thanks in advance!
No Events found!
tccicraic
1 Rookie
•
8 Posts
0
December 16th, 2019 12:00
This is resolved!
Thanks for all the suggestions. We figured out that in the node properties, under devices, under status the storage node was not enabled.
bingo.1
2.4K Posts
0
November 21st, 2019 23:00
Sure.
If you have the correct parameters (device name & access information as well as the appropriate user name and password) you can add the device to a NW server/storage node and scan the media. I just wonder why you want to setup an old NW 8.2 server for that purpose - just connect it to the new system.
However, a duplicate volume name could be a problem. Years ago, NW had no problem because it really used the volid which most likely is unique. But I tested this some years ago and vaguely remember that a duplicate vol name in fact caused an issue. I do not know whether this has been fixed in the meantime.
And please - be extremely careful - in mounting the volume later. Do not accidentally label it!
tccicraic
1 Rookie
•
8 Posts
0
November 22nd, 2019 08:00
Thanks for the info.
I read that that latest versions of Networker are not backwards compatible. I took that to mean that I cannot build a new NW server 18 or 19 and scan old NW 8 data.
Is that not true?
Are there any references on scanning the media? Step-by-step references?
crazyrov
4 Operator
•
1.3K Posts
0
November 22nd, 2019 19:00
@tccicraic, The backward compatibility is regarding the architecture of NetWorker and not about the data that has been backed up. Here is one of the community discussions regarding "scanner" command that is used to scan back the data from a device(if not overwritten or relabeled) - https://www.dell.com/community/NetWorker/Using-scanner-command/td-p/6968045
bingo.1
2.4K Posts
0
November 23rd, 2019 00:00
Actually, there is no such specific document because the procedure did not change since the very beginning.
If you need to test the general procedure, here is a small (12 MB) but very old backup which has been created about 20 years ago (with NetWorker 4.2.0): ftp://ftp.legato.com/pub/NetWorker/German/ultra_420.zip
Setup your NW (eval) server as follows:
- Create a fake entry in your hosts table for a client called 'ultra'
- Create an new directory on your NW server and unzip the files in this directory
- Create a 'file' type device using this directory. Use either nsradmin or the 'new device properties' GUI. The wizard will not work as it does not know this old device type any longer
- Run 'scanner -m device_name' to verify that the media can be read. If necessary, create the necessary pool.
- Run 'scanner -m device_name' to re-read the save set and re-polulate the index information.
In case you need anything else, let us know.
bingo.1
2.4K Posts
0
November 24th, 2019 12:00
I must slightly correct my procedure. Here are the new instructions:
Setup your NW (eval) server as follows:
- Create a fake entry in your hosts table for a client called 'ultra'
- Create the client ultra but disable the option 'scheduled backup'. As it does not exist, it cannot be backed up.
- Create an new directory on your NW server and unzip the files in this directory
- Create an 'optical' type device pointing to the file ...\your_directory\bu_dev1. Use either nsradmin or the 'new device properties' GUI. The wizard will not work as it does not know this old device type any longer.
- Run 'scanner -m device_name' to verify that the media can be read. If necessary, create the necessary pool.
- Run 'scanner -i device_name' to re-read the save set and re-polulate the index information.
In case you need anything else, let us know.