• State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 9193 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Best Practice for site A Fail Back after DR Excersize at Site B with Virtual Standbys

jtrevino
over 7 years ago

Hello,

 

...looking for the best way to do this. Here is the setup (MS Paint still rules!)

 

For the failback operation, we do not want, nor will we have the time to create a seed and ship it back down to Site A. Only ~35GB will have changed and it is a SQL database, files and folders changed, and IIS website data changing.

 

Is there a way to fail back to the Site A source and not have to restore all 500GB? Only 35GB has changed so this could be restored overnight if there is an efficient way. These sites are across the country from each other.

Site A source is currently physical but could be changed to Virtual if needed.

 

*SiteA and SiteB are DL4000 Appliances running 6.1

Parents
  • +1 over 7 years ago
    It is possible to reverse the replication path and replicate the data back to the source core. It takes some manual work but we have a KB for that - support.software.dell.com/.../195296. This would allow you to replicate the data back to the source core. However, there is no way to incrementally update the original production server that was backed up and has now been out of use for 3 days. So you have to do a complete virtual standby of that server to get an up to date copy of it at Site A, then go through the failover process again to get back to the production site. If the original protected agent is physical, then you have to do a BMR (unless you are only restoring a data volume in which case you can just do a rollback). But either way you have to restore the original machine in order to update it with the data that was changed while it was running at Site B.
Reply
  • +1 over 7 years ago
    It is possible to reverse the replication path and replicate the data back to the source core. It takes some manual work but we have a KB for that - support.software.dell.com/.../195296. This would allow you to replicate the data back to the source core. However, there is no way to incrementally update the original production server that was backed up and has now been out of use for 3 days. So you have to do a complete virtual standby of that server to get an up to date copy of it at Site A, then go through the failover process again to get back to the production site. If the original protected agent is physical, then you have to do a BMR (unless you are only restoring a data volume in which case you can just do a rollback). But either way you have to restore the original machine in order to update it with the data that was changed while it was running at Site B.
Children
No Data