We are moving a Vault subscriber server from one location to another across a state. The server will be used for Vault, but for a entirely new group/ Where can I find the best practice information on how to do this "cleanly"
Solved! Go to Solution.
In reality the best approach here will be to rebuild the subscriber (SQL and Vault setup), if you are changing domains you will encounter a raft of security issues to overcome with SQL etc.
I would suggest taking a copy of the filestore so this does not need to be replicated of course (you can simply copy this into place and replication will manage the differentials)
We found out that the "move" is now 8 blocks, not 80 miles. Since the domain and the Server name are to remain the same, is there any Vault Administration procedure that needs to take place?
If you are just physically moving the machine (not changing hardware, machine name, domain, etc) then there shouldn't be any impact here. It sounds like the moral equivalent of a shutdown / restart of the machine.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.