|
|
You should have a standby server configured and available in case your primary server fails. To avoid data loss if the primary database server fails, Symantec recommends that you save the bedb.bak file and the Catalogs directory to a separate server after the scheduled daily database maintenance.
To create a standby primary database server
Use BEUtility to add all the SAN servers that will use the new primary SAN SSO server.
Use BEUtility to create a media server group that contains all the servers you added in step 1.
Do not select the Create group from SAN SSO configuration option.
Use BEUtility to promote a new SAN SSO server to primary in the media group you created.
Use BEUtility to stop the Backup Exec services on all media servers in the media server group.
On the media server that you promoted to primary, navigate to \Program Files\Symantec\Backup Exec\Data directory and rename the bedb.bak file to indicate that this is the original file.
originalbedb.bak or bedborg.bak
On the original primary server, navigate to \Program Files\Symantec\Backup Exec\Data directory. Copy the bedb.bak file to the same directory on the new primary server.
If the original primary server is unavailable, locate the latest copy of the bedb.bak file and copy it to the new primary server.
On the media server that you promoted to primary, navigate to \Program Files\Symantec\Backup Exec. Rename the Catalogs directory to indicate that this is the original.
On the original primary server, navigate to \Program Files\Symantec\Backup Exec\. Copy the Catalogs directory to the same directory on the new primary server.
If the original primary server is unavailable, locate the latest copy of the Catalogs directory and copy it to the new primary server.
Use BEUtility to restore the database you copied in step 6. Be sure to select the Drop existing database and reload from backup option.
Use BEUtility to start the Backup Exec services on all the media servers in the media server group.