I’m not sure what you mean
by duplication script. I’ve never duplicated a catalog backup or written
one to a DSSU.
Hot catalog backups must be written
to catalog backup volume pools, and other backup types cannot be written to
these pools. You can create multiple volume pools and mark them as catalog
backup pools.
-Jonathan
From: Jim Horalek
[mailto:jimh AT federaledge DOT com]
Sent: Friday, January 14, 2011 11:11 AM
To: Martin, Jonathan; 'VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU'
Subject: RE: [Veritas-bu] Diaster Recovery
Thanks j.onathan,
But should I have a separate
offsite_catalog pool? Or is it just more overhead and my dazed mind.
The duplication script only call
a single destination pool OFFSITE
From: Martin, Jonathan
[mailto:JMARTI05 AT intersil DOT com]
Sent: Friday, January 14, 2011 8:02 AM
To: Jim Horalek; VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Subject: RE: [Veritas-bu] Diaster Recovery
Hot catalog backups require
their own volume pool. The drfile is just what you suggested, the image /
pointer to the catalog backup.
-Jonathan
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Jim
Horalek
Sent: Friday, January 14, 2011 10:58 AM
To: 'VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU'
Subject: [Veritas-bu] Diaster Recovery
I’ve been using offline catalogs and have now switched
to online catalogs (6.5.4)
I’ve started duplicating the images using the
duplicate_images script in the goodies directory.
I’m not using any switches (except –dp and
–dstunit) so its duplicating everything (all clients, all policies
etc) to the offsite pool.
My question is the catalog. Should the catalog have its own
offsite pool?
How does the catalog know about the images the images that I
just created? Is the catalog the last image written?
I seems to me that there is a lingering catalog image (of
itself-duplication) that was never duped.
Or more likely I a bite dazed and it was duped and the
drfile fixes everthing.
Thanks
Jim