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™ for Greenplum Administrator's Guide
  3. Troubleshooting NetBackup for Greenplum
  4. Troubleshooting of Greenplum backups that are canceled mid-backup
NetBackup™ for Greenplum Administrator's Guide

Troubleshooting of Greenplum backups that are canceled mid-backup

If Greenplum backups are canceled mid-backup, the backup processes are left hanging. If the main Greenplum gpbackup process is terminated in mid-backup, the cleanup_plugin_for_backup calls cannot be made to the plug-in to complete the normal completion and shutdown of the backup. In this case the setup_plugin_for_backup processes hang that remain running on the segment hosts. These processes eventually end due to the configurable error_shutdown_timer setting in the nbgpbackup_config.yaml file. The default is 10 hours.

Feedback

Was this page helpful?
Previous

Minimize time-out failures on large database restores

Next

Appendix A. Register authorized locations

Feedback

Was this page helpful?