If you change the host name or the IP address of the D2D Server or the client node (backup node), you have to configure the system settings. You configure the system settings to help ensure the following items:
When the Host Name of the Central D2D Server is Changed
When you change the host name of the central D2D Server, you must configure the server so that you can use CA ARCserve D2D for Linux without any problem.
Follow these steps:
source /opt/CA/d2dserver/bin/setenv
/opt/CA/d2dserver/sbin/sqlite3 /opt/CA/d2dserver/data/ARCserveLinuxD2D.db "update D2DServer set Name=’New_Hostname’ where IsLocal=1"
/opt/CA/d2dserver/sbin/sqlite3 /opt/CA/d2dserver/data/License.db "update LicensedMachine set ServerName =’New_Hostname’ where ServerName =’Old_Hostname’"
mv /opt/CA/d2dserver/TOMCAT/conf/server.keystore /opt/CA/d2dserver/TOMCAT/conf/server.keystore.old
keytool -genkey -alias tomcat -keyalg DSA -keypass <YOUR_VALUE> -storepass <YOUR_VALUE> -keystore /opt/CA/d2dserver/TOMCAT/conf/server.keystore -validity 3600 -dname "CN=<New Hostname>"
Note: Update the YOUR_VALUE field according to your requirement. Typically, the value is your password.
Example:
keytool -genkey -alias tomcat -keyalg DSA -keypass LinuxD2D -storepass LinuxD2D -keystore /opt/CA/d2dserver/TOMCAT/conf/server.keystore -validity 3600 -dname "CN=New Hostname"
<Connector port="8014" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="${catalina.home}/conf/server.keystore" keystorePass="YOUR_VALUE"/>
Example:
<Connector port="8014" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="${catalina.home}/conf/server.keystore" keystorePass="LinuxD2D"/>
/opt/CA/d2dserver/bin/d2dserver restart
The central D2D Server is configured.
When the Host Name or IP Address of the Member Server is Changed
When you change the host name or the IP address of the member D2D Server, configure the member server to manage it from the central server. If you do not configure the member server, then you will have an error when you try to manage it from the central server. A member server is a server that you have added to the central D2D Server web interface.
Follow these steps:
source /opt/CA/d2dserver/bin/setenv
/opt/CA/d2dserver/sbin/sqlite3 /opt/CA/d2dserver/data/ARCserveLinuxD2D.db "update D2DServer set Name=’New_Hostname’ where IsLocal=1"
mv /opt/CA/d2dserver/TOMCAT/conf/server.keystore /opt/CA/d2dserver/TOMCAT/conf/server.keystore.old
keytool -genkey -alias tomcat -keyalg DSA -keypass <YOUR_VALUE> -storepass <YOUR_VALUE> -keystore /opt/CA/d2dserver/TOMCAT/conf/server.keystore -validity 3600 -dname "CN=<New Hostname>"
Note: Update the YOUR_VALUE field according to your requirement. Typically, the value is your password.
Example:
keytool -genkey -alias tomcat -keyalg DSA -keypass LinuxD2D -storepass LinuxD2D -keystore /opt/CA/d2dserver/TOMCAT/conf/server.keystore -validity 3600 -dname "CN=New Hostname"
<Connector port="8014" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="${catalina.home}/conf/server.keystore" keystorePass="YOUR_VALUE"/>
Example:
<Connector port="8014" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="${catalina.home}/conf/server.keystore" keystorePass="LinuxD2D"/>
/opt/CA/d2dserver/bin/d2dserver restart
The old host name server is deleted.
The Add Server dialog opens.
The Add Server dialog closes and the member server with the new host name is added to the UI.
source /opt/CA/d2dserver/bin/setenv
/opt/CA/d2dserver/sbin/sqlite3 /opt/CA/d2dserver/data/License.db "update LicensedMachine set ServerName =’New_Hostname’ where ServerName =’Old_Hostname’"
The member D2D Server is configured.
When the Host Name or the IP Address of the Client Node is Changed
If you change the host name or the IP address of a node, you can configure the host name or the IP address in the system settings so that you can back up that node without any error.
Follow these steps:
For example, consider the old host name for node1 is First_Node. The backup destination for node1 is //Backup_Destination/LinuxBackup. After the first successful backup, a folder named First_Node is created in //Backup_Destination/LinuxBackup. Now, you have modified the old host name to Second_Node. Locate the First_Node folder in //Backup_Destination/LinuxBackup and rename the folder to Second_Node.
source /opt/CA/d2dserver/bin/setenv
/opt/CA/d2dserver/bin/d2drp --storagepath=Backup Destination --node=New_Hostname
/opt/CA/d2dserver/sbin/sqlite3 /opt/CA/d2dserver/data/ARCserveLinuxD2D.db "update JobQueue set TargetName=’New_Hostname’ where JobType in (1,3,4,5) and TargetName=’Old_Hostname’"
/opt/CA/d2dserver/sbin/sqlite3 /opt/CA/d2dserver/data/ARCserveLinuxD2D.db "update TargetMachine set Name=’New_Hostname’ where Name=’Old_Hostname’"
Note: If you use NFS share or CIFS share as the backup destination, you should mount it to Local share.
Example: If your mount point is /mnt/backup_destination.
/opt/CA/d2dserver/bin/d2drp --storagepath=<mount point> --node=New_Hostname
Note: If you use Local share, then the command is:
/opt/CA/d2dserver/bin/d2drp --storagepath=<local path> --node=New_Hostname
/opt/CA/d2dserver/sbin/sqlite3 /opt/CA/d2dserver/data/License.db "update LicensedMachine set MachineName =’New_Hostname’ where MachineName =’Old_Hostname’"
The host name is configured to perform a backup without any error.
Copyright © 2013 CA.
All rights reserved.
|
|