This post is more than 5 years old
11 Posts
0
1633
June 28th, 2015 09:00
Recover Networker from Data Domain collection replication
Hi,
In order to get more restore performance from a Data Domain system Support has recommended that we add more disk shelves to the system. They also say we need to destroy the filesystem in the process so that the data will be reallocated on all the drives. I saw in the Networker documentation that it does not support moving data to another Data Domain system using Collection Replication, but is it possible to recover the collection replicated data back to the same Data Domain system, and for networker to recognize that data as it's own? The reason is because Collection Replication is by far the most efficient way of replicating a very large amount of data. about 1PB. I do not want to risk losing the backup data.
Here is what I think would be needed to accomplish this. Please let me know if this will work.
1. Sync Collection Replication between the two Data Domains.
2. Unmount the volumes in Networker.
3. disable the replication pair to stop replication.
4. Destory the Filesystem on the source.
5. Create a filesystem on the source with all the new drives, but do not enable the filesystem.
6. Perform a recovery from the Data Domain Replication pair to sync the data back to the source.
7. Mount the devices in Networker.
crazyrov
4 Operator
•
1.3K Posts
0
June 28th, 2015 22:00
Hello danger-6IDmh,
when they say Collection replication is not supported in NetWorker, it does not mean that you cannot use the replicated data to restore information using NetWorker, what they actually mean is that NetWorker is not by default aware that the data is being copied over to the other DD via Collection replication. You can always configure the the 2nd DD in NetWorker with the correct "Device access information" to get the replicated data available to NetWorker.
If you plan is to use the original DD itself after the addition of shelves then i would suggest you go ahead with the plan that you already put forth in your post.
crazyrov
4 Operator
•
1.3K Posts
2
June 28th, 2015 23:00
You could copy the device access information from the original device and just change the name of the DD, all this can be found on the 2nd Tab of device properties when creating a new wizard (try not to use the wizard).
eg : If the access information for the device on the primary server was -DD1:/Folder1/Folder2, you can create the new device with access information as DD2:/Folder1/Folder2. remember you just need to mount it and do not label it.
danger-6IDmh
11 Posts
0
June 28th, 2015 23:00
Thanks for your answer. I will go ahead with the plan.
Is there a procedure for configuring the 2nd DD in Networker with the correct Device access information? That would be very useful for developing a DR plan.
danger-6IDmh
11 Posts
0
July 1st, 2015 10:00
My plan worked perfectly.
Although, There were two additonal steps after recovery finished. I needed to enable ddboost and also run this command in the Data Domain CLI to get the storage units to come up.
ddboost storage-unit modify user
Its a good idea to take a note of the storage unit names before you destroy the file system since they are not visible after the restore.