Technical White Paper NetBackup 8.1 and later. NetBackup in the AWS Cloud: Required setup to use Amazon EFS as the NetBackup CloudCatalyst cache

Transcription

1 Technical White Paper NetBackup 8.1 and later NetBackup in the AWS Cloud: Required setup to use Amazon EFS as the NetBackup CloudCatalyst cache 1

2 Contents 1.0 Summary Terminology Configuring NetBackup CloudCatalyst to use Amazon EFS as the CloudCatalyst cache Configuring a Virtual Private Cloud (VPC) Configuring Identity and Access Management (IAM) Configuring an Elastic File System (Amazon EFS) Launching an Elastic Compute Cloud (Amazon EC2) Instance... 6 Configuring the instance details... 6 Mounting the EFS to the CloudCatalyst media server Configure CloudCatalyst on the EC2 instance Saving the configuration files necessary to replace a CloudCatalyst media server Replacing the CloudCatalyst media server by creating a new EC2 instance Creating a new EC2 instance For more information

3 1.0 Summary By default, Veritas NetBackup CloudCatalyst media servers use NetBackup ESFS as the file system for CloudCatalyst operations. When NetBackup 8.1 or later is deployed in Amazon EC2, whether installed manually or by using AMI templates, the NetBackup ESFS file system must be installed on Amazon EFS. Amazon EFS is designed for high availability, which helps ensure that operations are minimally impacted if a CloudCatalyst media server instance needs replacing. Note: CloudCatalyst works best when using a file system with high levels of availability, durability, and scalability. Amazon requires EFS for this solution. This document describes the following procedures: Configuring NetBackup CloudCatalyst to use Amazon EFS as the CloudCatalyst cache. (See page 4.) This procedure is required for the NetBackup ESFS file system to be installed on Amazon EFS. Saving the configuration files necessary to replace a CloudCatalyst media server. (See page 13.) Replacing the CloudCatalyst media server by creating a new EC2 instance. (See page 13.) Note: This document assumes that you already have set up a NetBackup 8.1 or later master server instance in EC2. Your environment may vary. 2.0 Terminology Amazon Elastic Block Store (Amazon EBS): A storage file system that provides persistent block storage volumes that can be used with Amazon EC2 instances in the AWS Cloud. However, do not use this storage for CloudCatalyst operations in Amazon EC2. Amazon Elastic Compute Cloud (Amazon EC2): A web service that provides secure, resizable compute capacity in the cloud. Amazon Elastic File System (Amazon EFS): A storage file system that provides scalable storage that can be used with Amazon EC2 instances in the AWS Cloud. This is the only supported storage for CloudCatalyst operations in Amazon EC2. Amazon Machine Image (AMI): A file that provides the information necessary to launch an instance (or virtual server) in the Amazon cloud. NetBackup Extendable Storage File System (NetBackup ESFS): The NetBackup CloudCatalyst database used for CloudCatalyst operations. CloudCatalyst uses the NetBackup Extendable Storage File System Service (vxesfsd) and its subcomponents to move and manage files in the local cache directory and the cloud. 3

4 3.0 Configuring NetBackup CloudCatalyst to use Amazon EFS as the CloudCatalyst cache Begin by logging into the AWS Management Console and configure the following services in the order listed below. 4

5 3.1. Configuring a Virtual Private Cloud (VPC) Configure a Virtual Private Cloud according to your needs. In this example, the NetBackup master, media server, and EFS instance are installed in the same VPC Configuring Identity and Access Management (IAM) Create the users for your environment Configuring an Elastic File System (Amazon EFS) 1. Create an EFS file system within the appropriate VPC. 2. Configure file system access: Connect the EFS instance to the appropriate Availability Zone. Our example keeps all resources in the same security group. 5

6 3.4. Launching an Elastic Compute Cloud (Amazon EC2) Instance This instance will become the NetBackup CloudCatalyst media server. Configuring the instance details NetBackup CloudCatalyst media servers run on Red Hat Enterprise Server 7 Update 3 or later. 1. Using the EC2 Dashboard in the AWS console, click Launch Instance. 2. On the Choose an Amazon Machine Image (AMI) page, click an AMI for Red Hat Enterprise Linux 7.3 or later, and then click Select. 6

