A NAS proxy is the same as Hybrid Workloads agent; it is the link between the NAS device and the Druva server to handle the backup and restore of NAS shares. To back up from NAS shares, you must install the NAS proxy on a separate Linux or Windows server and map it to the NAS device. Druva supports backup from SMB Shares if the proxy is installed on a Windows server. Similarly, to back up from NFS Shares, the proxy must be installed on a Linux server.

The Hybrid Workloads agent on the NAS proxy may get disconnected from the Druva Cloud because of the following reasons:

For Windows:
Command-line: Run > net start PhoenixCPHService
Run > services.msc > Druva Hybrid Workloads agent Client Service > Start
​For Linux: service Phoenix restart

From the Backup Sets page, click a backup set. In the backup set details page, navigate to the Backups tab. The Backups tab lists all the recovery points for that backup set. The Scan Type Column indicates whether the scan was a Full Scan or Advanced Smart Scan.

Druva saves the old activation tokens and displays them under Manage > Activation Tokens. You can copy the activation token from the Manage Activation Tokens page. For more information, see Manage activation tokens.

No. You can install any number of NAS proxies. The proxies become functional in backup and restore jobs only when they are mapped to a NAS device and are attached to a backup set.

Yes, you can restore data to a share in a different administrative group, provided:

A backup set comprises of a content rule, backup policy, and NAS proxy. You can use different combinations of these components to perform efficient backups and optimize the available bandwidth. For example, you can back up PDF and .txt files using one backup set and configure another backup set to back up .xls and image files. You can also use different policies to back up data at different frequencies.

No, you cannot copy a backup set to the same or different share. For a NAS share, you can create multiple backup sets with exactly same configurations (such as content rule, backup policy, and NAS proxy) but with unique names. Across different NAS shares, you can create multiple backup sets with exactly same configurations, provided the proxy is mapped to the NAS device of the share.

Yes, provided the proxy is mapped to the NAS devices.

Druva backs up stub files as flat files with the size of zero bytes. However, Druva does not read the archived file on the archive destination the stub file refers to, and Druva does not backup the offline attributes that specify the archive destination. For example, if the file foo.txt is converted to a stub file with its contents moved to archive storage ,Druva will backup foo.txt stub as a flat file with size zero bytes without its content. Druva does not read the archived file that is stored on the archive storage. In addition, Druva does not backup the attributes that specify the archive destination where the actual archived content of the foo.txt file is stored.

A NAS device mapped to a specific NAS proxy is deleted. It is then re-added and mapped to the same proxy. The re-addition fails with the error "Unable to add device as none of the proxy reachable". To work around this issue, restart the Hybrid Workloads agent service on the NAS proxy.