System Requirements for Amazon Redshift

To back up and restore Redshift data on an Amazon application, verify that your environment has the required software and a firewall.

Software Requirements

  • Packages that are required on access nodes:

    • Virtual Server Agent

    • Media Agent

  • For information on supported Amazon EC2 instances as access nodes, see Supported Amazon EC2 Instance Families.

  • Access nodes that you run backup and restore operations on must have one of the following operating systems:

Linux

Operating system

Processor architecture

Amazon Linux 2023 AMI

  • 64-bit (Arm) (recommended)

  • 64-bit (x86)

Amazon Linux 2 AMI (HVM) - Kernel 5.10, SSD Volume Type

  • 64-bit (Arm) (recommended)

  • 64-bit (x86)

Commvault Cloud Cloud Access Node Arm BYOL: Amazon Linux AWS Graviton

  • 64-bit (Arm)

Commvault Cloud Cloud Access Node BYOL: Red Hat Enterprise Linux AWS Graviton

  • 64-bit (Arm)

Oracle Enterprise Linux 9.x, 8.x

  • x64

  • Compatible processors

Red Hat Enterprise Linux (RHEL) 9.x, 8.x

  • x64

  • Compatible processors

Rocky Linux 9.x, 8.x

  • x64

  • Compatible processors

Windows

Operating system

Processor architecture

Windows Server 2022, 2019, 2016

  • x64

  • Compatible processors

Hard Drive

A minimum of 100 GB of disk space is recommended. If a staging directory is required on the access node, the actual space needed will depend on the database being backed up and the configured settings.

Network Connectivity

  • Access nodes must have Layer 3 network connectivity to the upstream MediaAgent on port 8403. If the MediaAgent and the access node are in different accounts or in different Virtual Private Clouds (VPCs), you can configure Amazon VPC peering. For information, see VPC peering basics in the AWS documentation.

  • Access nodes must have connectivity to regional and global AWS service endpoints. For information, see Requirements for Connectivity to AWS Service Endpoints.

Firewall Requirements

  • If you have network configuration enabled on the access nodes, before you deploy the Linux proxy, configure a firewall on the cloud proxy and on-premises. For more information, see Configuring a Firewall to Install the Virtual Server Agent on a Cloud VM or Instance.

  • Access node machines must be able to connect to redshift.region.amazonaws.com, or the Regional equivalent if the AWS account is restricted to specific Regions. To route communications through an HTTP or HTTPS proxy, provide proxy information in the CommServe Control Panel, on the HTTP Proxy tab of the Internet Options dialog box. To use an HTTPS proxy, you must provide authentication details.

×

Loading...