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. About instant access for object storage
NetBackup™ Deduplication Guide

About instant access for object storage

The following table describes the platforms supported by instant access for object storage.

Table: Supported platforms

Supported platforms

Description

Azure Kubernetes Service (AKS)

This platform is supported and enabled by default.

Amazon Elastic Kubernetes Service (EKS)

This platform is supported and enabled by default.

VM in Azure or AWS (Cloud Build-Your-Own, BYO-In-Cloud)

This platform is supported. You must manually enable this option.

MSDP on-premises (BYO, Flex media server, NetBackup appliance)

This platform is supported. You must manually enable this option. The connection from MSDP to object store must have good network bandwidth and latency.

The instant access for object storage is enabled by default on the AKS/EKS platforms. If instant access is not enabled by default, you must manually perform the following steps to enable it:

  1. Add the instant-access-object-store = 1 option into the /etc/msdp-release file on storage server.

  2. On the primary or media server, run the following commands to verify that the IA_OBJECT_STORE name is in the extendedcapabilities option.

    Example:

    nbdevconfig -getconfig -stype PureDisk 
    -storage_server your_storage_server_name 
    |grep IA_OBJECT_STORE
  3. On the primary or media server, run the following commands to reload the storage server attributes:

    nbdevconfig -getconfig -stype PureDisk 
    -storage_server your_storage_server_name > /tmp/flags
    nbdevconfig -setconfig -stype PureDisk 
    -storage_server your_storage_server_name -configlist /tmp/flags

Feedback

Was this page helpful?
Previous

Configure a disk pool using Azure service principal

Next

Upgrading to NetBackup 10.3 and cluster environment

Feedback

Was this page helpful?