|Oracle Disaster Recovery - veritas volume replicator/flashsnap [message #231158]
||Sun, 15 April 2007 04:13
Registered: December 2006
Hi all, |
We are running Oracle 18.104.22.168 on
Solaris and the company is going
with the Veritas Volume replicator and
flashsnap to make a DR solution and also
a means to copy Production data to a Test system.
System people have installed VVR (Veritas
volume replicator) and the changes are going
to a staging system/volume group and from there
using flashsnap a Test envrionment is being
Our involvement comes in terms of DBA
actions on the database.
a)What do I have to do in terms of
bringing up oracle at the Test envrionment for
DR situation? In this case the oracle SID
will be maintained as the same as Production one.
b)Once the flashsnap synchronises all the
data files, can I login to sqlplus and
and bringup the database without any
recovery commands? Since this is DR
situation, I am assuming I do not have
to recreate the control etc? Is that correct?
c)If I have to bring the up the database
for making a copy of Production database
and need to rename the SID. What actions
should I take in terms of bringing up
I was told by the system team that
when VVR or flashsnap is executed
there is no "Alter tablespace Begin backup"
or "end backup" executed at all.
My doubt is:
How do I bring up the database consistently
if there is no "begin / end " backups issued?
Does this mean the way VVR/flashsnap works
automatically takes care of the Begin/End backups
and the datafiles are consistent and database
can be opened without any issues?
Please forgive my terminology on VVR / flashsnap,
I do not have any experience or exposure to them.
The system people have installed
and we are the end where we are looking after
the oracle from DBA point of view.
I would appreciate if any of you could shed some
light on the subject or point me in the correct direction.