The following procedure helps ensure that the member servers in a Arcserve Backup domain can communicate with the primary server after you change the computer name of the member server.
You must change the computer name of the member server before you complete this procedure.
To change the computer name of a member server
Note: Do not open the Manager Console or log in to Arcserve Backup.
%ARCSERVE_HOME%
Execute the following commands, to stop and start all Arcserve services:
cstop cstart
All Arcserve services stop and restart.
Note: Various Arcserve Backup services will not start after the cstart command completes. This is expected behavior that will not adversely affect this procedure.
Do not close the Windows Command Line.
The Server Configuration Wizard opens and the Select Options dialog appears.
The Add to Another Arcserve Backup Domain dialog opens.
The System Account dialog opens.
Click Next.
Note: At this time, a pop-up message may appear to inform you that various Arcserve Backup services will not start. This is expected behavior that will not adversely affect this procedure.
The Arcserve Backup Data Migration dialog opens.
The Migrate Server Data Dialog opens.
The Complete dialog opens after the data migration process starts and completes.
Note: At this time, jobs do not transfer to the new member server. Continue to the next step to transfer the jobs to the new member server.
Locate a job associated with the old member server.
Right-click the job and click Modify Job on the pop-up menu.
From the Backup Manager, click the Destination tab.
Specify the new member server as the destination for the job.
Submit the job with a Hold status.
Close the Backup Manager.
Note: You cannot modify and transfer jobs if the source data for the jobs reside on the old member server. As such, you must delete jobs with this configuration and then re-create them on the new member server.
bab -cahost <primary server> -removehost <invalid member server>
Example: The following syntax describes a primary server named A, and an invalid member server named B.
bab -cahost A -removehost B
Note: If your Arcserve Backup implementation contains more that one invalid member server, repeat this step (b) for each member server.
(Optional) Open Microsoft SQL Server Management Studio and open to the Arcserve Backup database instance using Windows authentication.
For example, the path to a Microsoft SQL Server Express Edition database is as follows:
<server name>\ARCServe_DB
osql -S <server_name[\instance_name]> -E -d asdb -Q "delete from ashost where rhostname = '<member server name>'"
Example: The following syntax describes a Arcserve Backup database named asdb and the database requires Windows authentication:
osql -S A -E -d asdb -Q "delete from ashost where rhostname = 'B' "
osql -S <server_name[\instance_name]> -U <login_user> -d asdb -Q "delete from ashost where rhostname = '<member server name>'"
Example: The following syntax describes a Arcserve Backup database named asdb, an invalid member server named B, a Microsoft SQL Server user name sa, and a password 123.
osql -S A -U sa -d asdb -Q "delete from ashost where rhostname = 'B' " password: 123
Note: If your Arcserve Backup implementation contains more than one invalid member server, repeat this step (c) for each member server.
If you can view the details for the instance, the database is functioning properly. Close Microsoft SQL Server Management Studio and continue to the next step.
If Microsoft SQL Server Management Studio displays pop-up messages, the database instance is not functioning properly. You must try to resolve the problems indicated on the pop-up messages and then verify the status of the Arcserve Backup database.
If the above commands complete successfully, the following message appears:
n rows affected
If the above commands did not complete successfully, verify that the server name, the user name that is logged in to Arcserve Backup, and database name are correct, and then repeat this step.
Expand the Windows Systems object in the Source directory tree.
The member server, with its new host name, appears under the Windows Systems object.
Copyright © 2016 |
|