Video Screencast Help

Veritas VVR as DR solution

Created: 22 Jun 2011 | 7 comments
Sa1's picture

I am having solaris servers configured in solaris cluster at production site running Oracle based application at Production setup. Want to check how VVR can help me establishing DR.

How easy or difficult this task would be and what are the points I need to consider ?.....

Need the inputs.....

Thanks...

Comments 7 CommentsJump to latest comment

Gaurav Sangamnerkar's picture

Hello,

very first thing you would need is Veritas Volume Manager ... are you using it ?  VVR code is inbuilt in veritas volume manager only ...  so u need to pass the entire disk control to veritas volume manager .... All VVR objects are controlled by volume manager..

secondly , are u planning to use GCO or just VVR ?

I think u can read VVR guides to understand better..

https://sort.symantec.com/documents  (select solaris OS & product guides)... you will find all VVR guides there.... have a run through.. m sure that will clear ur doubts..

 

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

mikebounds's picture

For VCS you need to consider if you want to use GCO, RDC or neither - see posts:

 

https://www-secure.symantec.com/connect/forums/global-cluster-option-two-single-node-cluster

 

https://www-secure.symantec.com/connect/forums/cluster-configuration-rdc-or-gco

 

https://www-secure.symantec.com/connect/forums/sf-cfs-rac-without-gco-option

 

For VVR you need to consider:

  1. Replication Mode: Sync, soft sync (Sync override) or asyn, or use bunker - see post from above https://www-secure.symantec.com/connect/forums/global-cluster-option-two-single-node-cluster
  2. Bandwidth you require (use vradvisor - https://sort.symantec.com/public/documents/sfha/5.1sp1/solaris/productguides/pdf/vvr_advisor_users_51sp1_sol.pdf)
  3. SRL size ( use vradvisor)
  4. How you are going to do initial sync - network, tape or flashsnap copy (see https://sort.symantec.com/public/documents/sfha/5.1sp1/solaris/productguides/pdf/vvr_admin_51sp1_sol.pdf)

You should also look at https://sort.symantec.com/public/documents/sfha/5.1sp1/solaris/productguides/pdf/vvr_planning_51sp1_sol.pdf and https://sort.symantec.com/public/documents/sfha/5.1sp1/solaris/productguides/pdf/vcs_vvr_agent_51sp1_sol.pdf

Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below

Sa1's picture

Thanks for inputs.

I am not using Veritas Volume Manager. My Solaris is having UFS file system and two node cluster is built on it. What are the challanges to install Volume Manager or Storage foundation on Production Solaris servers running with UFS file system. Does it requires downtime?

VVR will enable me to replicate data only....and I need to start services manually on DR servers. This is considering I have Solaris cluster at production site.

Regarding Global Cluster.... Yes I may consider that option so as to have better failover of services to DR servers. Do I need to break solaris cluster and configure veritas cluster at production site?

Gaurav Sangamnerkar's picture

Hello,

well there would be couple of stuff which you would need to take care of ..

1. If  u want to use GCO, then yes, you would need to take everything out of Sun cluster control so that you can install veritas cluster & configure resources in it. Later you can configure it for DR (when you have vxvm installed)

2. Now for installing veritas volume manager, you need to take out all your solaris filesystems out of sun cluster control .. question here is, how are you using your filesystems here, are they purely on slices or on solaris metadevices ?  In any of the case, if you want to take full use of veritas volumes under VVR, I would assume you need to migrate your data from solaris slices/metadevices to veritas volumes.  Filesystem is not a question here whether u use vxfs/ufs, that should not be a problem as VVR replicates data block by block regardless of filesystem type.. but you need to have veritas volumes in a diskgroup....  roughly I can suggest you following steps:

-- Take a full system backup of all filesystems & configurations

-- Break the root mirror & keep one mirror aside to keep a safe rolback option.

-- Get some extra storage luns allocated, would help in easy migration.

-- On one of mirror now, take all resources out of sun cluster & uninstall Sun cluster software...

-- Install veritas storage foundation, be ready with vxvm/vcs & vvr license with GCO.

-- Now add the newly added storage luns to veritas control

-- create volumes of similar size on these new disks from veritas, you can install ufs on veritas volumes.

-- migrate your data from old solaris volumes/slices to veritas volumes

-- Once you have all ready with volumes, configure cluster services

-- configure vvr

-- configure GCO...

 

hope this helps

 

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

mikebounds's picture

You cannot convert Solaris slices or SVM to VxVM online, but you can convert offline which is fairly quick and does not depend on the size of you volumes as it just creates the private region (header on disk) so how long it takes depends on the number of volumes, although I THINK you have to convert the boot volumes which would require a reboot - see "Migrating from Solaris Volume Manager to VxVM" section in https://sort.symantec.com/public/documents/sfha/5.1sp1/solaris/productguides/pdf/sf_adv_admin_51sp1_sol.pdf for more information.  You do not need to convert UFS to VxFS in order to use VVR, but this will give you significant benefits as you are using Oracle - see https://sort.symantec.com/public/documents/sfha/5.1sp1/solaris/productguides/pdf/sf_adv_ora_51sp1_sol.pdf.  Again you must convert filesystems offline and the time taken depends on the number of files (not size of files)

If you have a Solaris cluster at production site and no cluster at DR site, then you do not need to migrate to VCS - Solaris cluster at production site only needs to be changed to used VxVM diskgroups - it does not need to know about VVR.  To failover to DR would require one VVR command, either:
vradmin migrate , if Production site was still running

vradmin takeover, if Produciton site is down.

VVR will not effect your ability to failover locally at the production site using shared disks.

If you want a cluster at the DR site and VVR commands to be run by the cluster (this can be manually initiated), then you can use VCS at both sites with GCO option.

Why do you want to use VVR, can you not use replication provided by the Array?

Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below

Sa1's picture

Hi...

Thanks for inputs...

One more input...It is Solaris LDOM environment.

Also I read somewhere that no need to change the UFS file system. However UFS volumes needs to be encapsulated inside VxVM

Also as suggested by Mike, no need to break Solaris Cluster at Production site....(as we may not use VCS).

I am looking for implementation of DR solution without much downtime..... (Production downtime is my concern.....)

Need your comments on encapsulation part.....

mikebounds's picture

If you use array replication, then I don't think you would need any downtime.

To use VVR, you must encapulate volumes, this changes Solaris slices to VxVM (or if you have SVM, then these can be converted to VxVM).  This requires downtime - conversion is very quick, but I think you have to reboot, although I never understood why if you were not encapsulating boot volumes (perhaps someone else can comment on this).  So supposing you are using Solaris slices - this would change your block device from /dev/dsk/c1t1d5s1 too /dev/vx/dsk/diskgroup/vol1.  This has no affect on the filesystem, which would remain UFS - this would be a separate step to convert to vxfs, but this is NOT required for VVR (but is beneficial for Oracle, but you can do this later if you want).

Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below