NetBackup™ Web UI Cloud Administrator's Guide

Consider the following important points for granular restore.

• 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.

• The ephemeral storage devices are ignored when a snapshot is performed. (For example, Amazon AWS instance store volumes and Microsoft Azure temporary disks.) 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. To support the recovery of LVM assets, you need to restart the older agents.

• Granular restore (GRT) or single file restore (SFR) can be performed with the help of VxMS indexing. VxMS indexing is applicable for all Snapshot Manager supported file systems. VxMS indexing can be performed for Azure, Azure Stack, AWS cloud and GCP is 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 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.

• Snapshot Manager 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 Snapshot Manager 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.

• Snapshot Manager host limits the number of disk slots that the cloud providers enforce. NetBackup throttles the indexing requests to Snapshot Manager. To achieve this request, during Cloud Asset discovery process, NetBackup fetches Snapshot Manager host capabilities. These capabilities include the Max no of index jobs parameter. This parameter is used to limit the requests that are sent to Snapshot Manager 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 Snapshot Manager 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 Snapshot Manager host. If the Snapshot Manager host receives number of indexing requests more than its capability, the requests are queued.

• During indexing, OS errors can occur while crawling files, directories, or other entries. These errors are ignored and the indexing operation continues. To restore the missing files, you must initiate the granular restore operations on the parent folder.

• When you create or mount a disk from the Windows VM, add the drive letter. This action ensures that the indexing operation can capture the correct drive letter.

• In some cases a mount point is not visible when you browse for add files or folders in the recovery point. Consider the following reasons:

  • The "/" (root file system) is on an LVM, and

  • The mount point is not directly related to "/" (root file system).

  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.

• A user group cannot restore a drive as source to an alternate folder as the destination. A user group does not have the writer permission to create a new folder.

• 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.

• Files stored on volume mounted on folder (junction point) can be restored only if underlying disk has GPT partition layout. If volume is mounted using drive letter, then files can be restored irrespective of partition layout of the underlying disk.

• Consider the following limitations for single file restore from backup of snapshot:

  • If restoring files/folders when source host is Linux and target host is Windows, then

    • File attributes cannot be restored on windows host and only the content of the file is restored.

    • If there is any symlink in selected files/folders for restoration, then the symlink will not be restored.

  • In case of Original Location Restore, available size check before copy is skipped.

  • If restoring files/folders when source host is Linux and target host is Linux, then socket and block files would not be restored.

  • Restoration of files and folders is not supported when they reside on LDM disks/dynamic disks/storage spaces.

  • Live mount retained during partial restore success would be removed/expired before retention period expiry, if media server or PureDisk Deduplication Engine and Veritas Provisioning file system daemon service restarts.

  • If Media servers are not upgraded to 10.2, then master server on 10.2 will be used to connect to NetBackup Snapshot Manager.

  • Junction point on windows after indexing is seen as format like Volume {4e3f8396-490a-400a-8abf-5579cafd4c0f} in Add files. If junction point is selected in Add files for single file restore from backup operation then select Restore everything to a different location and enable the Require to restore access control list in Advanced option.