How can I migrate EPM DB's to a different SQL instance? (for the purpose of SQL upgrade, SQL machine change, or otherwise)
Steps
Use the following steps-
1. Backup all DB's
- This can be done using the built in Backup Tool in the Administration page
Administration > Configuration > Backup Settings >
- Or manually for all DB"s that begin with VF
In 5.+ that means - VFSTAGEDB5, VFMNGDB5, VFNESTDB5, VFSTATDB5, VFEVENTSDB5
2. Restore in new location/SQL instance and
run revive scriptPlease refer to
How to restore EPM database from backup3. Afterwards perform an Uninstall and Reinstall of the Manager from the IIS Machine.
During the reinstall, point the installation at the restored DB's in the "new" location. (Note it is critical that the IIS FQDN is the same as was used before)
When the "reinstall" or "upgrade install" happens with the installer, it will validate all user access and permissions, as well as update the connection points needed in the DB.
But if you are looking to validate afterwards, the connection strings can all be seen in the following 2 tables-
a. Expand VFMNGDB5 > find table called DBO.tblSetConfigs
b. Expand VFMNGDB5 > find table called vfdsp.tblManagerConnectionPoints
Note - We do not advise making any manual changes to these tables without consulting CyberArk.
Note2 - When you reinstall *it is crucial that the FQDN of the server stay the same.*
Note 3 - If upgrading SQL or changing the Reporting Services instance as well - make sure that the User Accounts for MS SQL Database and Reporting Services are given the "sysadmin" Server Role. This is only temporary and once the installation is completed, the user account will only need “db_owner” and “db_backupoperator” roles. The Reporting Services Account also requires local Administrator privileges.
Q:
How can I migrate EPM DB's to a different SQL instance? (for the purpose of SQL upgrade, SQL machine change, or otherwise)
A:
Use the following steps-
1. Backup all DB's
- This can be done using the built in Backup Tool in the vfadmin/Administration page
Administration > Configuration > Backup Settings >
- Or manually for all DB"s that begin with VF
In 5.+ that means - VFSTAGEDB5, VFMNGDB5, VFNESTDB5, VFSTATDB5, VFEVENTSDB5
2. Restore in new location/SQL instance and run revive script
3. Afterwards perform an Uninstall and Reinstall of the Manager from the IIS Machine.
During the reinstall, point the installation at the restored DB's in the "new" location. (Note it is critical that the IIS FQDN is the same as was used before)
When the "reinstall" or "upgrade install" happens with the installer, it will validate all user access and permissions, as well as update the connection points needed in the DB.
But if you are looking to validate afterwards, the connection strings can all be seen in the following 2 tables-
a. Expand VFMNGDB5 > find table called DBO.tblSetConfigs
b. Expand VFMNGDB5 > find table called vfdsp.tblManagerConnectionPoints
Note - We do not advise making any manual changes to these tables without consulting CyberArk.
Note2 - When you reinstall *it is crucial that the FQDN of the server stay the same.*
Note 3 - If upgrading SQL or changing the Reporting Services instance as well - make sure that the User Accounts for MS SQL Database and Reporting Services are given the "sysadmin" Server Role. This is only temporary and once the installation is completed, the user account will only need “db_owner” and “db_backupoperator” roles. The Reporting Services Account also requires local Administrator privileges.