Unsolved
This post is more than 5 years old
1 Rookie
•
1 Message
0
675
November 1st, 2018 22:00
Datadomain Networker DR site
Hello,
Need some help on setting up and testing a DR site
our architecture :
ton he primary site DD4500 (datadomain1) with Networker 8.2 on redhat using VTL and DDboost.
on the DR site DD4500 (datadomain2), we installed a Networker server with the same Hardware/OS/Networker version.
on the DR site the networker server didnt commmunicate with datadomain1 and all other the networker clients.
For the replication we used datadomain (mtree) replication for the VTL.
and for DDboost we used CCR for some data Volumes.
The networker index and bootstrap are saved to a separate index pool we also CCR cloned this pool to the DR datadomain.
Now on the DR datadomain we create a VTL using the replicated mtree, we import all media (RO), the replication are kept active.
on the DR networker we created VTL and configured the datadomain replicated data volume and also the index volume.
The first time when we run the nsdr command we succeed to load the entire configuration using the index volume, we answer NO when the program ask to load the index for all clients. After we just load the indexes of only two clients (X2,X3) just for Test with (nsdr -I ).
we didnt broke any replication task from primary to secondary site.
Now we are facing some trouble :
1- when networker on DR load a VTL media (which is an activ replicated mtree) it take more time to load and verify label.
here the first question, for using the VTL on DR just for restore we have to broke the replication or not ?
2- we try to restore a database on an alternate client X1 on DR site we didnt suceed to restore the contol file.
The client on DR site X1 is already configured on the primary site, now when we try to modify some property whe got this message :Failed to open lockbox /nsr/lockbox/ /clb.lb.
we didnt restore the index file for this client X1, is it necessary to do it for restoring a database from X2 ?
when we test a recover on the X1 client (recover -c X1 -R X2), we got a message regarding X2 index, how we can verify the index of X2 on the server ?
3- we try an other index restore with (nsdr -I X2), networker try to use a volume index from datadomain1 wich is not reachable .
how can we restore X2 index ?
thanks for your help
0 events found

