Laurence Beard writes:
> I have written unix scripts to backup an ORACLE database via 6 GByte
> storage pools -> 2 x 8mmtape(5Gbytes). At the end of the backup I do a
> "update stg backuppool hi=0"
> This causes the data in the storage pool backuppool to be moved from
> disk(storagepool) -> 8mmtapes. This means everything is on tape, such
> that, migration = 0%, and utilization can be > 0%.
> If I were to do the following
> 1."backup db type=full..."
> 2. Delete everything in that database i.e. delete volumes and "delete
> filespace <CLIENT> *" etc.
> 3. Shut down server ,and "dsmserv restore db".
> Could I expect the ADSTAR database to look exactly the same at the
> time of the "backup db type=full..", complete with all volumes and
> storage pools. I am not concerned about the any data in the storage
> pools as I have migrated it out to tape.
I'm not sure if what you wrote is really what you mean, as it sounds
like you think that the data no longer exists in a storage pool when it
is migrated to tape. It is important to note that the data still exists
in a storage pool, only it consists of tape rather than disk.
> This is how I am trying to implement my Disaster-Recovery, rather than
> creating a disaster-recovery stgpool as in Chapter 14 of
> Administrator's Guide for ADSTAR and backing up from
> backuppool->disaster-recovery any unmigrated files.
In answer to your question, yes, the ADSM database will look just like it did
at the time you did the
BACKUP DB. However, your storage pools (even the tape pools) might not look
quite the same.
Backing up the database is only a part (although a very important part!) of
implementing a disaster
recovery backup scheme for ADSM. The other major piece of this scheme should
include protecting
your ADSM storage pools. Otherwise, if a disaster wipes out your ADSM database
and storage pools,
you'll be able to restore the database, but you won't have any client data.
This would render your
ADSM server useless.
Deleted stuff...
Newly created copy storage pool volumes
ADSM database backup media
External backup copies of volume history and device configuration files
Output from the above QUERY commands
ADSM server options file
There may be other variations on this that other folks might suggest, but I
think I've got the highlights.
Hope this helps. Good luck!
Andy Raibeck
ADSM Level 2 Support
***************************************************************
Hi Andy and all others..
I am getting closer to nutting out DR for ADSTAR, and must say it is a
bit more complex than I thought. Support for ADSTAR is non-exsistent
in this part of the world so need some more advice.
1. In your comment: " It is important to note that the data still
exists in a storage pool, only it consists of tape rather than disk"
I was wondering, at the end of every backup from UNIX to ADSTAR, I am
moving all from BACKUPPOOL -> TAPEPOOL, by setting "update stgpool
packuppool hi=0", at this
point the stgpool of concern is TAPEPOOL that I should look at
recoverying for DR, or still the BACKUPPOOL as well ?
2. (***CONFUSED***) From the ADSTAR Administrator's Guide, you create
a DR stgpool and use "backup stgpool backup..." for primary stgpools.
Currently, I have 6GByte (raw) for BACKUPPOOL (everything is a FULL
cold backup of ORACLE database about 15 GBytes/day for 5 days), this
is the only stgpool I am using, with migration to TAPEPOOL.
Does the DR stgpool require extra disk space above the 6 GByte for
BACKUPPOOL ?
Is the DR stgpool called a "copy storage pool" ?
From the above figures, how much data will I have to backup from the
DR stgpool to tape (scratch vols) ?
I am of the impression that I need to backup the data twice, once in
the primary stgpool and also in the DR stgpool ??
The logmode is rollforward, does "dsmserv restore db" backup anything
of the logs, or does this all ready have to be intact on the system?
If so, then how does the database recover to the time of total
failure, when the system has to be completely rebuild ? Should the log
be backed up also?
I hope someone can clear up my confusion ??
Regards
Laurence Beard
lbeard AT cscnz.co DOT nz
Auckland, New Zealand.
|