It is recommended that you develop and implement a backup schedule to protect your data. You should also ensure that you have created and tested your backup and recovery commands as part of your backup and recovery plan.
Some of the factors that you need to consider when developing your backup and recovery plan include:
where are the database files located?
what files need to be backed up?
where are the backup files stored?
how does the backup affect performance of your database or application?
will the database server be running while you run the backup?
Some of the most common situations where you require a backup include:
Typically, a backup uses a combination of full and incremental backups. The frequency of each backup type depends on the type of data that you are protecting. You should also validate your backups to ensure that they can be used for recovery. See Backup validation.
You can use the scheduling features in SQL Anywhere to automate the task of backing up your database. Once you specify a schedule, the backups are performed automatically by the database server. See Task automation using schedules and events and Maintenance plan creation.
The length of time your organization can function without access to the data in your database determines the maximum recovery time.
You should verify that you have the protection you need against media failure on the database file and on the transaction log file. If you are running in a replication environment, you should consider using a transaction log mirror. See Media failure.
External factors such as available hardware, the size of database files, recovery medium, disk space, and unexpected errors can affect your recovery time. When planning a backup strategy, you should allow additional recovery time for tasks such as entering recovery commands or retrieving and loading tapes.
Discuss this page in DocCommentXchange.
|Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1|