Can anyone assist with this situation ?

I have a requirement to keep DB2 daily backups for 30 days, month end for 14
months and year end for 7 years on an S70 running AIX 4.3.1, ADSM server
3.1.2.0, client 3.1.0.3 and DB2/UDB 5.2.

Daily backups are being done using the following command "db2 backup db <DB
NAME> use adsm", these are then kept for 30 days. In order to deletes backup
images older than 30 days the following command is used "db2adutl delete full
taken at <TIME STAMP> db <DB NAME> without prompting". That is OK for daily
backups.

Month end and year end backups are treated differently, first a daily backup is
taken then another backup to disk. The disk image is then archived to ADSM using
a management class that will keep the image for the correct number of days.

This was OK wile backing up a 4GB database, but a 40GB database is about to be
added onto this system and there is not enough disk space to do a DB2 to disk
backup then archive.

If anyone has come across this situation, how did you create and manage month
end and year end archives?

Andrew Miller

The S70 had a 3570-B12 and I have just added a additional 3575-L12 onto this
system, licensed ADSM for Advanced Device support.

It has now been noticed that if a migration or reclamation is running and a DB2
backup or restore is started, the migration/reclamation is cancelled, also if a
DB2 backup is in progress and a DB2 restore is started the backup is cancelled.
This was not happening when just the 3570 was in use.

Any thoughts ?

Andrew Miller