1) Cloning the existing virtual machine that is used for production
2) Attempting to do a backup and restore using the built in GA utilities.
Both methods offered little success. The hostname, IP address are different for the DR environment. We have licensed the DR instances completely and would like to have them as a warm standby and always available.
One final requirement is that we would like to automate this sync process on a daily or weekly basis.
There is really only 2 ways to maintain this Sync'd status.
1- Externalize your database. If you externalize your database, then both the Prod and D/R box will use the same data during Production and/or Disaster Recovery Use. Thus, allowing you to maintain the same status for each user on each system. This would be easier using Data Replication for the database used between the Production site and the D/R site, but it's not mandatory. The key here is that only 1 GAService can be active at a time, otherwise ... database integrity could be compromised.
2- On a nightly basis, after internal database backup, you could FTP/Copy the latest zip file from your Production System to your D/R system and have the Database Replaced on the D/R system. This means that if your system needs to be switched to the D/R Server, it would be as of the last restore not as of last use change.
A cluster license would allow you to handle this situation easily, but keep in mind ... a DBA is needed for any of your External Database maintenance and replication.
Some planning is necessary, but the end result is very obtainable.
Lead Solutions Consultant
In terms of the solution, I know exactly where the backup zip file is, but I don't know how to restore it. Would I have to use "Switch Database"? I tried to read the man page but I didn't see where you would point at that zip file. Also, would there be a way to automate such a restore or is it all interactive using the GUI? Thanks!
No "switch database" is needed.
You will have a Zip file available to you from the Internal (scheduled) backup. Same folder as the Database, but ... in the /Backups Folder.
It's just like restoring a Zipfile that you made for any other backup. Check the Zipfile for the data and compare it to what you have in Production. Then, when you get ready to restore on your D/R Server, remove the same folder (ie, the GoAnywhere Derby Database) and restore the one from the Zipfile into it's place.
Just make sure the D/R GoAnywhere Service is inactive!
I just got through training your people on utilizing GoAnywhere Director ... Yes, it can be automated!
Go forth and Script!! Make me proud!! :)
Lead Solutions Consultant
We have had great success with Mimix. You might want to contact Vision solutions (or one of their competitors) and discuss their replication products to see what would fit your particular needs. We replicate our entire GoAnywhere Director product with Mimix to our DR system.
We don't have GoAnywhere active on the DR system normally. But so far every time I've brought it up on the DR system for a test, it works perfectly. We use the Derby database. And when we upgrade GoAnywhere on production, the upgrade is sent to the DR system without any effort at all
Bear in mind that setting the product in the beginning is complex, and the products can be pricey. But once it's done you have everything you need being sent over in real time. So if you lose your main data center unexpectedly you'll have everything you need to recover. You can also configure for other software and databases to be replicated as well.
howto-services-director-ha-config-for-l ... ensuse-477
Can someone at Linoma who knows the GA/MFT folder paths take out the 15 minutes to write up something that just says copy these files/folders and don't copy these files/folders? That will give us the safety of replication while avoiding the chances we would do something to mess up GA/MFT.
Whatever can be done will be deeply appreciated. Thanks.