We're here to help!

A customer wants to move an existing Dbvisit Standby configuration from Windows 2012 to Windows 2016. He has successfully migrated both primary and standby databases to the new hosts. What are the steps involved to move the Dbvisit Standby configuration files?

Below assumptions are taken into consideration in this procedure:

• Primary and standby databases have been successfully migrated from Windows 2012 to Windows 2016.
• The hostnames and IP addresses of the new hosts are kept the same as it was in the old hosts.
• Oracle versions installed and OS versions of both new hosts are identical.
• ORACLE_HOME, ORACLE_HOME_DR, DBVISIT_BASE, DBVISIT_BASE_DR, ARCHDEST, ARCHSOURCE to be used in the new hosts are kept the same.

1. In the new primary and standby hosts (Win 2016), make sure that hostnames will resolve to correct IP addresses. Check that hosts file (i.e. C:\Windows\System32\drivers\etc\hosts) contains correct entries for primary and standby.
2. Install dbvisit standby software (please make sure to use the latest version from our website) on the new primary and standby hosts. Dbvisit services - dbvnet, dbvagent, dbvserver will automatically be restarted. Make sure that the user account that will be used to install meets the criteria as described here.
3. Perform connectivity tests as described here. This is to make sure that any issues related to network has been isolated at this step prior to proceeding any further.
4. If step3 is successful, do the following on the new primary (Win2016). Note that the assumption here is that you are keeping everything the same DBVISIT_BASE, ORACLE_HOME, ARCHDEST, ARCHSOURCE. But just in case you are pointing to new directories in the new hosts, please make sure that you update these parameters (DBVISIT_BASE, DBVISIT_BASE_DR, ORACLE_HOME, ORACLE_HOME_DR, ARCHDEST, ARCHSOURCE) in the DDC file prior to running Dbvisit.
• Stop dbvnet, dbvagent
• Backup current dbvagent.db in Win2016 (simply rename to dbvagent_bkp.db) - this is usually located in C:\Program Files\Dbvisit\dbvagent\conf\
• Copy dbvagent.db from old primary (Win 2012) to new primary (Win 2016)
• Copy <DDC>.db from old primary (Win 2012) to new primary (Win 2016) - this is usually located in C:\Program Files\Dbvisit\standby\conf\
• Copy DDC file (dbv_<DDC>.env) from old primary (Win 2012) to new primary (Win 2016) - this is usually located in C:\Program Files\Dbvisit\standby\conf\
• Start dbvnet, dbvagent
5. Do the following on new standby (Win2016):
• Stop dbvnet, dbvagent, dbvserver (if GUI is installed here)
• Backup current dbvagent.db in new standby Win2016 (simply rename to dbvagent_bkp.db) - this is usually located in C:\Program Files\Dbvisit\dbvagent\conf\
• Copy dbvagent.db from old standby (Win 2012) to new standby (Win 2016)
• Copy <DDC>.db from old standby (Win 2012) to new standby (Win 2016) - this is usually located in C:\Program Files\Dbvisit\standby\conf\
• Copy DDC file (dbv_<DDC>.env) from old standby (Win 2012) to new standby (Win 2016) - this is usually located in C:\Program Files\Dbvisit\standby\conf\
• Backup current dbvserver.db in new standby Win2016 (simply rename to dbvserver_bkp.db) - this is usually located in C:\Program Files\Dbvisit\dbvserver\conf\
• Copy dbvserver.db from old standby (Win 2012) to new standby (Win 2016)
• Start dbvnet, dbvagent, dbvserver

NOTE: The whole reason for copying the sqlite database files (.db) is to keep the historical data of the existing configuration. It's quite tedious but this should give you the exact copy - i.e. when you start the GUI, you need not add the hosts again in the Manage Hosts as dbvagent.db is copied over. You will also see the history of the tasks in the GUI since dbvserver.db is copied over. Otherwise, if these are not relevant to you, you can always start from clean slate - i.e. you would need to add the hosts again, and import the DDC from GUI once the file is copied.

6. Access the GUI and review the following:

• Manage Hosts - both new primary and standby hosts should be present
• Manage Configurations - DDC should exists
• You should also see previous tasks in the "Active Tasks List"
• Manually transfer and apply logs - see if it works
• If everything works well, please enable Dbvisit daemons to schedule transfer and apply of logs automatically.

NOTE: We strongly recommend to test the above steps to see if it works before making the new hosts live.