7 3. On the Choose an Instance Type page, select an appropriate size for your performance requirements. 4. Click Next: Configure Instance Details. 5. On the Configure Instance Details page: Under Network, select the appropriate VPC. The EFS instance and NetBackup media server must reside in the same VPC. Enable Auto-assign Public IP to access the instance from your desktop. 7

8 6. Click Next: Add Storage. 7. On the Add Storage page, select the storage size and volume type. Select an appropriate EBS volume size. 8. Click Next: Add Tags. 8

9 9. On the Add Tags page, add tags if desired. However, tags are not required. 10. Click Next: Configure Security Group. 11. On the Configure Security Group page, add NFS to the security group for the instance. You cannot mount EFS if NFS is not added to the security group inbound configuration. In this example, we ve allowed members of the security group NFS access. 12. Click Review and Launch. 9

10 13. On the Review Instance Launch page, review the EC2 instance, and then click Launch. The instance is available in approximately 15 minutes. 14. Change the host name of the machine to a fully qualified domain name (FQDN) using the following procedure: Mounting the EFS to the CloudCatalyst media server 1. In the Amazon AWS Management Console, in the list of AWS service, click EFS. 2. Click the appropriate EFS instance. A list of file systems appears. Expand your EFS instance to see the details. 3. The mount target is automatically created by AWS. Take note of the DNS name for use when mounting. 4. Click Amazon EC2 mount instructions to see the mount command. 10

11 5. Follow the instructions to mount the EFS instance to the NetBackup CloudCatalyst media server. Note: In place of mount point efs, the following example uses mount point msdpc. a. Open an SSH client and connect to the EC2 instance. b. To install the nfs-utils package, type: sudo yum install -y nfs-utils c. To create a new directory on the EC2 instance, in our example, type: sudo mkdir /msdpc d. To mount your file system using the DNS name, copy the command line from step 3 of Mounting your file system. We ve replaced efs with /msdpc in this example. sudo mount -t nfs4 -o nfsvers=4.1,rsize= ,wsize= ,hard,timeo=600,retrans=2 DNS_name:/ /msdpc Note: The DNS_name varies in the mount command per EFS instance. The DNS_name appears in the File systems details (see step 3 in this procedure). 6. To make sure that EFS mounts automatically when the instance reboots, update the /etc/fstab file. Using sudo vi, add a line to the file, similar to the following: mount-target-dns:/ efs-mount-point nfs4 nfsvers=4.1,rsize= ,wsize= ,hard,timeo=600,retrans=2,_netdev 0 0 For example: fs-xxxxxxxx.efs.us-east-1.amazonaws.com:/ /msdpc nfs4 nfsvers=4.1,rsize= ,wsize= ,hard,timeo=600,retrans=2,_netdev 0 0 Note: This process is also described in the following Amazon article: 11

12 7. Make any other changes to the instance that your organization may require. Configure CloudCatalyst on the EC2 instance Install NetBackup 8.1 or later on the EC2 instance. (This is the NetBackup CloudCatalyst media server.) During the CloudCatalyst configuration, as part of the Cloud Storage Server Configuration Wizard, enter the EFS mount point as the CloudCatalyst Local cache directory. In the example below, the EFS mount point is /msdpc 12

13 4.0 Saving the configuration files necessary to replace a CloudCatalyst media server Save the configuration files that are necessary to replace an existing CloudCatalyst media server: hostname.cfg and vxesfsd. The files are found in the following locations: /usr/openv/lib/ost-plugins/hostname.cfg /usr/openv/esfs/bin/vxesfsd After saving these files to a different location, shut down the media server. Proceed to Replacing the CloudCatalyst media server by creating a new EC2 instance on page Replacing the CloudCatalyst media server by creating a new EC2 instance This section describes replacing a NetBackup CloudCatalyst media server instance with a new EC2 instance. This figure shows an example of a NetBackup CloudCatalyst configuration in a VPC: 13

