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™ Clustered Master Server Administrator's Guide
  3. Operational notes
  4. General notes on clustered master server administration
Veritas NetBackup™ Clustered Master Server Administrator's Guide

General notes on clustered master server administration

Consider the following operational issues to consider when you use NetBackup as a failover server:

  • If a NetBackup server fails over and backup jobs are running, one of the following things happen:

    • If checkpoint restart is enabled for backup jobs for the policy, any backups that were running are resumed at the last checkpoint. Note that the schedule window must permit the job to be resumed.

    • If checkpoint restart is not enabled for backup jobs, any backup jobs that were running fail. These jobs show up as failed jobs in the Activity Monitor or NetBackup reports. Scheduled backup jobs are retried according to the normal retry logic. (See the Job retry delay and the Schedule backup attempts attributes). The schedule window and so on must permit the retry of the job. After a failover occurs, the user must restart user-directed backups and manual backups.

    Refer to the NetBackup Administrator's Guide, Volume I, for more information on checkpoint restart , Job retry delay, and Scheduled backup attempts.

    https://www.veritas.com/support/en_US/article.DOC5332

  • After a failover occurs on a NetBackup failover server, it takes time for the tape devices and media servers to be reset. For example, a tape may have to be rewound before it is made available. Until the device is again ready for use, you may see errors. For example, you may see error 213 (no storage units available for use) or error 219 (the required storage unit is unavailable).

  • After a failover, NetBackup may change the status of a drive that is required for a backup or restore to PEND. More information is available about how to use the NetBackup Administration Console Device Monitor to resolve a pending request or action.

    See the NetBackup Administrator's Guide, Volume I.

    https://www.veritas.com/support/en_US/article.DOC5332

  • If you have the NetBackup Administration Console open when a failover occurs, you need to refresh the display. This refresh ensures that the services on the active node are displayed correctly. In the NetBackup Administration Console (from the View menu) click Refresh All.

  • The backup and restore process is the same whether you are in a cluster or a non-cluster environment. See the NetBackup Troubleshooting Guide, for further information on backup and archive processes and on restore processes.

    https://www.veritas.com/support/en_US/article.DOC5332

  • TIR is not supported for clustered shared drives.

Feedback

Was this page helpful?
Previous

Operational notes

Next

About delay in detecting of loss of connection (WSFC and VCS on Windows)

Feedback

Was this page helpful?