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