Search <book_title>...

Veritas NetBackup™ CloudPoint Install and Upgrade Guide

Last Published: 2021-09-17

Product(s): NetBackup & Alta Data Protection (9.1.0.1)

Restarting CloudPoint

If you need to restart CloudPoint, it's important that you restart it correctly so that your environmental data is preserved.

To restart CloudPoint in the Docker environment

Warning:

Do not use commands such as docker restart or docker stop and docker start to restart CloudPoint. Use the docker run command described below.

On the instance where CloudPoint is installed, enter the following command:

# sudo docker run -it --rm 
-v /cloudpoint:/cloudpoint 
-v /var/run/docker.sock:/var/run/docker.sock 
veritas/flexsnap-cloudpoint:<version> restart

Here, version represents the currently installed CloudPoint product version.

For example:

# sudo docker run -it -rm 
-v /cloudpoint:/cloudpoint 
-v /var/run/docker.sock:/var/run/docker.sock 
veritas/flexsnap-cloudpoint:8.3.0.8549 restart

Note:

Ensure that you enter the command without any line breaks.

To restart CloudPoint in the Podman environment

First, stop the CloudPoint by using the following command on the instance where CloudPoint is installed:

# podman run -it --rm --privileged 
-v /cloudpoint:/cloudpoint 
-v /run/podman/podman.sock:/run/podman/podman.sock
veritas/flexsnap-cloudpoint:<version> stop

Then, start it again by using the following command:

# podman run -it --rm --privileged 
-v /cloudpoint:/cloudpoint 
-v /run/podman/podman.sock:/run/podman/podman.sock
veritas/flexsnap-cloudpoint:<version> start

Note:

Ensure that you enter the commands without any line breaks.

Troubleshooting CloudPoint restart

Refer to the following troubleshooting scenario:

Starting or restarting the CloudPoint services may fail if a stale IP address entry is retained in the Podamn layer on RHEL 8.3 environment

Sometimes the following error may be encountered when the cloudPoint service containers restart.

Error adding network: failed to allocate for
 range 0: 10.89.0.140 has been allocated to
 02da9e9aab2f79303c53dfb10b5ae6b6b70288d36b8fffbdfabba046da5a9afc,
 duplicate allocation is not allowed
ERRO[0000] Error while adding pod to CNI network
 "flexsnap-network": failed to allocate for
 range 0: 10.89.0.140 has been allocated to
 02da9e9aab2f79303c53dfb10b5ae6b6b70288d36b8fffbdfabba046da5a9afc,
 duplicate allocation is not allowed
Error: error configuring network namespace for container
 02da9e9aab2f79303c53dfb10b5ae6b6b70288d36b8fffbdfabba046da5a9afc:
 failed to allocate for range 0:
 10.89.0.140 has been allocated to
 02da9e9aab2f79303c53dfb10b5ae6b6b70288d36b8fffbdfabba046da5a9afc,
 duplicate allocation is not allowed"

The issue exists in the Podman subsystem which fails to remove the existing IP allocated for the container from dir /var/lib/cni/networks/flexsnap-network/, when the container is stopped.

Workaround

To remove the stale entry

Find the stale IP address which is retained when the containers are stopped. For example 10.89.0.140, in the above error.
Run the following command to delete the stale entry from dir
# rm /var/lib/cni/networks/flexsnap-network/<stale IP address>
Then start the service using
# podman start <service-name>