Consultor Eletrônico

VMS BACKUP method utilizing Shadow Sets

VMS Backup Method utilizing shadow sets

NOTE: The following is a customer implementation of how they chose
to back up their databases utilizing shadow sets. Progress Technical
Support is providing this as a guideline as an alternative to the
PROGRESS backup. This document may not be appropriate for all
situations. If there are questions regarding VMS BACKUP and its use
please contact your VMS system adminstrator, DCL dcoumentation or
Digital Equipment Corporation.

The following outline is a process one of our customers is
currently using as a backup procedure. Their database is
over 6.5G. In PHASE 1, the databases are down and back up
within 30 minutes. They found that PHASE 2 which backs up the
shadow set to disk takes about 2 hours. PHASE 4 which copies
the backup disk to tape takes about 3 hours.

They've broken down their backup procedure into 4 phases.
This procedure is called DB_BACKUP.

DB_BACKUP:
PHASE 1 - break up the production database shadow sets
PHASE 2 - backup the production databases (to backup disk)
PHASE 3 - backup non-production databases
PHASE 4 - copy files (from backup disk) to tape

Their chosen method of backup is VMS BACKUP.


PHASE 1 Break up the production database shadow sets
----------------------------------------------------

1. They first check the integrity of Shadow Sets containing
production data.

2. Send warning message out that backup process is starting

3. If PHASE 1, they check if there are any database files
that are open (there should not be any open database files)
Also logging system info: show active users, system processes,
device information, batch que information.

4. Submit procedure to remove users to start at a later time
for example, 10 minutes later, using the VMS command
SUBMIT/PARAM=("00:10:00")

5. Shutdown the databases (PROGRESS command)

6. Truncate bi (PROGRESS command)

7. Backup bi (VMS BACKUP)

8. Backup ai (VMS BACKUP)

9. Mark database as backed up (PROGRESS command)

10. Split shadow sets (VMS command)

11. Enable ai (PROGRESS command)

12. Startup databases (PROGRESS command)


PHASE 2 Backup the production databases (to backup disk)
--------------------------------------------------------

1. Set up private stripeset (VMS command)

2. Backup database (VMS BACKUP)

3. Backup lg file (VMS BACKUP)

4. Backup shm file (VMS BACKUP, this is not necessary,
backing this file up just save time when starting up
the database)

5. Backup st file (VMS BACKUP)

6. Relink shadow sets (VMS command)

PHASE 3 Backup non-production databases
---------------------------------------

1. (phase 1, step 4) logging system information (VMS command)

2. (phase 1, step 6) shutdown databases (PROGRESS command)

3. (phase 1, step 7) truncate bi (PROGRESS command)

4. (phase 1, step 8) backup bi (VMS command)

5. (phase 1, step 9) mark database backed up (PROGRESS command)

6. (phase 2, step 3) backup database (VMS BACKUP)

7. (phase 2, step 4) backup lg file (VMS BACKUP)

8. (phase 2, step 5) backup shm file (VMS BACKUP, this is not
necessary, backing this file up just saves time when starting
up the database)

9. (phase 1, step 13) startup databases (PROGRESS command)


PHASE 4 Copy files (from backup disk) to tape
---------------------------------------------

1. Execute VMS BACKUP command


Other kbases:
15986 Alternative method of backing up database - VMS

5-aug-96
jyt


Progress Software Technical Support Note # 15985