How to configure a Linux media server as a CloudCatalyst storage server

Use the following procedure if you use a Linux media server (non-appliance) as a CloudCatalyst storage server.

This procedure assumes that the preferred use case is configured. The preferred use case is described in the following topic:

See Optimized duplication is used to copy data from an MSDP storage server to a CloudCatalyst storage server (preferred use case).

Table: Configuration steps for a media server (non-appliance)

Step	Task	Where to configure	Procedure
Step 1	Configure an MSDP storage server (source)	One or more media servers	A NetBackup environment may contain one or more media servers that serve as source MSDP storage servers for CloudCatalyst storage servers. See About MSDP optimized duplication within the same domain. See About the media servers for MSDP optimized duplication within the same domain.
Step 2	Create an account with a cloud service provider	Cloud service provider	Make sure that you have an account with a cloud service provider and that you know the user name and password.
Step 3 (Conditional)	Deploy host name-based certificates	Master server	This step is applicable and required for media server versions 8.0 to 8.1.2 only. Deploy a host name-based security certificate for the media server that is configured as the CloudCatalyst storage server. /usr/openv/netbackup/bin/admincmd/bpnbaz - ProvisionCert host_name Restart the services on the media server after generating a certificate.
Step 4	Configure a CloudCatalyst storage server (target)	Media server	A CloudCatalyst storage server is the target for the optimized duplication. It is a dedicated media server for cloud storage. Run the Cloud Storage Server Configuration Wizard in the Java GUI selecting the Enable NetBackup CloudCatalyst check box and entering a path for the local cache directory. The administrator configures a local cache directory as part of configuring a CloudCatalyst storage server. The minimum size for this directory is 4 TB, however, an environment may see benefits from a larger local cache directory. See About the CloudCatalyst cache. A NetBackup environment may contain one or more media servers that serve as CloudCatalyst storage servers. There should be one CloudCatalyst storage server for each different cloud service provider that is used in the environment.
Step 5	Ensure that a common media server is configured to allow optimized duplication	Media server	If the CloudCatalyst media server was added as a load balancing media server during the MSDP storage server wizard (Step 1), pull optimized duplication is configured. See the following topic for configuration considerations: See Configuring source control or target control optimized duplication for CloudCatalyst.
Step 6	Protect the MSDP data and catalog	Media server	Create an MSDP catalog backup policy for every MSDP storage server and CloudCatalyst storage server in the environment. See About protecting the MSDP catalog. See Configuring an MSDP catalog backup. Note: After the MSDP catalog backup policy is created, it is inactive. Assign a storage unit to it and then make it active by setting the Go into effect at option on the Attributes tab. Save a configuration file for every MSDP storage server and CloudCatalyst storage server in the environment. See About saving the MSDP storage server configuration.
Step 7	Configure a storage lifecycle policy	Master server	See Configuring a storage lifecycle policy for NetBackup CloudCatalyst. The backup and the duplication jobs can also be run manually from the NetBackup Administration Console or by using the bpduplicate command.
Step 8	Configure a backup policy	Master server	Create a backup policy that uses the SLP. In the Policy storage field of the policy Attributes tab, select the SLP. See About MSDP backup policy configuration. See Creating a backup policy.

How to configure a Linux media server as a CloudCatalyst storage server

Feedback

Feedback