Restore domain controller from Simplivity backup into Test network

[jfer2022]

Hello,

Looking to restore simplivity backup into segregated network for a test environment. Will keep naming the same but will change IP addres range and it will be walled off from everything. I don't see why I shouldn't be able to restore a DC like this and just sieze rolls if needed and do a little cleanup in sites and services for DC's that are not in that test network. Get things cleaned up and see if things work.  Does this sound unreasonable? We are a smaller business so no worries about getting exact timing of information when restoring.  

Can someone please shed any light on this? we use Vmware  7.0.3 and I think simplivity is almost at the latest version. 

Thank you!

[support_s]

System recommended content:

1. HPE SimpliVity - File Level Restore Returns "Failed to get the partition list."

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[jfer2022]

Hello,

This doesn't really answer my question. I have restored VM's before and haven't had an issue. Why would restoring a Domain controller be so much different? I will wait for another answer as this doesn't really explain anything. 

[Sanika]

Hi  jfer2022,

When restoring an HPE SimpliVity backup, the following three options are available to you:

1. Create a new virtual machine or VM template from a backup - In this option, the original Virtual Machine will not be touched and instead, a new Virtual Machine will be created.

2. Replace a virtual machine or VM template with a backup - This is called in-place backup when the current VM is powered off and deleted and the backup of the VM is restored in its place.

3. Restore files from a backup - In this option, one or more files or folders from a backup of a virtual machine can be restored to the same or a different virtual machine.

All these features will be supported for Domain Controllers (DC) as well.

The process to restore the VM can be found in the below link:
https://support.hpe.com/hpesc/public/docDisplay?docId=sf000046042en_us&docLocale=en_US&page=index.html

Looking at the query, it seems like you are trying to restore a backup of DC to a new VM/existing VM. Both of this should work when you just look at it as a VM-level restore.

However, the functionality of a Domain Controller after restore depends on multiple factors which I think HPE doesn't provide support on as it is a Microsoft tool.

I have pulled few documents which relate to a similar scenario which could be helpful.

https://learn.microsoft.com/en-us/answers/questions/163550/active-directory-domain-split-and-clone-after-comp
https://www.reddit.com/r/sysadmin/comments/136m4mw/help_with_domain_controller_clone/
https://learn.microsoft.com/en-us/answers/questions/281480/problems-joining-a-domain-on-another-subnet

Hope you find it useful.

Regards,
Sanika.

If you feel this was helpful, please click the KUDOS thumb below. Also consider marking this as an "Accepted Solution", if the post has helped to solve your issue.

[gustenar]

Hello @jfer2022,

The restore of the VM will happen on one of the datastores available in your federation. Are you experiencing any problems with the reconfiguration of the VM? Please provide more details of your current configuration and what you are planning on doing. 

[jfer2022]

@Sanika   Thank you for the reply as this aligns with my thoughts. I was generally just looking at this from a simplivity restore to a new VM standpoint. There are actions I will take as the MS side of things for this require different things which is not a worry.  Mainly was just curious if doing this on a DC will work just like any other VM for simplivity restore.  Also, was curious when you would choose to "Clone" vs using a simplivity backup of the machine? Seems they do the same thing from what I can tell as the clone is the same as simplivity backup. The only difference is that in doing my particular restore from simplivity is that I wanted to restore it in a different location so not in the same location. When I backed up the vm I chose a different datastore remote vs the local datastore. This would have been the only difference. 

Are my notes correct? if so, I think we are good. 

Thank you!

[Sanika]

Hello @jfer2022 ,

Whatever you have mentioned is correct in my opinion and seems like we're on the right track.

If you have no further query and you are satisfied with the solution provided, then kindly mark the topic as "Solved" so that it is helpful for all community members.

Regards,
Sanika.

Consider marking the solution as an "Accepted Solution", if it has helped to solve your issue.

[jfer2022]

@Sanika One last question to make sure i'm not overthinking this. Once I restore a VM from simplivity backup and do a "New VM" from it and give it a different VMware Name. On the Simplivity end it is 2 different VM's correct? They aren't related in any fashion after that.  This would be the only thing that I am questioning and again maybe i'm just overthinking it. 

Thank you for any clarification. Just want to make sure the VM I restore from a backup is going to be completely unrelated since both VM's will be up but in different environments using a simplivity restore of the original so vmx file is the same but vmware name and path is different.