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™ for Sybase Administrator's Guide
  3. Introduction to NetBackup for Sybase
  4. NetBackup for Sybase overview
  5. NetBackup for Sybase technical overview
Veritas NetBackup™ for Sybase Administrator's Guide

NetBackup for Sybase technical overview

NetBackup for Sybase has a dynamically loadable library that provides the functions necessary for Sybase backup server to use NetBackup. This library is installed when NetBackup for Sybase is installed.

NetBackup for Sybase is integrated with Sybase backup server through the Sybase backup server archive API. Sybase backup server uses the archive API routines to issue I/O requests to an archive-byte stream. At run time, Sybase backup server loads the NetBackup for Sybase library and makes calls to the API routines to open, close, read, and write to the byte stream through this API interface.

The dump-device string of the Sybase DUMP and LOAD commands is extended to support the archive API. The following syntax instructs Sybase backup server to use the NetBackup archive device to transfer data to and from NetBackup:

"sybackup::"

The Sybase DUMP command is as follows:

dump database model to "sybackup::"

SQL Server and Sybase backup server do not have a backup-catalog feature. However, when you perform a database or transaction dump, NetBackup for Sybase automatically creates a file name for the dump image. You must then specify this file name during a subsequent load operation.

The file naming convention for the database and transaction dumps is the following:

sql_server_name.database_name.backup_type.stripe_number.pid.dd-mm-yyyy.hh:mm:ss

The backup_type is either D for database or T for transaction.

For example:

SYBASE11.mydb.D.0.24312.17-12-2003.14:05:25

More Information

NetBackup for Sybase overview

Sequence of operation for NetBackup for Sybase backups

Feedback

Was this page helpful?
Previous

SQL server and Sybase backup server

Next

Sequence of operation for NetBackup for Sybase backups

Feedback

Was this page helpful?