- Notes, cautions, and warnings
- Preface
- Introduction
- Getting Started
- Configuring and Managing Storage and Applications
- Configuring and Managing Multiple Network Links for CyberSense
- Configuring and Managing Policies and Copies
- Managing Reports
- Monitoring
- Performing a PowerProtect Data Manager Recovery with Cyber Recovery
- Recovering PowerProtect Data Manager data
- Meeting prerequisites for a PowerProtect Data Manager recovery
- Initiating a PowerProtect Data Manager recovery in the Cyber Recovery UI
- Running a PowerProtect Data Manager recovery check
- Cleaning up after a PowerProtect Data Manager recovery
- Performing postrecovery steps for a PowerProtect Data Manager recovery
- Administration
- Administration overview
- Manually securing and releasing the Cyber Recovery vault
- Managing users
- Managing login sessions
- Setting up an email server
- Managing Cyber Recovery password expiration
- Resetting Cyber Recovery passwords
- Resetting the IP address on the management host
- Changing the network gateway on the Cyber Recovery server
- Updating the SSL security certificate
- Configuring a daily activity report
- Configuring a telemetry report
- Changing time zones
- Changing the log level
- Collecting logs for upload to support
- Log file rotation
- Protecting the Cyber Recovery configuration
- Retrieving your preserved Cyber Recovery configuration
- Setting up a maintenance schedule
- Cyber Recovery disaster recovery
- Troubleshooting
PowerProtect Data Manager 19.13 Cyber Recovery User Guide
Managing Cyber Recovery services
Start and stop Cyber Recovery Docker container services manually if there is an unexpected event on the management host.
Use the crsetup.sh script that is in the Cyber Recovery installation directory. To stop or start the Docker container services, use the --stop and --start options. To stop and then immediately restart the services, use the --restart option.
Enter the following command to stop the Docker container services:
# ./crsetup.sh –-stop
The following Cyber Recovery Docker container services stop in this order:
| Service | Function |
|---|---|
| swagger | Provides access to the Cyber Recovery REST API documentation |
| ui | Manages Cyber Recovery UI actions |
| edge | Acts as the gateway to the Cyber Recovery services |
| clouds | Provides access to supported cloud vendors; the current cloud vendor is Amazon Web Services (AWS) |
| system | Manages internal Cyber Recovery system-level activities such as cleaning, DR backups, creating log bundles, and so on |
| schedules | Manages Cyber Recovery schedule actions |
| reporting | Manages Cyber Recovery reports |
| policies | Manages Cyber Recovery policy actions |
| vcenter | Manages the vCenter server objects that are required for PowerProtect Data Manager deployments |
| mgmtdds | Manages the DD actions in the Cyber Recovery vault |
| apps | Manages storage system and applications in the Cyber Recovery vault actions |
| notifications | Manages alert, event, email, and log actions |
| vault | Manages CR Vault actions |
| users | Manages the Cyber Recovery Admin users and the Security Officer user actions |
| mongo-auth | Manages the database |
Enter the following command to start the Docker container services:
# ./crsetup.sh –-start
The Docker container services start again.
NOTE: At this time, you cannot stop and start an individual Docker container service.
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: <>()\