I don't believe that I should be a recipient of these emails.
Craig Temby
Keane, Inc.
Howell, MI
517-540-4141
**************************************************************************************************************************
This e-mail, including attachments, is intended for the exclusive use
of the addressee and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, any dissemination,
use, distribution or copying is strictly prohibited. If you have
received this e-mail in error, please notify me via return e-mail and
permanently delete the original and destroy all copies.
**************************************************************************************************************************
>>> Richard.Mochnaczewski AT STANDARDLIFE DOT CA 03/15/07 11:20 AM >>>
Let's say that we have a disk storage pool called PRD_DISK. Every night
backups run and we run a backup stgpool command for our offsite copies
to a tapepool called PRD_DR and then we initiate a migration of data
from PRD_DISK to onsite tapepool called PRD_TAPE.
When you run a backup stgpool of PRD_DISK to PRD_DR you are only
backing up the incremental and not the whole storage pool ( by whole ,
the equivalent data of what is being cached ). If , for instance, we are
running Oracle incremental backups of a database where we run a full
cold backup which is 420 Gb to the storage pool PRD_DISK on a Friday
and then the next few days I run an incremental, come Wednesday, if I
run a backup stgpool again I will only get the latest incremental data
restored when I do a restore stgpool. What it comes time to restore such
a database, in the past becasue we were running daily hot backups of the
database. At a DR test we would be give the DR test date and do a
restore stgpool of PRD_DISK which would contain the complete database on
disk. Then, the DBA could launch as many threads as they need to restore
the database quickly rather than having to go to tape and hogging
several tape drives to get the databse restored when we go the
incremental route.
Rich
----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf
Of
Mark Stapleton
Sent: Thursday, March 15, 2007 11:04 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Backing up full primary stgpool
From: ADSM: Dist Stor Manager on behalf of Richard Mochnaczewski
During DR, we would like to restore one of our primary storage pool
but not just the incremental of the last night's backup but as it looks
with all its cached data. Aside from not running a migration to tape
which puts us at risk of losing data that hasn't been backed up to tape,
is there a way of achieving this using native TSM commands ?
This question doesn't make much sense to me. Are you talking about
recreating your primary disk storage pool? There's no need for that
during a DR exercise.
Are you talking about restoring your primary tape storage pool? There's
no need for that either. Your copy storage pool (the volumes of which
should all be at your DR site), can be used to rebuild lost servers,
provided that the primary tape storage pool is marked as DESTROYED once
your TSM database is restored and the TSM server is running.
--
Mark Stapleton (mark.s AT evolvingsol DOT com)
Senior consultant
|
