About an alternate restore
An alternate restore lets you restore a DB2 database to a different client or to a different instance. You can also change the name of the database during the restore.
Alternate restores differ from regular restores as follows:
Use the regular restore procedures if you want to restore a database into the same instance on the same NetBackup client that hosted it previously. In this case, the database also retains its original name.
Use alternate restore procedures if you want to restore a database to a different instance or to a different client or if you must rename the database during the restore.
Databases within an instance must have unique names. If you restore a database into an instance that already has a database by that name, the alternate restore process overwrites the existing database.
Table: Types of restores permitted summarizes the types of restores you can perform and whether you need to use regular or alternate restore procedures.
Table: Types of restores permitted
Object | Regular restore | Alternate restore | Alternate restore | Alternate restore | Alternate restore | Alternate restore | Alternate restore | Alternate restore |
|---|---|---|---|---|---|---|---|---|
Database name | Same | Same | Same | Different | Same | Different | Different | Different |
Instance | Same | Same | Different | Same | Different | Different | Same | Different |
Client | Same | Different | Same | Same | Different | Same | Different | Different |
For example, assume that you have two NetBackup clients, grade7 and grade8. Instances class1 and class2 are on grade7. Instance class1 is on grade8.
Figure: Alternate restore example illustrates this example.
The following list shows some of the types of restores you can perform with alternate restore procedures:
You can restore database eng1 from instance class2 on client grade7 into instance class1 on client grade8. Database eng1 can retain its name because it is unique to instance class1.
You can restore database math1 from instance class1 on client grade7 into instance class1 on client grade8. During the restore, you need to rename math1 to math2 because class1 on grade8 already has a database named math1. Without renaming, the existing database math1 would be overwritten.
You can restore database art1 from instance class2 on client grade7 into instance class1 on client grade7. During the restore, you need to rename art1 to art2 because instance class1 already has a database named art1. Without renaming, the existing database art1 would be overwritten.