Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Deduplication Guide
  3. MSDP cloud support
  4. Configuring FortKnox Google for NetBackup using the CLI
NetBackup™ Deduplication Guide

Configuring FortKnox Google for NetBackup using the CLI

Use the following procedure to configure FortKnox Google for NetBackup using the CLI.

Table: Steps for configuring FortKnox Google with the CLI

Steps

Task

Instructions

Step 1

Retrieve credentials.

Retrieve FortKnox credentials from your Cohesity NetBackup account manager.

Step 2

Add credentials using the Credential management option.

Log into NetBackup web UI and perform the following:

  1. On the left, click Credential management.

  2. On the Named credentials tab, click Add and provide the following properties:

    • Credential name

      The Credential name must use alphanumeric characters with hyphens or underscores and cannot contain spaces or illegal characters.

    • Tag

    • Description

  3. Click Next.

  4. In the drop-down, select FortKnox.

  5. Click FortKnox Google.

  6. Add the Refresh token.

  7. Select or add a role that can access this credential.

  8. Review the information and click Finish.

Step 3

Create an MSDP storage server.

See Configuring media server deduplication in NetBackup.

Step 4

Create a cloud instance alias.

Use the following examples depending on your environment:

  • Creating a FortKnox Google cloud instance alias:

    /usr/openv/netbackup/bin/admincmd/csconfig 
    cldinstance -as -in 
    FortKnox-Google 
    -sts <storage server> 
    -lsu_name <lsu name>
  • Creating an FortKnox Google Cold Vault cloud instance alias

    /usr/openv/netbackup/bin/admincmd/csconfig 
    cldinstance -as -in 
    FortKnox-Google -sts <storage server> 
    -lsu_name <lsu name> -storage_tier 
    FortKnox-Google-Cold-Vault
    
    

The cloud alias name is <storage server>_<lsu name>, and is used to create a bucket.

Step 6

Create a configuration file, then run nbdevconfig command.

Configuration file content for adding a new cloud LSU (configuration setting and description):

  • V7.5 "operation" "add-lsu-cloud" string - Specifies the value "add-lsu-cloud" for adding a new cloud LSU.

  • V7.5 "lsuName" " " string - Specifies the LSU name.

  • V7.5 "cmsCredName" " " string - Specifies the Credential name created using credential management.

  • V7.5 "lsuCloudBucketName" " " string - Specifies the cloud bucket name.

  • V7.5 "lsuCloudBucketSubName" " " string - Multiple cloud LSUs can use the same cloud bucket. This value distinguishes different cloud LSUs.

  • V7.5 "lsuEncryption" " " string - Optional value and the default is NO. Sets the encryption property for the current LSU.

  • V7.5 "lsuKmsEnable" " " string - Optional value and the default is NO. Enables KMS for the current LSU.

  • V7.5 "lsuKmsKeyGroupName" " " string - Optional value. Key group name is shared among all LSUs. Key group name must have valid characters: A-Z, a-z, 0-9, _ (underscore), - (hyphen), : (colon), . (period), and space.

  • V7.5 "lsuKmsServerName" " " string - Optional value. KMS server name is shared among all LSUs.

  • V7.5 "lsuKmsServerType" " " string - Optional value.

Note:

All encrypted LSUs in one storage server must use the same keygroupname and kmsservername. If you use the nbdevconfig command to add a new encrypted cloud LSU and one exists in this MSDP, the keygroupname must be the same as the keygroupname in the previous encrypted LSU.

After you create the configuration file, run the nbdevconfig command:

/usr/openv/netbackup/bin/admincmd/nbdevconfig 
-setconfig -storage_server <storage server> 
-stype PureDisk 
-configlist <configuration file path>

Note:

The parameter <storage server> must be the same as the parameter <storage server> in Step 4.

Step 7

Create disk pool.

Create disk pool by running the nbdevconfig command. The following are examples of using the nbdevconfig command:

Example 1:

/usr/openv/netbackup/bin/admincmd/nbdevconfig 
-previewdv -storage_servers <storage server name> 
-stype PureDisk 
| grep <LSU name> > /tmp/dvlist

Example 2:

/usr/openv/netbackup/bin/admincmd/nbdevconfig 
-createdp -dp <disk pool name> 
-stype PureDisk -dvlist /tmp/dvlist 
-storage_servers <storage server name>

Note:

You can also create the disk pool from the NetBackup web UI or NetBackup Administration Console.

Step 8

Create storage unit.

Create storage unit by using bpstuadd command. The following are examples of using the bpstuadd command:

/usr/openv/netbackup/bin/admincmd/bpstuadd 
-label <storage unit name> 
-odo 0 -dt 6 -dp <disk pool name> 
-nodevhost

Note:

You can also create the storage server from the NetBackup web UI or NetBackup Administration Console.

Note:

Use the web UI and update the refresh token within Credential management.

About msdpcldutil changes for FortKnox Google

To use this utility, you must create a credential name using the NetBackup web UI and also create a cloud alias using the csconfig command similar to the following example:

/usr/openv/netbackup/bin/admincmd/csconfig cldinstance 
-as -in FortKnox-Google -sts  <storage_server_name>
-stype PureDisk -lsu_name test101

Successfully added storage server(s): <storage_server_name>_test101

Added the --enable_oauth option to use for FortKnox Google. Additionally, if the -enable_oauth option is used you must export the following environment variables:

  • MSDPC_MASTER_SERVER - This option is name of the NetBackup primary server.

Example output

export MSDPC_PROVIDER=vgoogle
export MSDPC_REGION="US-EAST1"
export MSDPC_ENDPOINT="storage.googleapis.com"
export MSDPC_MASTER_SERVER=<primary server>
export MSDPC_ALIAS=<storage_server_name>_test101
export MSDPC_CMS_CRED_NAME=<cms_cred_name>

/usr/openv/pdde/pdcr/bin/msdpcldutil create -b rv-worm1 
-v dv-worm --mode GOVERNANCE --min 1D --max 3D 
--live 2023-03-31 --enable_oauth

If a cred file is used for the msdpcldutil command, do not add any quotes to the values.

Feedback

Was this page helpful?
Previous

Configuring FortKnox Google for NetBackup

Next

Migrating from standard authentication to token-based authentication for Recovery Vault

Feedback

Was this page helpful?