PowerProtect Data Manager 19.13 Cyber Recovery User Guide

Cleaning up existing Cyber Recovery Docker containers

If necessary, clean up existing Cyber Recovery containers before you run the restore procedure after a disaster.

Steps

  1. Identify the Cyber Recovery containers that are running:
    docker container ls --filter name=cr_

    The output shows the running Cyber Recovery containers. The following list is an example of what you might see:

    • cr_swagger
    • cr_ui
    • cr_edge
    • cr_clouds
    • cr_shelteredharbor
    • cr_system
    • cr_schedules
    • cr_policies
    • cr_vcenter
    • cr_mgmtdds
    • cr_apps
    • cr_notifications
    • cr_vault
    • cr_users
    • cr_mongo
    • cr_registry
    NOTE:
    • Each container name includes a suffix, which differs depending on your version of Docker Compose.
    • If the Cyber Recovery instance is not running on or Amazon Web Services (AWS), the cr_clouds container is not displayed.
    • If the Cyber Recovery instance is not running in a Sheltered Harbor deployment, the cr_shelteredharbor container is not displayed.
  2. Stop all the running Cyber Recovery containers:
     docker container stop `docker container ls -q --filter name=cr_`
  3. Remove all the stopped Cyber Recovery containers:
    docker container rm `docker container ls -a -q --filter name=cr_`
  4. Verify that all Cyber Recovery containers are removed:
    docker container ls -a –-filter name=cr_

    No containers are listed.

  5. List the Cyber Recovery images that are associated with the containers that you removed:
    docker images | grep localhost:14779/cr_
  6. Remove all the Cyber Recovery container images:
     docker image remove `docker images | grep localhost:14779/cr_ | awk '{ print $3 }'`
  7. Verify that all the Cyber Recovery container images have been removed:
    docker images | grep localhost:14779/cr_

    The images that were listed in step 5 are no longer listed and the cleanup is complete.

  8. Perform to the Cyber Recovery software restore procedure (see Restoring a Cyber Recovery software installation after a disaster).

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\