NetBackup™ Web UI Cloud Administrator's Guide

After a restore job is completed, you cannot expand the directories in the File List section of the restore job.

If adequate space is not available on the target location, the restore operation fails before the copy operation begins.

In the activity monitor summary, when the restore job starts it shows the current file which is the first entry in the restore items. After the job is complete, the summary goes blank.

Bytes transferred and estimated bytes in activity monitor are not updated and shown as 0.

(Applicable for GCP only) The number of attachment points for a data disk available on the CloudPoint host minus 1 and the instance type. CloudPoint metadata volume consumes this one attachment point.

The ephemeral storage devices like Amazon AWS instance store volumes and Microsoft Azure temporary disks are ignored when a snapshot is performed. These devices are also ignored for indexing as well.

The file systems that are created on LDM disks are ignored when host consistent snapshots are created and indexed.

Until old agent (pre-installed) service is not restarted, alternate host restore (GRT and application) of LVM asset might fail. You need to restart the older agents in order to support recovery of LVM assets.

Granular restore (GRT) or single file restore (SFR) can be performed with the help of VxMS indexing. VxMS indexing is applicable for all CloudPoint supported file systems. VxMS indexing can be performed for Azure, AzureStack and AWS cloud except for GCP it will be performed on an existing mount based indexing.

Host consistent snapshot is supported for EXT2 file system only if it is mounted as read-only.

If any unsupported file systems are present on the host, the host can't be added to the protection plan that is created for granular restore. The protection plans for granular restore have the Enable granular recovery for files or folders check box value set to true.

CloudPoint communicates the number of index jobs that can be run to NetBackup. NetBackup then throttles the requests. By default, the number of index jobs is initialized to 2. Post discovery of CloudPoint host capabilities, it is increased to number of disk slots available. However, you can update the value for indexing max_jobs=<value> in flexsnap.conf file to override this limit.

CloudPoint host limits the number of disk slots that the cloud providers enforce. NetBackup throttles the indexing requests to CloudPoint. To achieve this request, during Cloud Asset discovery process, NetBackup fetches CloudPoint host capabilities. These capabilities include the Max no of index jobs parameter. This parameter is used to limit the requests that are sent to CloudPoint and index job queue in NetBackup. By default, the maximum number of parallel indexing jobs is 2. But once the cloud plug-in is configured which discovers the CloudPoint host, the capability API fetches the number of max jobs based on attachment points and available resources. You can set the limit by adding the indexing max_jobs=x entry in the config file of the CloudPoint host. If the CloudPoint host receives number of indexing requests more than its capability, the requests are queued.

When an indexing operation is in progress, if any OS errors occur while crawling files, directories, or other entries, the errors are ignored and the indexing operation continues. To restore the missing files, you must initiate the granular restore operations on the parent folder.

If a mount point is not visible in the tree on the left panel for browsing when you add files or folders from the recovery point, it can be because of the following reasons:

In this scenario, search for the mount point from the right panel and then restore the files or folders successfully.

For example, if a disk is mounted on /mnt1/mnt2 where /mnt1 is any directory on the "/" (root FS which is on LVM setup) and mnt2 is a mount point inside mnt1, the "mnt2" is not visible in the tree on the left panel. However, you can search and restore files or folders inside mount point.

To restore files and folders from VM snapshot recovery points, the /etc/fstab file on the Linux servers, must have entries based on the file system UUID, instead of device paths. The device paths can change depending on the order in which Linux discovers the devices during system boot.

While restoring application or file systems from one OS version to another OS version, refer to the OS and application vendor's compatibility matrix. Restore of file system from higher version to lower version is not recommended.

While restoring a drive as source to an alternate folder as destination, the user group cannot perform the write operation on the newly created folder due to lack of the write permission.

The agentless connection cannot restore the encrypted file by Windows (or EFS) through Granular File Level Restore (Restore Files and Folder option). However you can restore the file through volume level restore and then decrypt the file.