Upgrade Snapshot Manager deployment using new AWS CloudFormation stack
Note:
Enter the above collected information against the respective attributes in Snapshot Manager Upgrade Configuration.
Deploy the product
On clicking the Action button, you will see an option to Launch CloudFormation Stack, which will lead to the Launch page. Another option is, after searching for the product, you may directly on Launch CloudFormation Stack, which will lead to the Launch page. Select the delivery method, software version and region from the dropdown appearing on the screen.
Click on Continue to Launch button after selecting the above fields.
On the next page, you can review the configuration selected and choose how you wish to launch the software.
From the "Choose Action" drop-down, select Launch CloudFormation and click on Launch.
This will take you to the CloudFormation service page, where template source would be pre -filled. Click on Next.
Fill in the CloudFormation Template
Stack Name
Unique stack name has to be provided. The name you specify would be the name of the stack created.
Snapshot Manager System Configuration
EC2 Instance type (Mandatory): Select a type from the drop down that appears. The default being t3.large.
Volume Size (Mandatory): Size of the volume which would be created as part of stack for CP metadata. Default is 60 GB.
IAM role (Optional): Specify IAM role name, which would be attached to the CP instance. Otherwise it would be created with the required permissions and would be attached to the CP instance.
Snapshot Manager Upgrade Configuration
EBS Volume ID (Optional): This is used in case of upgrade. Existing Volume ID which has Snapshot Manager metadata must be specified, which would be attached to the Snapshot Manager instance.
Volume Snapshot (Optional): This is used in case of upgrade. Existing Snapshot Manager metadata disk's snapshot ID must be specified. Volume would be created and attached to the Snapshot Manager instance from the snapshot.
Network Configuration
Snapshot Manager VPC (Mandatory): Select a Virtual private network where you want to deploy Snapshot Manager instance. The drop-down lists down the VPC IDs in the region where you are deploying Snapshot Manager.
Snapshot Manager Subnet (Mandatory):From the drop down, select the ID of existing subnet in your VPC where you want to deploy Snapshot Manager instance. The drop -down lists down the subnet IDs in the region where you are deploying Snapshot Manager.
Availability Zone (Mandatory): From the drop down that appears, choose a zone in which the volume or snapshot exists for upgrade
Snapshot Manager Domain Name (Mandatory): Domain name must correspond to an existing Route53 Hosted Zone associated with this VPC, or it must be a new domain for which a Hosted Zone will be created with the deployment.
Inbound Access CIDR(Mandatory):The Inbound Access CIDR would be used to create a Security Group for Snapshot Manager. The traffic from the CIDR mentioned would be allowed to the Snapshot Manager.
Elastic IP (Optional):Specify an Elastic IP which was dissociated from the previous deployment in case the selected network type is Public, which would be assigned to Snapshot Manager instance.
HTTP Proxy (Optional):Specify HttpProxy environment variable to configure Snapshot Manager with proxy server
HTTPS Proxy (Optional): Specify HttpsProxy environment variable to configure Snapshot Manager with proxy server.
No Proxy (Optional): Specify NoProxy environment variable to configure Snapshot Manager with proxy server.
Snapshot Manager Configuration
Snapshot Manager server name (Optional): Provide the server name with which you want to enable the access to Snapshot Manager. The installer uses this name to generate a TLS certificate for the Snapshot Manager host.
Security Configuration
SNS Topic ARN (Optional): The ARN of a SNS topic to receive notifications when ASG scales to address the disaster.
Snapshot Manager Recovery Notification Configuration
SNS Topic ARN (Optional): The ARN of a SNS topic to receive notifications when ASG scales to address the disaster.
Snapshot Manager KMS Configuration
Customer's Mater Key ID (Optional): ID of the customer's master key to configure KMS with Snapshot Manager, if KMS need to be configured.
Customer's Master Key's Region (Optional): The region in which the above mentioned key is present. Optional, if the region is same as the region in which Snapshot Manager is deployed.
Snapshot Manager Registration with NetBackup
Provide a Fully Qualified Domain Name (FQDN) of the existing the primary server to which the Snapshot Managerserver needs to be associated. Configuration fails if the FQDN is not resolvable from this Snapshot Managerserver.
NetBackup server name and NetBackup API Key : Provide a valid API key generated from the existing the primary server to validate the communication between the primary server and the Snapshot Managerserver. The user generating API keys must have permission to add the Snapshot Manager server.
Confirm and Create the stack
In the next page, user needs to specify information such as Tags, Permissions, Rollback Triggers, and some other additional options for the stack, like notification options and a stack policy.
The next page allows you to review your inputs and asks for the acknowledgment that the AWS CFT may create some IAM resources.
Click on the button.
This will now take you the page where all the stacks are listed. You can view the status of the stack you just created.
Perform the following steps before you proceed with the upgrade:
- Check for the status of the CloudFormation stack created.
- Delete the stack created by the previous deployment.
- After the stack creation is successful, perform any one of the action from the below:
a. If the hostname of the Snapshot Manager server remains same, enable the Snapshot Manager server from the NetBackup primary server.
b. If the hostname of the Snapshot Manager server is changed, you will have to upgrade the NetBackup to the latest version and then again add the Snapshot Manager to the upgraded NetBackup primary server.