Symantec Critical System Manuel D’Utilisation
102 Migrating to the latest version
Migrating legacy installations of Symantec Critical System Protection
When migrating legacy installations for Symantec Critical System Protection,
you should note the following:
you should note the following:
■
If you upgrade the management server, then you must also upgrade the
management console to the same version, and vice versa. The management
server and management console must be the same version.
management console to the same version, and vice versa. The management
server and management console must be the same version.
■
Upgrading the agent is optional; you can use agent 5.0.0, agent 5.0.1, agent
5.0.5, or agent 5.1 with the latest version of the management server and
management console. However, if you upgrade the agent to the latest
version, then you must also upgrade the management server and
management console.
5.0.5, or agent 5.1 with the latest version of the management server and
management console. However, if you upgrade the agent to the latest
version, then you must also upgrade the management server and
management console.
■
To use simple failover, you must upgrade the management server,
management console, and agent to version 5.1.1 or higher.
After upgrading, you use the agent config tool to specify the alternate
management servers for the agent.
See
management console, and agent to version 5.1.1 or higher.
After upgrading, you use the agent config tool to specify the alternate
management servers for the agent.
See
■
You cannot upgrade Symantec Critical System Protection 4.5. You must
uninstall the Symantec Critical System Protection 4.5 software (server,
console, and agent) and then install the latest version.
uninstall the Symantec Critical System Protection 4.5 software (server,
console, and agent) and then install the latest version.
Software migration is straightforward. When you install the Symantec Critical
System Protection software (server, console, and agent), the installation kit
automatically detects legacy installations and migrates the Symantec Critical
System Protection software to the latest version.
System Protection software (server, console, and agent), the installation kit
automatically detects legacy installations and migrates the Symantec Critical
System Protection software to the latest version.
Providing scspdba password during management server upgrade
During a management server upgrade, you are asked for the password to the
scspdba account. If you chose the Evaluation installation when you initially
installed the management server, the scspdba password is the same as the sa
account password that you specified during the installation. Enter that same
password during the upgrade. If you chose the Production installation, you
entered the password for this account (the Database Owner account) during the
initial installation of the management server. Enter that same password during
the upgrade.
scspdba account. If you chose the Evaluation installation when you initially
installed the management server, the scspdba password is the same as the sa
account password that you specified during the installation. Enter that same
password during the upgrade. If you chose the Production installation, you
entered the password for this account (the Database Owner account) during the
initial installation of the management server. Enter that same password during
the upgrade.
If you do not remember the scspdba password, you should change it in the
database using SQL Server tools. This account is used strictly for upgrading the
software; it is not used operationally by the management server. So changing
the password in the database is safe—there is no corresponding change needed
for the management server.
database using SQL Server tools. This account is used strictly for upgrading the
software; it is not used operationally by the management server. So changing
the password in the database is safe—there is no corresponding change needed
for the management server.