Sybase Database Backup Software
Sybase database backup helps organizations protect business-critical data stored in SAP Adaptive Server Enterprise (ASE), SQL Anywhere, and SAP IQ databases. These database systems continue to serve enterprise applications, transactional workloads, embedded software, and analytical environments where reliable backup is essential.
Handy Backup provides two practical approaches to Sybase backup: automated database data backup through ODBC and scheduled copying of backup files created by native SAP database utilities. These methods can be used separately or together, depending on the database engine and recovery requirements.
Download Trial
What Is Sybase Database Backup?
Sybase was historically associated with several database products that later became part of SAP's software portfolio. The best-known systems include SAP Adaptive Server Enterprise, SAP SQL Anywhere, and SAP IQ. Although they share historical roots, their architectures, backup commands, and recovery procedures differ.
SAP ASE Backup
SAP Adaptive Server Enterprise, formerly Sybase ASE, is a relational database management system used for transactional applications. Its native backup mechanisms include database dumps and transaction log dumps.
SQL Anywhere Backup
SAP SQL Anywhere, formerly Sybase SQL Anywhere, is used in embedded, departmental, and business applications. It provides database backup utilities and procedures for protecting DB files and transaction logs.
SAP IQ Backup
SAP IQ, formerly Sybase IQ, is a column-oriented analytical database. It has its own database backup and recovery mechanisms designed for its storage architecture and analytical workloads.
Administrators should choose between native database backup and logical data backup according to their recovery objectives. See Database Backup Strategies for guidance on backup planning, recovery frequency, and storage.
Sybase Database Backup Methods Compared
Not every Sybase backup method produces the same type of recoverable data. An ODBC connection provides logical access to database information, while native SAP utilities create backups according to the internal requirements of each database engine.
Handy Backup Professional can automate ODBC data backups and protect the files generated by native Sybase backup procedures.
| Backup Method | Data Protected | Typical Use |
|---|---|---|
| ODBC Database Backup | Database content accessible through the configured ODBC driver. | Automated logical data backup and selected database information. |
| SAP ASE DUMP DATABASE | Native database dump created by the SAP ASE Backup Server. | Database recovery using SAP ASE restoration procedures. |
| SQL Anywhere dbbackup | Database and transaction log files according to the selected backup options. | Native SQL Anywhere database recovery. |
| SAP IQ BACKUP DATABASE | Native SAP IQ backup archives containing database information required by the selected backup operation. | SAP IQ database recovery through native utilities. |
| Handy Backup File Backup | Files and directories containing previously generated database dumps and backup archives. | Scheduled copying, versioning, and additional storage of database backups. |
Important: ODBC backup is not equivalent to a complete native database dump. It should not be assumed to preserve transaction logs, database server configuration, users, or every database object. For full database recovery, use the appropriate native backup procedure and verify that all required components are available.
Sybase Backup Features in Handy Backup Professional
Handy Backup Professional includes the Database plug-in for working with ODBC data sources, along with tools for scheduled file backup, storage management, encryption, compression, and recovery.
ODBC Database Access
Connect to a configured Sybase data source and select available database content through the Database plug-in.
Automatic Scheduling
Run database and file backup tasks daily, weekly, monthly, or at custom intervals without repeatedly configuring each operation.
Flexible Storage
Store Sybase backup data on local disks, external drives, NAS storage, remote servers, or cloud destinations.
Encryption and Compression
Protect stored backup copies with AES encryption and use compression when appropriate for your storage policy.
Backup Versions
Maintain previous backup copies to provide recovery points before database changes, updates, or maintenance operations.
Logs and Notifications
Review backup task results, receive email notifications, and identify failed operations or storage problems.
Sybase Backup Through ODBC
Handy Backup Professional uses the Database plug-in to connect to ODBC-accessible Sybase data. This method is useful when administrators need to automate the extraction and backup of selected database content rather than create a complete native database archive.
A suitable Sybase ODBC driver must be installed and configured in Windows before creating the task. The connection requires appropriate access permissions, compatible driver architecture, and a working database server.
When ODBC Backup Is Useful
- Creating regular copies of selected database content.
- Automating logical database data backup.
- Protecting data from older Sybase applications with existing ODBC connections.
- Managing database data backups alongside other Windows backup tasks.
ODBC Backup Considerations
- Driver compatibility depends on the specific Sybase database and version.
- Access permissions determine which objects can be read.
- Logical data backup does not automatically include all server-level information.
- The resulting backup and restoration procedure must be tested.
For more details on database connections and logical backups, see Database Backup Over ODBC.
How to Back Up Sybase Data with Handy Backup
The following procedure demonstrates how to configure an ODBC-based Sybase backup task. The example uses a Sybase SQL Anywhere data source. For other Sybase database engines, connection details and available database objects may differ.
-
Install the ODBC driver. Obtain a driver appropriate for the Sybase database engine and Windows environment. Verify that the driver can connect to the database.
-
Configure the data source. Open Windows ODBC Data Source Administrator, select the correct 32-bit or 64-bit version, and configure the connection using the installed driver.
-
Create a backup task. Open Handy Backup Professional and start the New Task Wizard using the Create button or Ctrl+N. Select Backup and continue to the data selection step.
Before Starting the Backup
The ODBC driver installation and Windows data source configuration are performed outside Handy Backup.
Check the database connection before proceeding. The backup application must have access to the necessary data, and the configured driver must be compatible with the installed Windows environment.
Note: Successful ODBC connectivity does not by itself establish that every database object can be exported or restored. Verify the actual backup results for the required Sybase data.
-
Select the Database plug-in. On Step 2 of the wizard, expand the Database group and open the Database plug-in to access the configured ODBC data sources.
-
Select the Sybase data. Open the configured data source and select the database objects or content available for backup. Confirm the selection by clicking OK.
-
Choose backup storage. Select a local disk, network folder, NAS, remote server, or cloud destination where the backup data will be saved.
-
Configure and run the task. Set the required schedule and available backup options. Save the task, run the first backup, and review its results.
For additional instructions on configuring storage, scheduling, encryption, and recovery tasks, see the Handy Backup User Manual.
Recovery recommendation: Perform a test restore after configuring the ODBC task. Verify that the resulting backup contains the required information and that the chosen restoration procedure works with the target database environment.
Native Sybase Backup Methods: ASE, SQL Anywhere and IQ
Native database backup utilities are generally preferable when the recovery objective is to restore an entire database environment with its internal structures and transaction information. The commands and backup files differ between SAP ASE, SQL Anywhere, and SAP IQ.
SAP ASE Database Backup
SAP Adaptive Server Enterprise provides the DUMP DATABASE command for creating native database dumps and DUMP TRANSACTION for backing up transaction logs where applicable.
These operations use SAP ASE backup facilities rather than a generic ODBC export.
A simplified SAP ASE database dump command looks like this:
dump database mydatabase
to "/backup/mydatabase.dmp"
goThe actual command must use a valid backup destination accessible to the configured SAP ASE Backup Server. Database and transaction log dumps can form part of a recovery sequence.
Restoration uses LOAD DATABASE and, when applicable, LOAD TRANSACTION. Administrators should follow the SAP ASE backup documentation for their database version.
SAP SQL Anywhere Backup
SQL Anywhere includes its own database backup tools, including the dbbackup utility and the BACKUP DATABASE statement.
Depending on the selected options, these tools can preserve database files and transaction log information needed for recovery.
A typical SQL Anywhere backup process involves connecting to the database, selecting a destination, and running the appropriate native backup command or utility.
With dbbackup, administrators can create backup files in a designated directory. The exact command depends on the database connection and selected backup options.
Consult the SAP SQL Anywhere backup documentation when configuring backup and recovery procedures.
SAP IQ Database Backup
SAP IQ provides native BACKUP DATABASE and RESTORE DATABASE functionality designed for its column-oriented database architecture.
Backup planning should consider the database version, storage configuration, backup archive destinations, and requirements for recovering a complete IQ database.
SAP IQ backup procedures can use full or incremental backup approaches according to the database version and configuration. Native backup archives should be preserved together with the information required for restoration.
See the SAP IQ Backup, Restore, and Data Recovery documentation for details.
Automating Sybase Database Dump Storage
When SAP ASE, SQL Anywhere, or SAP IQ creates native database backup files, Handy Backup can automate copying these files to additional storage destinations. This separates the database backup procedure from the process of maintaining and protecting stored backup copies.
For example, an administrator can create a regular SAP ASE database dump and configure Handy Backup to copy the completed dump file to a NAS device or offsite storage.
1. Create a Native Database Backup
Use the database engine's own backup utility to create a consistent native backup. Configure the backup destination and ensure the operation completes successfully.
2. Create a File Backup Task
In Handy Backup, select the directory containing the completed database dump or backup archive files. Configure the required destination.
3. Configure Automatic Execution
Schedule the Handy Backup task after native backup creation, or coordinate execution using scripts and appropriate task settings. Avoid copying an archive while it is still being written.
4. Retain and Test Recovery Copies
Maintain the required versions and verify that archived backup files can be retrieved and used with the corresponding database recovery procedure.
Important: For databases using full backups and subsequent transaction log backups, preserve the files and sequence required by the recovery plan. Copying only the latest database dump may not provide the intended recovery point.
Managing Sybase Backup Archives and Recovery Chains
Storing a Sybase database dump is only one part of a recovery strategy. SAP ASE databases may require a full database dump followed by a sequence of transaction log dumps, while SQL Anywhere and SAP IQ have their own backup dependencies. Losing one required file can prevent recovery to the intended point in time.
Handy Backup helps administrators organize and retain these files after they have been created by native database utilities, reducing the need to transfer each backup archive manually.
Preserve Complete Backup Sets
Keep the database dumps, transaction logs, and incremental backup files required for each recovery sequence. For SAP ASE, this can include a full database dump and subsequent transaction log dumps. Avoid deleting earlier files until the dependent backups are no longer needed.
Coordinate Backup Completion
Configure Handy Backup to copy files only after the native Sybase backup operation has finished successfully. This prevents incomplete database dumps from being transferred to secondary storage and mistaken for valid recovery copies.
Maintain Separate Recovery Copies
Use Handy Backup to transfer completed backup sets from the database server to independent storage, such as a dedicated backup repository, NAS, or remote location. Separating these copies from the production server helps protect them against local hardware failures and accidental deletion.
Align Retention with Recovery Needs
Define how long full dumps, transaction log sequences, and previous backup generations must remain available. Retention settings should account for database recovery objectives and dependencies between files, rather than simply deleting the oldest archive.
Recovery planning: A collection of backup files is not necessarily a recoverable backup set. Periodically test the native Sybase restore procedure, verify that every required archive is available, and confirm that the database can be recovered to the intended point.
How to Restore a Sybase Database Backup
The restoration procedure depends on how the backup was created. An ODBC data backup, a native SAP ASE database dump, and a SQL Anywhere database backup require different recovery approaches.
Before restoring production data, identify the database engine and version, verify the available backup files, and determine which additional transaction logs or configuration information are needed.
Restore ODBC Backup Data
Use Handy Backup's restore functionality to access the existing backup and configure the required recovery operation. Verify the target connection and available data objects.
When necessary, restore data into a separate environment first to test the result without affecting the production database.
Restore Native Sybase Backups
For SAP ASE, use the appropriate LOAD DATABASE and LOAD TRANSACTION sequence. For SQL Anywhere, restore the necessary database and transaction log files according to its recovery procedures.
SAP IQ backups require the corresponding native RESTORE DATABASE procedure and any additional backup archives needed for the selected recovery point.
Verify Database Recovery
After restoration, check that the database starts correctly and that the application can access required tables, records, stored procedures, and other database objects. Review transaction consistency and perform representative application queries before returning the restored database to production use.
Recommended Solution
Lifetime license
Handy Backup Professional
Handy Backup provides Sybase database backup software with ODBC-based backup through the Database plug-in and automated file backup for native Sybase database dumps. It combines scheduling, configurable storage, encryption, versioning, and recovery tools in one Windows application. The software helps administrators create regular copies of selected Sybase data or automate the protection of native SAP ASE, SQL Anywhere, and SAP IQ backup files without manually transferring them after each operation.
FAQ About Sybase Database Backup
How do I back up a Sybase ASE database?
SAP ASE provides DUMP DATABASE for creating native database dumps and DUMP TRANSACTION for transaction log backups where applicable. These files can subsequently be copied to additional storage using Handy Backup. ODBC backup is another option for selected database data, but it does not replace the native dump procedure for complete database recovery.
What is the difference between Sybase ASE and SQL Anywhere backup?
SAP ASE uses native database and transaction log dump procedures, while SAP SQL Anywhere provides its own utilities, including dbbackup and BACKUP DATABASE. Both systems require recovery procedures appropriate to their architecture, backup files, and database version.
Can Handy Backup back up Sybase databases through ODBC?
Yes. Handy Backup Professional includes the Database plug-in for working with ODBC data sources. A compatible Sybase ODBC driver must be installed and configured, and the connection must provide access to the required database content. The exact objects and data available for backup depend on the driver and database environment.
How can I automate Sybase database dump backups?
Configure native database backup creation with the appropriate SAP utility, then create a scheduled Handy Backup file backup task for the directory containing completed database dumps or backup archives. Coordinate the schedule so that files are copied only after the native backup finishes successfully.
Can Sybase backup files be stored on NAS or cloud storage?
Yes. Handy Backup can copy completed Sybase backup files to local disks, external drives, network folders, NAS devices, remote servers, and cloud storage. The appropriate destination depends on the required recovery time, data volume, storage policy, and available infrastructure.
Does an ODBC backup include the complete Sybase database?
Not necessarily. ODBC provides logical access to database data, but it does not automatically include transaction logs, server settings, every database object, or all information needed for complete database recovery. Native Sybase backup utilities should be used when full database restoration is required.
How do I restore a Sybase database?
Recovery depends on the database engine and backup method. SAP ASE uses native LOAD DATABASE and LOAD TRANSACTION operations, SQL Anywhere restores database and transaction log files according to its recovery procedure, and SAP IQ provides RESTORE DATABASE. For ODBC-based data backups, use the applicable Handy Backup restoration procedure and verify the restored database content.