Veritas NetBackup™ CloudPoint Install and Upgrade Guide

CloudPoint agent fails to connect to the CloudPoint server if the agent host is restarted abruptly.

This issue may occur if the host where the CloudPoint agent is installed is shut down abruptly. Even after the host restarts successfully, the agent fails to establish a connection with the CloudPoint server and goes into an offline state.

The agent log file contains the following error:

flexsnap-agent-onhost[4972] MainThread flexsnap.connectors.rabbitmq:
ERROR - Channel 1 closed unexpectedly: 
(405) RESOURCE_LOCKED - cannot obtain exclusive access to locked queue '
flexsnap-agent.a1f2ac945cd844e393c9876f347bd817' in vhost '/'

This issue occurs because the RabbitMQ connection between the agent and the CloudPoint server does not close even in case of an abrupt shutdown of the agent host. The CloudPoint server cannot detect the unavailability of the agent until the agent host misses the heartbeat poll. The RabbitMQ connection remains open until the next heartbeat cycle. If the agent host reboots before the next heartbeat poll is triggered, the agent tries to establish a new connection with the CloudPoint server. However, as the earlier RabbitMQ connection already exists, the new connection attempt fails with a resource locked error.

As a result of this connection failure, the agent goes offline and leads to a failure of all snapshot and restore operations performed on the host.

Workaround:

Restart the Veritas CloudPoint Agent service on the agent host.

CloudPoint agent registration on Windows hosts may time out or fail.

For protecting applications on Windows, you need to install and then register the CloudPoint agent on the Windows host. The agent registration may sometimes take longer than usual and may either time out or fail.

Workaround:

To resolve this issue, try the following steps:

Refer to the following for more information:

See Registering the Windows-based agent.

See Restarting CloudPoint.

Disaster recovery when DR package is lost or passphrase is lost.

This issue may occur if the DR package is lost or the passphrase is lost.

In case of Catalog backup, 2 backup packages are created:

The DR package contains the NetBackup UUID certs and Catalog DB also has the UUID. When you perform disaster recovery using the DR package followed by catalog recovery, both the UUID cert and the UUID are restored. This allows NetBackup to communicate with CloudPoint since the UUID is not changed.

However if the DR package is lost or the Passphrase is lost the DR operation cannot be completed. You can only recover the catalog without DR package after you reinstall NetBackup. In this case, a new UUID is created for NetBackup which is not recognised by CloudPoint. The one-to-one mapping of NetBackup and CloudPoint is lost.

Workaround:

To resolve this issue, you must update the new NBU UUID and Version Number after NetBackup primary is created.

After you get the NBU UUID and Version number, execute the following command on the CloudPoint host to update the mapping:

/cloudpoint/scripts/cp_update_nbuuid.sh -i <NBU UUID> -v <Version Number>

The snapshot job is successful but the backup from snapshot job fails with the error "Certificate verification failed" if CloudPoint server's certificate is revoked

In backup from snapshot operations, while taking snapshot NetBackup communicates with CloudPoint server.

In backup operations, communication happens between the datamover container on CloudPoint server and NetBackup media/primary server. Following flags should be used to enforce the revocation status check of certificates of respective servers.

See Configuring security for Azure and Azure Stack .

CloudPoint fails to establish connection using agentless to the Windows cloud instance

Error 1: <Instance_name>: network connection timed out.

Case 1: CloudPoint server log message:

WARNING - Cannot connect to the remote host. SMB Connection timeout
 <IP address> <user>

…

flexsnap.OperationFailed: Could not connect to the remote server 
<IP address>

Workaround

To resolve this issue, try the following steps:

Case 2: CloudPoint Server log message:

WARNING - Cannot connect to the remote host. WMI Connection 
timeout <IP address> <user>

…

flexsnap.OperationFailed: Could not connect to the remote 
server <IP address>

Workaround:

To resolve this issue, try the following steps:

Case 3: CloudPoint Server log message:

Exception while opening SMB connection, [Errno Connection error 
(<IP address>:445)] [Errno 113] No route to host.

Workaround: Verify if the cloud instance is up and running or not in inconsistent state.

Case 4: CloudPoint Server log message:

Error when closing dcom connection: 'Thread-xxxx'"

Where, xxxx is the thread number.

Workaround:

To resolve this issue, try the following steps:

Error 2: <Instance_name>: Could not connect to the virtual machine.

CloudPoint server log message:

Error: Cannot connect to the remote host. <IP address> Access denied. 

Workaround:

To resolve this issue, try the following steps:

CloudPoint cloud operations fail on a RHEL system if a firewall is disabled

The CloudPoint operations fail for all the supported cloud plugins on a RHEL system, if a firewall is disabled on that system when the CloudPoint services are running. This is a network configuration issue that prevents the CloudPoint from accessing the cloud provider REST API endpoints.

Workaround