NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- Configure Snapshot Manager in NetBackup
- Managing intelligent groups for cloud assets
- Protecting cloud assets or intelligent groups for cloud assets
- About protecting Microsoft Azure resources using resource groups
- About the NetBackup Accelerator for cloud workloads
- Protecting PaaS assets
- Installing the native client utilities
- Configuring storage for different deployments
- Add credentials to a database
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
- Troubleshoot PaaS workload protection and recovery issues
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:
The following requirements apply to snapshots:
(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 the 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 and Google Cloud Platform): The Snapshot Manager host and the connected VM must be in the same account and region.
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 the required supported configuration.
The host must have the
and 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 must be attached to the Snapshot Manager instance explicitly.File systems on the host must be supported.
Configure ports 5671 and 443 for open Snapshot Manager host.
For agentless restore, in Linux systems, configure port 22 on the indexable virtual machines. For the Windows platform, configure the ports 135, 445, and the dynamic or fixed WMI-IN port on the indexable virtual machines.
Ensure that you have appropriate permissions to perform a granular restore. See the information on role permissions in the NetBackup Web UI Administrator's Guide.
Ensure that the following points are addressed before you perform the single file restore from a snapshot backup:
You have NetBackup and Snapshot Manager version 10.2 or later.
A granular restore is successful only if the backup image is restored from the MSDP storage server (10.3 or later), with instant access enabled.
For MSI and RPM-based agent installation, the target host agent must be upgraded to the latest version.
On the Windows target host, the administrator must have the attach and detach policy enabled for the disks. For more information, refer to the AttachVirtualDisk function.
(For Windows) To restore symlink, the agent must be configured using the required access. For this, add the administrator user in the Create symbolic links policy under
Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment
.The backup must be taken with the
option selected.The target virtual machine must have access to the MSDP storage server over NFS/SMB.
(For Linux) The NFS client (
nfs-utils
) must be installed to restore over NFS.If
/etc/hosts
entry is created for the MSDP host in the MSDP storage server, add the FQDN of the MSDP storage server also in the same entry.The Windows target must meet the following requirements:
(For restoring Windows image content with Restoring Access Control list) The Samba user credentials must be stored in the Windows credential manager for an MSDP storage server. This server is the one that exports the instant access share.
On the MSDP server, run the following command to generate the Samba credentials.
smbpasswd -a <username>
Add the DNS name or the IP address of the MSDP server. Provide the username from the previous step and the password that was generated in the Windows credential manager.
The smbpasswd command fails if the username is not present on the MSDP server. You must first add users with the command useradd <username> command.
(For restoring Linux image content) The NFS client is installed.
For more information on how to enable SMB/IA on MSDP, refer to the NetBackup Deduplication Guide.
Verify the SMB configuration on the MSDP server with the following precheck script:
/usr/openv/pdde/vpfs/bin/ia_byo_precheck.sh