Unsolved
1 Rookie
•
25 Posts
0
293
December 2nd, 2022 04:00
Cloning a clone job to a DDVE
Hi,
We are looking at decommissioning our old Data Domain appliances and want to moving our yearly backups to a single DDVE.
Currently we have two sites, each with a NetWorker server and a Data Domain. We backup locally to the Data Domain and then using Networker CCR the backups are cloned to the other site.
Our plan is to deploy a new DDVE on Site1 and create NW clone jobs to clone the yearly backups from site1 DD to the DDVE.
Can we also use Networker in Site1 to clone Site2's clone jobs from Site1 DD to the DDVE and recover them locally in Site1?
Also, if we were to use Data Domain replication to replicate the storage units from Site1 DD to the DDVE will the clone jobs from Site2 be recoverable?
We are trying to avoid adding any additional load onto our Site to Site link as it is already maxed out with production replication traffic.
Any advice will be apricated.
Thanks,
D
bingo.1
2.4K Posts
0
December 4th, 2022 02:00
Of course you can clone a (cloned) save set to the same or any other location within the same data zone (the same NW server).
If we talk about multiple data zones, you must first scan 'foreign' media to add it to the media index.
You may either use standard clone or CCR jobs but you may also consider to use the NW volume move utility which is available since some months.
barry_beckers
393 Posts
0
December 5th, 2022 05:00
wouldn't it have been easier to have just one NW server (maybe with a NW storage node on each location, just in case a client would not be able to use nor support NW client direct to directly write to a DD, for example when the NW client version cannot be upgraded to a version that is supported by the DDOS version), that has DD"s in both locations instead of two?
Using scanner to be able to make available data from another NW server is possible, however depending on the amount of data involved, that can take some time. Also clients of the other NW server will need to be defined on the NW server scanning in the data to be able to restore.
If you have just one NW server, then all data would be available. In case you'd have some virtualization going on, between the tow sites, then you could have a high available VM, that could even vmotion between the sites. Or have a 2nd system standby that you can restore the most current NW bootstrap backup unto. The sky is the limit.
Years ago we had also two NW servers in a dual data center approach. We deemed it not to be that handy, as for example some customers would have systems in both locations that would need to restore form each other, hence such clients needed to be defined in both NW servers. Combined with tape at the time, that was far from helpful as only one NW server can control the backup devices if a client is to act as a NW storage node. So we got rid of one of the two nw servers, and would have the nw server handle clients in both sites and also be fully in control of any cloning occurring.
So no scanning of NW data required if and when using no mtree replication. So data was available directly through just one backup server instead of two. For us that was possible as it is a high bandwidth between location not very far from each other. Later on we migrated from physical to virtualized NW server approach, making it even easier to assure that the NW server became high available, with replicated storage between both locations.
When required you can throttle the bandwidth to be used by the DD's for the replication occurring between them, if bandwidth is of an issue. You can use days and times with different throttles even.