How do I replace an existing or a failed publisher database server or co-resident server?
Tip When you perform a server replacement, you must always manually enter the IP information, computer name, and other configuration data exactly as it was on the original server. Before you begin, locate the configuration information for this server. When one server is configured to replace an existing or failed server, the new server uses the IP information and computer name of the original server. To replace an existing or failed server, use the following guidelines: 1. Install the operating system and the software as if it were a new installation. 2. Upgrade the application to the version of the backup that you want to restore. 3. Restore the backup data to the new server. To restore the data, you must have backup data stored on tape or on a network directory, not on the local directory of the existing or failed server. 4. Verify that the data was restored to the new server. 5. See the “What post-restoration tasks should I perform?” section. Obtaining Documentation These sections e
Related Questions
- Where are the GUIguide program files and database stored on my server? How do I take a backup of our existing database before upgrading to a newer release?
- I see that WebSecure Backup uses the SQLite database. Can I replace the SQLite database in my backup server with PostgreSQL, MySQL or MS-SQL Server etc?
- I see that StoreGrid uses the MySQL database. Can I replace the MySQL database in my backup server with PostgreSQL or MS-SQL Server etc?