Prerequisites for agentless files and folder recovery
You can perform files or folder recovery only if the source AHV VM is running on specified operating system such as Red Hat Linux, or SUSE Linux, or Ubuntu, or windows. Also, the file system must be compatible for creating file system mappings from the full agentless VM backup. For AHV compatibility, see Support for NetBackup in Virtual Environments.
If support for restore of individual files and folders for a non-supported OS is required, protect such VMs with NetBackup standard policy type.
Table: Prerequisites for files and folder recovery
Step overview | Description and reference |
|---|
Agent based restore | Agent based restore is performed if the target host has NetBackup client or server installed. NetBackup version of such client or server must be 8.1 and later for windows and 8.2 and later for Linux. If you select the Linux version 8.1 or earlier, agentless restore options are displayed. You must specify the NetBackup configured host name in the target host for agent based restore.
If the logged on NetBackup user has sufficient permissions, you can browse the list of NetBackup hosts and select one for restore files or folders. If a logged on user does not have sufficient RBAC permissions, target host needs to be manually specified. You must specify the NetBackup configured host name or IP in the target host for agent based restore.
If source AHV VM is running on a Linux platform, you can restore files or folders to any supported Linux platform target host. If NetBackup is uninstalled from the target host, you can still initiate the agent based restore, however it fails. |
Agentless restore | Agentless restore is performed if the target host does not have NetBackup client or server installed. Both IPv4 and IPv6 IP addresses are supported. In IPv6 the standard CIDR format is not supported. |
Target host | Target host is a host on which you want to restore files or folders from an AHV VM backup. The host name must be in FQDN format or IP address. You can choose to restore files or folders to any target host, which is deployed on AHV, other hypervisors, or even a physical host. Ensure that the target host is accessible from the recovery host. Source and target host platforms must be homogeneous. Host files of windows source can be restored to windows target host and Linux source VM files on Linux target host. The default target host staging directory on target host is the user's home directory. You can provide a custom staging location. Prerequisites: NetBackup does not create target host staging location, the location must exist with write, and execute permissions.
The target host staging location must have enough space for restore operation. That includes restore file size,
NetBackup restore package (~150MB for windows) and (~100 MB for Linux), space for NetBackup operation logs.
If staging location path is on a system drive, it must have enough space required for other running processes.
|
| Agentless target machine must be running on supported OS platforms. For AHV compatibility, see Support for NetBackup Virtual Environment Tar utility should be present on default path on target host and path is added in the system path variable. NetBackup supports host name in ASCII format only. For host name with non-ASCII format you can use the IP address as target host. Maximum number of SSH connections to target host is configurable and default value is 10. SSH port should be open between recovery host and target host. If any firewall is configured, SSH port should be in Exception List in firewall. To restore to network path on target host provide the correct export permissions. For example, rw,sync,no_root_squash.
|
SSH connection requirements | Agentless restore to Linux target host is performed with the use of SSH service. It must be running on target host. SSH communication time out on the target host must be greater than 5 minutes. When you communicate with target host using SSH, NetBackup uses cipher aes256-ctr. SSH version must be 1.2 or later. Custom SSH port is supported. The following are supported: Key exchange algorithms: Host key ssh-rsa ssh-dss ecdsa-sha2-nistp256 ecdsa-sha2-nistp384 ecdsa-sha2-nistp521
Hash Method
|
SUDO user restore | Sudo user must be already existing on Linux target host. Ensure that the non-root user is already configured in the sudoers file. Example: Linux sudo user must have ownership of the custom staging location along with read, write, and execute permissions.
You can use SSH private key instead of password. See SSH key fingerprint. |
| Agentless target machine must be running on supported OS platforms. For AHV compatibility, see Support for NetBackup Virtual Environment. WMI must be configured and accessible between recovery and target host. For WMI and SMB requirements, seehttps://www.veritas.com/support/en_US/article.100040135. Accepts host name in ASCII format. For Unicode host name, use the IP address instead of the host name. The following services must be running on your windows hosts: DCOM RPC WMI File and Printer Sharing
By default, Admin share is enabled on host. If it is disabled. From GPO, user needs to enable Admin Share on the staging location drive or the drive on which the staging location is located. By default, Administrator users have required permission for WMI and DCOM access. If any issue occurs in DCOM and WMI permissions, refer Microsoft Documentation.. User or Group that is used to assign DCOM and WMI permissions: Out of two ways to assign the DCOM and WMI permissions, use one of the following options: User must be part of Administrators group, you can assign the permissions to the Administrators group. Assign the permissions to the specific user.
Supports UAC and non-UAC environments:
Staging location requirements: Default location is user's home directory, if custom path is provided, user must have access to it. Must be an absolute path. Soft-links, hard-links, network path, etc. are not supported. It should have enough space for restore operation, includes: If the path is on system drive, it must have enough space required for other running processes. Maximum character limit of the path is 260. However, NetBackup needs around 110 characters for formation of temporary location. Thus, you should pick a path that has less than 150 characters. If staging location and restore location is on same drive, double space of restore size could be needed.
Parallel restore jobs with same user are supported. However, if same destination folders are specified the restored data might be in inconsistent state.
|
WMI and SMB requirements | Agentless restore to Windows target host uses Windows Management Instrumentation (WMI) and Server Message Block (SMB) protocols. Ensure that WMI and SMB ports are opened in your firewall settings. Encrypt the data transfer over the SMB by enabling SMB encryption. For more details, refer Microsoft Documentation. Supports the SMB version 3.0. If your host has an older version, you can disable it. Refer, the Microsoft guidelines.
|
Recovery host | Recovery host is a NetBackup media server/client installed host and use to communicate with provided target host. NetBackup version of the recovery host must be 9.1 and later must have connectivity to target host. Linux recovery host must have SSH connectivity to Linux target host and windows recovery host must have WMI and SMB connectivity with windows target host. Recovery host must be of homogenous platform. Windows recovery host is required to restore files from windows AHV VM to target windows host. Similarly, Linux recovery host is required to restore file from Linux AHV VM to target Linux host. To restore files to Ubuntu target host use either RHEL or SUSE as recovery host. Recovery host with NetBackup 9.1 server or client is only supported. Network path as staging location on recovery host works, provided the export permissions are correct. For example, rw,sync,no_root_squash. Default staging location on recovery host is: For Linux: /{install-path}/openv/var/tmp/staging For windows: {install-path}\NetBackup\Temp\staging Default staging location can be changed using bpsetconfig.
|
Other | |