Symptoms

Replicated backups are not visible in the UI or CLI after upgrading to Avamar v19.10. These backups were visible prior to upgrading.

Cause

The cause is unknown at the time of publication, but a workaround is available in the resolution steps below.

Resolution

1. Log in to the Avamar Utility Node as admin. 2. Elevate to root privilege: su - 3. Prior to making any changes, make a backup copy of any existing keystores: a. If /home/admin/.keystore exists: cp -p /home/admin/.keystore /home/admin/.keystore-`date +%y%m%d` b. If /home/tomcat/.keystore exists: cp -p /home/tomcat/.keystore /home/tomcat/.keystore-`date +%y%m%d` c. For rmi_ssl_keystore: cp -p /usr/local/avamar/lib/rmi_ssl_keystore /usr/local/avamar/lib/rmi_ssl_keystore-`date +%y%m%d` d. Verify that any copied keystores exist: ls -al /home/admin/.keystore* ls -al /home/tomcat/.keystore* ls -al /usr/local/avamar/lib/rmi_ssl_keystore* 4. Run the following command on the source grid: echo | openssl s_client -connect <target-grid-ip-address>:9443 2>/dev/null | openssl x509 > /tmp/<target>.cert.pem For example: If the target grid is "blueserver.company.com" and has an IP address if 10.10.10.11: echo | openssl s_client -connect 10.10.10.11:9443 2>/dev/null | openssl x509 > /tmp/blueserver.cert.pem 5. Run the import command on the source grid: keytool --importcert -trustcacerts -alias <target> -file /tmp/<target>.cert.pem -keystore /usr/local/avamar/lib/rmi_ssl_keystore -storepass $(avlockbox.sh -r keystore_passphrase) Example using the "blueserver" grid: keytool --importcert -trustcacerts -alias blueserver -file /tmp/blueserver.cert.pem -keystore /usr/local/avamar/lib/rmi_ssl_keystore -storepass $(avlockbox.sh -r keystore_passphrase) 6. Restart the Management Console Server (MCS), Enterprise Manager (EM), and the backup scheduler: a. Restart MCS: mcserver.sh --restart b. Restart EM: emwebapp.sh --restart c. Restart the backup scheduler: dpnctl start sched 7. If the remote backups still cannot be seen, stop the firewall, and restart services again: a. Stop the firewall: service avfirewall stop b. Restart MCS: mcserver.sh --restart c. Restart EM: emwebapp.sh --restart d. Restart the backup scheduler: dpnctl start sched 8. If the remote backups still cannot be seen, update mcserver.xml and restart the services again: a. Make a backup copy of mcserver.xml: cp -p /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml /usr/local/avamar/var/mc/server_data/prefs/x-mcserver.xml.`date +%y%m%d` b. Update get_backups_from_external_server from to false to true: <entry key="get_backups_from_external_server" value="true" /> c. Restart MCS: mcserver.sh --restart d. Restart EM: emwebapp.sh --restart e. Restart the backup scheduler: dpnctl start sched 9. Once the remote backups can be seen once, revert steps 5 and 6 to start the firewall and change mcserver.xml back: a. Start the firewall: service avfirewall start b. Make another backup copy of mcserver.xml: cp -p /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml /usr/local/avamar/var/mc/server_data/prefs/x-mcserver.xml-2.`date +%y%m%d` c. Update get_backups_from_external_server from true to false: <entry key="get_backups_from_external_server" value="false" /> d. Restart MCS: mcserver.sh --restart e. Restart EM: emwebapp.sh --restart f. Restart the backup scheduler: dpnctl start sched If the remote backups are no longer visible when the firewall is running, it is likely that the rules must be updated: a. Make a copy of the firewall rules: cp -p /usr/local/avamar/lib/admin/security/avfwb_custom_config.txt /usr/local/avamar/lib/admin/security/avfwb_custom_config.txt.`date +%y%m%d` b. See the following article to update the rules: Avamar: How to add or remove custom Avamar firewall rules with edit-firewall-rules.sh (v7.3 onwards)

Support Cases