Depending on your database backup schedule and needs, you might want to schedule AI file backups:
Each time you perform a database backup
Back up the AI files each time you back up the database. It should be a routine part of every backup. Also, back up the AI files on a backup media different from the database, log, and BI files. This technique provides a way to reconstruct the database by rolling forward the backup of the AI files against the previous backup of the database.
If you do choose to back up the AI files on the same media as the database, it is essential that you back up the AI files in a way that lets you restore them separately from the database, BI, and log files.
Note: If you back up the AI files when you perform a database backup, keep in mind that the AI files backed up are used with the previous database backup.
You can use the RFUTIL utility commands with online databases that have AI extents. You can perform online backups while after-imaging is enabled. The backup utility automatically marks the busy AI file as full and switches over to a new AI file.
On a daily basis
You should consider backing up the AI files on a daily basis if:
You are on a weekly full backup schedule and the AI files will grow very large during the week.
You want to perform daily backups of the AI files instead of performing incremental backups. However, it is quicker to restore your database from incremental backups than by rolling forward AI files.
If you are using a single AI file, it is important to back up the AI file before you fill the disk that contains it. If you do not back it up in time, the database engine shuts down the database. For a complete description of how to recover from a full AI disk, see Recoveringa Database. Also, if you are using a single AI file, you must shut down the database to switch to a new AI file.
If you are using multiple AI extents, you must back up the extents regularly to ensure that the system does not run out of AI space. Before deciding to back up the AI files every day, consider that recovering the database from small AI files is more intricate than recovering from a single, large AI file.
Each time you perform a database backup