Please enter search query.
Search <book_title>...
NetBackup™ Snapshot Manager Install and Upgrade Guide
Last Published:
2024-04-10
Product(s):
NetBackup & Alta Data Protection (10.3)
- Introduction
- Section I. NetBackup Snapshot Manager installation and configuration
- Preparing for NetBackup Snapshot Manager installation
- Deploying NetBackup Snapshot Manager using container images
- Deploying NetBackup Snapshot Manager extensions
- Installing the NetBackup Snapshot Manager extension on a VM
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (GKE) in GCP
- NetBackup Snapshot Manager cloud providers
- Configuration for protecting assets on cloud hosts/VM
- Protecting assets with NetBackup Snapshot Manager's on-host agent feature
- Installing and configuring NetBackup Snapshot Manager agent
- Configuring the NetBackup Snapshot Manager application plug-in
- Microsoft SQL plug-in
- Oracle plug-in
- Protecting assets with NetBackup Snapshot Manager's agentless feature
- Snapshot Manager catalog backup and recovery
- NetBackup Snapshot Manager assets protection
- Volume Encryption in NetBackup Snapshot Manager
- NetBackup Snapshot Manager security
- Preparing for NetBackup Snapshot Manager installation
- Section II. NetBackup Snapshot Manager maintenance
- NetBackup Snapshot Manager logging
- Upgrading NetBackup Snapshot Manager
- Migrating and upgrading NetBackup Snapshot Manager
- Post-upgrade tasks
- Uninstalling NetBackup Snapshot Manager
- Troubleshooting NetBackup Snapshot Manager
Restarting NetBackup Snapshot Manager
If you need to restart NetBackup Snapshot Manager, it's important that you restart it correctly so that your environmental data is preserved.
Run the following command to restart NetBackup Snapshot Manager in Docker/Podman environment using the flexsnap_configure CLI:
# flexsnap_configure restart
The output resembles as follows:
Restarting the services Stopping services at time: Mon Jul 31 11:43:43 UTC 2023 Stopping container: flexsnap-workflow-system-0-min ...done Stopping container: flexsnap-workflow-general-0-min ...done Stopping container: flexsnap-listener ...done Stopping container: flexsnap-nginx ...done Stopping container: flexsnap-notification ...done Stopping container: flexsnap-policy ...done Stopping container: flexsnap-scheduler ...done Stopping container: flexsnap-onhostagent ...done Stopping container: flexsnap-agent ...done Stopping container: flexsnap-coordinator ...done Stopping container: flexsnap-api-gateway ...done Stopping container: flexsnap-certauth ...done Stopping container: flexsnap-rabbitmq ...done Stopping container: flexsnap-postgresql ...done Stopping container: flexsnap-fluentd ...done Stopping services completed at time: Mon Jul 31 11:44:04 UTC 2023 Starting services at time: Mon Jul 31 11:44:04 UTC 2023 Starting container: flexsnap-fluentd ...done Starting container: flexsnap-postgresql ...done Starting container: flexsnap-rabbitmq ...done Starting container: flexsnap-certauth ...done Starting container: flexsnap-api-gateway ...done Starting container: flexsnap-coordinator ...done Starting container: flexsnap-agent ...done Starting container: flexsnap-onhostagent ...done Starting container: flexsnap-scheduler ...done Starting container: flexsnap-policy ...done Starting container: flexsnap-notification ...done Starting container: flexsnap-nginx ...done Starting container: flexsnap-listener ...done Starting services completed at time: Mon Jul 31 11:44:21 UTC 2023