❗ Important
This feature has limited availability. To know more about limited availability and sign up for this feature, contact your Account Manager.
Considerations for adding a NAS proxy
Druva supports the backup of the AWS S3 bucket using the NAS proxy. You must install the NAS agent on the Linux/Ubuntu EC2 instance.
📝 Note
The NAS agent backs up the AWS S3 objects inside the AWS S3 bucket. NAS agent restores the backed-up AWS S3 objects to any available AWS S3 bucket.
Step 1: Installing a NAS proxy
Log in to the Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization where you want to add the NAS proxy, and then select the workload.
The Get Started page is displayed if no NAS devices have been configured so far. On the Get Started page, under Deploy a NAS proxy, you will see No Proxy Registered message is displayed. Click Add NAS Proxy.
If NAS proxies and NAS devices (AWS S3 vendor) have already been configured, you can add more proxies. In the left navigation pane, click All Backup Proxy Pools, and click Add Proxy.
In the Add NAS Proxy dialog box, click Check Prerequisite and ensure that the server meets the prerequisites for the NAS proxy installation.
📝 Note
For AWS S3 backup and restore, only Linux/Ubuntu proxies are supported.
Download the Linux/Ubuntu agent on the provisioned EC2 machine that will act as the NAS proxy.
Installing the NAS proxy on a Linux server
The NAS proxy handles the backup and restore of the AWS S3 bucket. Install the NAS proxy on a Linux server if you want to back up AWS S3 buckets.
Log in as the root user on the Linux server where you want to install the NAS proxy.
Navigate to the location where you've downloaded the NAS proxy installer.
Run the following command depending on the OS of the server
RHEL, CentOS, or SLES:
rpm –ivh <package name>where
<package name>is the installer name with its extension.Ubuntu:
dpkg –i <package name>where
<package name>is the installer name with its extension.
Enter input as [yes/no] to enable signature verification.
📝 Note
By default, the input option for enabling signature verification is [no].
The Enable Signature Verification option ensures the integrity and authenticity of binaries. It also prevents the execution of any altered binaries, thereby safeguarding against malicious modifications or tampering with the package.
(Optional) You can also verify the integrity and authenticity of the package. See Package Signature Verification for more details.
Step 2: Activating the NAS proxy
After you install the NAS proxy, you must activate it using the activation token generated on the Management Console at the time of adding the proxy. The token functions as a unique identifier and performs a one-time authentication of the NAS proxy. After activation, the NAS proxy establishes a persistent connection with Druva Cloud.
📝 Note
Whenever you add and activate a proxy, the newly added proxy goes to the Default Proxy Pool. The Default Proxy Pool cannot be deleted. However, you can move a proxy from the Default Proxy Pool to a different pool. For more information, see Change Backup Proxy Pool.
Activating the NAS proxy on a Linux Server
In the Add NAS Proxy wizard, under the Activate Proxy section, select a valid activation token. An activation token can be used to activate up to 25 NAS proxies and expires in 7 days. If all activation tokens have expired, Druva creates a Default Activation Token automatically when you click Add Proxy. If you want to create a new token, perform the following tasks:
Click Generate New Token to create a new token.
In the Generate Token dialog box, enter the following details, and click Generate.
In the Generate Token dialog box, click Done.
Select the newly generated token from the drop-down list under Activation Token.
In the Activate Proxy section, under Linux/Ubuntu Server, click Copy Command to copy the activation command.
On the Linux server, open the terminal and navigate to:
cd /opt/Druva/EnterpriseWorkloads/bin (for agent version 7.0.0 and later)Paste the copied command as explained below:
Public Cloud
EnterpriseWorkloadsAgent nas activate -t <token> -n <ProxyName>(for agent version 7.0.0 and later)For example:
EnterpriseWorkloadsAgent nas activate -t 67831-228-1762-591132241ce4fb2e14fca792cbf532f4a2359eb0bf1b96f82211373ebea7c23b -n WIN-RTG3
GovCloud
EnterpriseWorkloadsAgent nas activate -g -t <token> -n <ProxyName>(for agent version 7.0.0 and later)For example:
EnterpriseWorkloadsAgent nas activate -g -t 67831-228-1762-591132241ce4fb2e14fca792cbf532f4a2359eb0bf1b96f82211373ebea7c23b -n WIN-RTG3
In both the above commands, <activation token> is the activation token of the NAS proxy.
💡 Tip
The NAS proxy name is not case sensitive. You cannot have one NAS proxy registered as "ABC" and another as "abc". Druva will display the error message " Server display name already exists. Cannot register the server with same display name."
Next steps