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. Veritas NetBackup™ OpsCenter Administrator's Guide
  3. Installing OpsCenter
  4. About OpsCenter upgrade on Windows and UNIX
  5. About importing authentication settings during OpsCenter upgrade
  6. About OpsCenter upgrade scenarios with respect to OpsCenter AT
Veritas NetBackup™ OpsCenter Administrator's Guide

About OpsCenter upgrade scenarios with respect to OpsCenter AT

Table: OpsCenter upgrade scenarios describes various scenarios of OpsCenter upgrade:

Table: OpsCenter upgrade scenarios

Which installation scenario?

Which additional tasks are required?

What happens after the installation?

Fresh OpsCenter installation

None

The installer installs OpsCenter AT on the OpsCenter server host

OpsCenter uses its own OpsCenter AT for user authentication

Note:

If OpsCenter is deployed in a clustered mode, each OpsCenter node has OpsCenter AT configuration of its own. Each cluster node has embedded AT binary and all nodes share the same AT configuration and authentication data exists on a shared disk.

Upgrade to OpsCenter: Non-clustered setup and shared AT in previous OpsCenter version

None

The installer installs OpsCenter AT on the OpsCenter server host

OpsCenter uses its own OpsCenter AT for user authentication

The shared AT broker's data store is imported to OpsCenter AT broker's data store

Only OpsCenterUsers(vx ) domain users are imported to OpsCenter AT

All credentials of PureDisk and NBAC-enabled NetBackup are imported from remote AT to OpsCenter AT

All imported OpsCenterUsers(vx ) users can logon to OpsCenter after the installation.

Upgrade to OpsCenter: Non-clustered setup and remote AT in previous OpsCenter version

Pre-upgrade tasks: Export the shared AT broker's data to an XML file using the atutil utility

See Exporting authentication settings.

Note:

While copying the exported xml file, the DOS to UNIX conversion may be improper that may result in garbage characters in the xml file. This may cause failure of import. To avoid this, copy the xml file through FTP and with binary format.

Upgrade tasks: During OpsCenter upgrade, when prompted, import this XML file to add the authentication settings from the shared AT to OpsCenter AT

See About importing authentication settings during OpsCenter upgrade.

Post-upgrade tasks:

If the import is not successful, the default OpsCenter user needs to reset the passwords of OpsCenterUsers(vx) domain users that you have imported from the earlier OpsCenter version.

Trust between NBAC-enabled NetBackup / PureDisk servers and OpsCenter server need to be established again.

See Setting up trust between OpsCenter and NBAC-enabled NetBackup or PureDisk.

The installer installs OpsCenter AT on the OpsCenter server host

OpsCenter uses its own OpsCenter AT for user authentication

All credentials of PureDisk and NBAC-enabled NetBackup are imported from remote AT to OpsCenter AT

Only OpsCenterUsers(vx) domain users are imported to OpsCenter AT

All imported OpsCenterUsers(vx) users can logon to OpsCenter after the installation.

Upgrade to OpsCenter: Clustered setup and remote AT in previous OpsCenter version

Pre-upgrade tasks: Export the shared AT broker's data to an XML file using the atutil utility

See Exporting authentication settings.

Note:

While copying the exported xml file, the DOS to UNIX conversion may be improper that may result in garbage characters in the xml file. This may cause failure of import. To avoid this, copy the xml file through FTP and with binary format.

Upgrade tasks: During OpsCenter upgrade, when prompted, import this XML file to add the authentication settings from the shared AT to OpsCenter AT

See About importing authentication settings during OpsCenter upgrade.

Post-upgrade tasks:

If the import is not successful, the default OpsCenter user needs to reset the passwords of OpsCenterUsers(vx) domain users that you have imported from the earlier OpsCenter version.

Trust between NBAC-enabled NetBackup / PureDisk servers and OpsCenter server need to be established again.

See Setting up trust between OpsCenter and NBAC-enabled NetBackup or PureDisk.

The installer installs OpsCenter AT on the OpsCenter server host

OpsCenter uses its own OpsCenter AT for user authentication

All credentials of PureDisk and NBAC-enabled NetBackup are imported from remote AT to OpsCenter AT

Only OpsCenterUsers(vx) domain users are imported to OpsCenter AT

All imported OpsCenterUsers(vx) users can logon to OpsCenter after the installation.

Feedback

Was this page helpful?
Previous

About importing authentication settings during OpsCenter upgrade

Next

Exporting authentication settings

Feedback

Was this page helpful?