14 The following figure shows that after the original media server is removed from the VPC, the configuration is updated to use a new EC2 instance for the CloudCatalyst media server. This section describes how that is done Creating a new EC2 instance Create a new EC2 instance that will become the new CloudCatalyst media server. The example in this document uses the same name for both the old and the new media servers. 1. Launch a new EC2 instance as described in Configuring the instance details on page Open an SSH client and connect to the EC2 instance. Use the same mount point as you did previously. (In this example, /msdpc.) 3. If the shutdown was not orderly, a LOCK file may exist in the CloudCatalyst cache directory. The LOCK file must be deleted. In this example, the location is /msdpc/ [root@cc-ms2 esfs_database]# ls -l /msdpc/cache/fsdb/lock -rw-r--r--. 1 root root 0 Sep 21 02:50 /msdpc/cache/fsdb/lock [root@cc-ms2 esfs_database]# rm -f /msdpc/cache/fsdb/lock 4. Change the host name of the new instance to match the name of the original server, as follows: hostnamectl set-hostname static FQDN_host_name of_cc echo preserve_hostname: true >> /etc/cloud/cloud.cfg For example: 14

15 Notes: You must include the echo command as shown above. To assign a static host name to a private Amazon EC2 instance running RHEL 7, see the following article: 5. Configure the networking for the new server to match the old server. If not using DNS or Elastic IPs, update the following hosts file: The /etc/hosts file on the NetBackup master server if the IP address for the CloudCatalyst media server has changed. The local /etc/hosts file on the CloudCatalyst media server. In the following example, the media server pings the master server, updates the /etc/hosts file, and then pings the master server again: 6. Reboot the CloudCatalyst media server for the settings and host name changes to take effect. 7. Reinstall NetBackup on the new instance of the CloudCatalyst media server. 8. On the master server, generate a re-issue token for the installation for the CloudCatalyst media server: a. In the NetBackup Administration Console, expand Security Management. b. Select the Certificate Management or the Host Management node. c. In the right pane, select the host that requires a reissue token. d. From the Actions menu, select Generate Reissue Token. e. Complete the fields in the Create Reissue Token dialog and click Create. f. The reissue token appears in a dialog. Select Copy to save the token value to the clipboard. g. Deploy the token on the media server to obtain another host ID-based certificate. 15

16 9. Replace the configuration files that were previously saved. /usr/openv/lib/ost-plugins/hostname.cfg /usr/openv/esfs/bin/vxesfsd 10. Change the permissions of vxesfsd to match the original settings, as shown below: 11. Copy and save the MSDP configuration file: /etc/pdregistry.cfg 12. Delete the existing pdregistry.cfg file and create a symbolic link to /msdpc/storage/etc/pdregistry.cfg The following example moves the file and creates a symbolic link: mv /etc/pdregistry.cfg /ssdfs/original.pdregistry.cfg ln -s /msdpc/storage/etc/pdregistry.cfg /etc/pdregistry.cfg 13. Restart all of the services on the CloudCatalyst media server. 14. Confirm that vxesfsd is running and mounted. For example, use df -h, as shown below: 16

17 6.0 For more information The following documents provide useful information about NetBackup CloudCatalyst and the procedures described in this document: Veritas NetBackup 8.1 Deduplication Guide, for detailed information about NetBackup CloudCatalyst. How do I assign a static hostname to a private Amazon EC2 instance running RHEL 7 or Centos 7? Configuring an EFS File System to Mount Automatically at EC2 Instance Launch. 17

18 About Veritas Technologies LLC. Veritas Technologies LLC enables organizations to harness the power of their information, with solutions designed to serve the world s largest and most complex heterogeneous environments. Veritas works with 86 percent of Fortune 500 companies today, improving data availability and revealing insights to drive competitive advantage. Visit our website Veritas World Headquarters 500 East Middlefield Road Mountain View, CA (650) Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This document is provided for informational purposes only and is not intended as advertising. All warranties relating to the information in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice. 18