Before you begin
Ensure the following points are addressed before you perform granular restore.
Configured CloudPoint server and VM to be protected with granular restore enabled have the following requirements:
Microsoft Azure: The CloudPoint host and the connected VM must be in the same subscription and region.
Amazon AWS: The CloudPoint host and the connected VM must be in the same account and region.
Google Cloud Platform: The CloudPoint host and the connected VM must be in the same project.
The host must be in a connected state and must have required supported configuration.
The cloud plug-in must be configured to protect the assets in the region in which the CloudPoint 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 fsConsistent flag allows the files systems on the host to be snapped by the CloudPoint and indexable flag allows the host to be indexed. The indexable flag can be set as true only if the fsConsistent flag is set as true.
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 CloudPoint instance explicitly.
File systems on the host must be supported. See List of supported file systems.
Configure port 5671 and 443 for open CloudPoint host.
For an agentless restore, port 22 must be configured on the indexable virtual machines for agent connection.
For on-host restore, port 5671 and 3389 (RDP) must be open on the target virtual machine for agent connection. RDP is only for used for configuration and is optional.
Ensure that you have appropriate permissions to perform a granular restore. See the Role permissions topic in the NetBackup Web UI Administrator's Guide.
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.