The Sybase iDataAgent provides an unique, simplified end-to-end backup and recovery solution for Sybase system and user databases in your enterprise. In addition to complete protection of the system databases which contain user database characteristics, file locations etc., it also provides more granular backup and recovery of your enterprise’s data, related administration files and transaction logs.
Full Range of Backup and Recovery Options
The Sybase iDataAgent provides the flexibility to backup the Sybase server which consists of system and user databases in different environments. This is very essential since the Sybase system and user databases are always subject to constant changes.
You can perform a full or transaction log backup of the entire Sybase Server at any point of time. The following section describes the backups that can be performed in different environments.
You can backup both the system and user-defined databases. You can comprehensively backup all the databases in an instance or schedule backups for the individual databases. You can also auto-discover new databases to comprehensively manage the backup of all databases in your environment.
Transaction Log Backups
You also have the facility to backup only the transaction logs when the database is online. These logs can be applied to an online backup and recover the database to the current point-in-time. A transaction log backup contains only the new changes since the full or another transaction log backup. Each time a transaction log is backed up it is truncated to the exact time of the backup. No checkpoint is issued at this time, therefore dirty pages are not written to disk before or after a transaction log backup. Any transactions that are not completed at the time a transaction log backup is performed are rolled back during a restore involving a transaction log backup.
Transaction Log Backup of a Damaged Database
If a database fails and any data is lost, you will want to restore it to the point of failure. Sybase iDataAgent allows you to capture all transaction log events that occurred after the last backup job was performed.
You can also protect the non-database files and profiles using the appropriate File System iDataAgent.
Backup and Recovery Failovers
In the event that a MediaAgent used for the backup or recovery operation fails, it is automatically resumed on alternate MediaAgents. In such cases, the backup or restore job will not restart from the beginning, but will resume from the point of failure. This is especially useful for backups and restores of large amount of data.
In the event, that a network goes down, the backup and recovery jobs are resumed on alternate data paths. Similarly, in the event of a device failure, the jobs are automatically switched to alternate disk and tape drives.
Efficient Job Management and Reporting
You can view and verify the status of backup and recovery operations from the Job Controller and the Event Viewer within the CommCell Console. You can also track the status of the jobs using Reports, which can be saved and distributed. Generate reports for different aspects of data management. Customize the reports to display only the required data and save them to a specific location in different formats. For example, you can create a backup job summary report to view the completed backup jobs.
You can schedule, generate and send the Reports via email without user intervention.
Deduplication provides a smarter way to store data by identifying and eliminating the duplicate items in a data protection operation.
Deduplication at the data block-level compares blocks of data against each other. If an object (such as, file, database) contains blocks of data that are identical to each other, then block-level deduplication does not store the redundant data, which reduces the size of the object in storage. This reduces the size of the backup data copies on both the disk and tapes.
The Sybase iDataAgent documentation uses the following terminology:
The computer in which the iDataAgent is installed and contains the data to be secured.
The Sybase Server to be used for the backup and restore operations.
The Sybase databases to be backed up.
A physical storage locations in a disk such as a partition that is dedicated to holding the Sybase database.
Last modified: 4/16/2019 6:55:56 PM