Backing Up After Changing the Physical Schema

Enterprise Edition Home | Express Edition Home | Previous Page | Next Page The ontape Backup and Restore System (IDS) > Backing Up with ontape > Creating a Backup >

Backing Up After Changing the Physical Schema

You must perform a level-0 backup to ensure that you can restore the data after you make the following administrative changes. Consider waiting to make these changes until your next regularly scheduled level-0 backup.

Changing TAPEDEV or LTAPEDEV from /dev/null
Adding logging to a database
Adding a dbspace, blobspace, or sbspace before you can restore it with anything less than a full-system restore
Starting mirroring for a dbspace that contains logical-log files
Dropping a logical-log file
Moving one or more logical-log files
Changing the size or location of the physical log and after you reinitialize shared memory
Dropping a chunk before you can reuse the dbspace that contains that chunk
Renaming a chunk during a cold restore

Tip:

Although you no longer need to backup immediately after adding a logical-log file, your next backup should be level-0 because the data structures have changed.