Search <book_title>...

Veritas Access 7.3.0.1 NetBackup Solutions Guide

Last Published: 2017-11-20

Product(s): Access (7.3.0.1)

Creating an S3 bucket on Veritas Access for storing deduplicated backup data from NetBackup

To create an S3 bucket on Veritas Access for storing deduplicated backup data from NetBackup

Log on to the Veritas Access GUI as the master user using the following URL:
https://Veritas Access Management console IP:14161/.
You can obtain the Veritas Access Management console IP by logging on to the CLISH using the su - master command on the Veritas Access cluster.
Create a storage pool for the S3 buckets.
Click NAS Infrastructure in the GUI navigation on the left.
Select the disks that you want to use for the S3 bucket, and click the Add to Storage Pool button to invoke the wizard for storage pool creation.
Follow the steps in the wizard for creating a new storage pool or adding the disks to an existing pool.
Click Settings > Service Management > Configure Active Directory to configure AD.
Enter the required information, such as the DNS Domain, DNS Name Servers, AD Domain, AD Domain Controller, and the AD Admin and Password.
Click Settings > S3 Management to configure and enable the S3 server.
Edit the default parameters that are required for the S3 server, such as the storage pool name, underlying S3 bucket layout, and the default size of the bucket.
Double-click S3 Server Status to start the S3 server.
Log out from the GUI, and log in again as an AD user.
Note:
Log in using the domainname\\username format.
Click on the Create keys button to generate the access key and the secret key for the Veritas Access S3 bucket.
Save the access key and secret key in a safe location, as Veritas Access does not allow retrieval of keys after initial creation.
Log out from the GUI, and log on again as the master user.
Registration of Amazon Web Services (AWS) is optional, and is only required in case you need to add an AWS cloud as a storage tier. Without this, backups are stored locally in Veritas Access S3 buckets.
Click Settings > Cloud Storage Registration > Add Cloud Subscription to register the AWS cloud service.
Enter information for the cloud service provider, name of subscription, access key, and secret key.
Activate the long-term data retention (LTR) policies.
Click Policies > LTR Policy.
Click Activate for either the LTR On-Premises + Cloud policy or the LTR On-Premises policy and provide the storage pool when prompted.
Provision the NetBackup bucket using the policy.
Under Quick Actions, click Provision Storage. Select S3 Storage for NetBackup and click Next.
Provide the bucket size, underlying layout of the bucket, the access key, and the secret key of the Veritas Access S3 server generated as the AD user in step 6.
If you selected the LTR On-Premises + Cloud policy, add information such as which data should be moved to the AWS cloud tier, AWS region, cloud tier type (S3/Glacier), and when the data movement to the cloud should occur.
Monitor the progress of the task under Recent Activity.
Make a note of the scale-out file system name that was used for the bucket creation.
Click File Systems.
For the scale-out file system that is created, ensure that the S3 Bucket column displays Yes to indicate that the S3 bucket is enabled.
You may need to wait for some time for this change to be reflected in the GUI.
Right-click the ellipses (additional options), and click Configure LTR Script.
A pop-up window appears with the following options:
Do you want to Run the LTR script?
Do you want to Download the LTR script?
- Select the Do you want to Run the LTR script? option if OpenDedup is hosted on Veritas Access. You will be prompted to enter you access key. Enter the access key and click Next. Wait for the task to be completed.
  The rest of the configuration steps are done automatically.
  After the configuration is completed successfully, the output message shows the port number on which the OpenDedup volume is mounted on Veritas Access. This port number is required later during OST configuration.
  Note:
  This operation creates/expands a new file system named odd_cache_fs to store the OpenDedup cache data. The default size of this file system is 12 GB. Veritas recommends that you expand the file system to the required size. See the OpenDedup documentation for more details.
  Go to step 20.
- Select the Do you want to Download the LTR script? option if OpenDedup is hosted on the NetBackup master and/or media server. Click Next. Wait for the task to be completed.
Copy the LTR script to the host where OpenDedup is installed. It can be the host where the NetBackup media server is installed.

Run the downloaded LTR script. The LTR script requires the Veritas Access S3 keys (access and secret key) as arguments that were generated as the AD user.

The LTR script creates the OpenDedup file system and prompts for the entry in the /etc/hosts file for the bucket to IP address mapping.

Output of LTR script execution:

[root@host1 ~]# sh LTRscript_<fsname/volname>_<bucketname>.sh 
<Access key> <Secret Key> 
===================================================================
Insert the below details in /etc/hosts file
10.100.100.1 4f459a2d-736e-4be5-9c5a-f821fbc198fds3bucket.s3.access
===================================================================
Attempting to create SDFS volume ...
Volume [S3fs1497356186] created with a capacity of [10.00GB]
check [/etc/sdfs/S3fs1497356186-volume-cfg.xml] for configuration 
details if you need to change anything

Note:

The volume name highlighted above and its equivalent .xml file are used to mount and update the SDFS volume parameters in later steps.

Add the IP associated with the virtual hosted-style bucket name (generated from the LTR script) in the /etc/hosts file on the media server.

Mount the SDFS volume under /opendedupe/volumes/ on the host where OpenDedup is installed.

# mkdir /opendedupe/volumes/filesystem_name

# mount -t sdfs filesystem_name /opendedupe/volumes/filesystem_name

The mount command mounts a bucket on the Veritas Access cluster or the NetBackup media server.

Note:

After mounting the SDFS volume, it will start listening on a specific port, usually starting from 6442.

Port information can be found using the mount command.

Example:

[root@host1 ~]# mount | grep opendedupe
sdfs:/etc/sdfs/S3fs1497346133-volume-cfg.xml:6443 on 
/opendedupe/volumes/S3fs1497346133 type fuse 
(rw,nosuid,nodev,allow_other,allow_other)
sdfs:/etc/sdfs/S3fs1497258807-volume-cfg.xml:6442 on 
/opendedupe/volumes/pool1 type fuse 
(rw,nosuid,nodev,allow_other,allow_other)

(Optional) Add the volume to fstab by adding the following line in: /etc/fstab.
```
filesystem_name /opendedupe/volumes/filesystem_name sdfs defaults 0 0
```
Update the URL tag in the /etc/sdfs/ostconfig.xml present on the NetBackup media server based on the following two cases:
Use case 1: OpenDedup on a NetBackup server
```
<URL>
http://localhost:6442/
</URL>
OpenDedup on separate Media server
<URL>
http://<media server hostname>:6442/
</URL>
```
Use case 2: OpenDedup on Veritas Access
```
<URL>
http://<Veritas Access server hostname>:<port number that was 
																																								specified in step 14>/
</URL> 
```
Note:
The Veritas Access server hostname should be DNS-resolvable and reachable from the NetBackup server. This should be the same node in the Veritas Access cluster where the SDFS volume is mounted in step 18.