NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- About protecting cloud assets
- Limitations and considerations
- Configure Snapshot Manager's in NetBackup
- Managing intelligent cloud groups
- Protecting cloud assets or intelligent cloud groups
- Cloud asset cleanup
- Cloud asset filtering
- AWS and Azure government cloud support
- About protecting Microsoft Azure resources using resource groups
- About the NetBackup Accelerator for cloud workloads
- Configuring backup schedule for cloud workloads
- Backup options for cloud workloads
- Snapshot replication
- Configure AWS snapshot replication
- Using AWS snapshot replication
- Support matrix for account replication
- Protect applications in-cloud with application consistent snapshots
- Protecting PaaS objects
- Prerequisites for protecting PaaS assets
- Installing the native client utilities
- Configuring the storage server for instant access
- Limitations and considerations
- Discovering PaaS assets
- Viewing PaaS assets
- Managing PaaS credentials
- View the credential name that is applied to a database
- Add credentials to a database
- Add protection to PaaS assets
- Perform backup now
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
Before you begin
Ensure the following points are addressed before you perform granular restore. Configured Snapshot Manager and VM to be protected with granular restore enabled have the following requirements:
(Microsoft Azure and Azure Stack Hub) Even if Snapshot Manager is not deployed in the same subscription and region as the connected VM, but if a backup schedule is configured as part of the protection plan, then granular restore can be performed. For snapshot-only protection plan schedule, for both Azure and Azure Stack Hub, you need to deploy the Snapshot Manager host in the same subscription and region as the VMs.
Amazon AWS: The Snapshot Manager host and the connected VM must be in the same account and region.
Google Cloud Platform: The Snapshot Manager host and the connected VM must be in the same project.
The cloud plug-in must be configured to protect the assets in the region in which the Snapshot Manager host is deployed.
The host must be in a connected state and must have required supported configuration.
The host must have the fsConsistent and indexable flags enabled when connected. The indexable flag is applicable for a snapshot-only protection plan schedule.
Protection plan must have the check box enabled.
Apart from the boot disk and disk that is mounted on "/cloudpoint", no extra disk should be attached to Snapshot Manager instance explicitly.
File systems on the host must be supported.
Configure port 5671 and 443 for open Snapshot Manager host.
For agentless restore, in Linux systems, configure the port 22 on the indexable virtual machines. For Windows platform, configure the ports 135, 445 and the dynamic/fixed WMI-IN port on the indexable virtual machines.
If you want to restore volume to same the virtual machine and location, you must detach existing volume and free the slot and then try to restore.