Hi All,
I have a doubt to clarify.
I have 45 volumes to which I have to resync the Physical copy daily at around mid night.
So I decide to write a command and schedule that task.
My concerns are
1. 45 volumes if I take individually then 45 tasks which I dont want to do.
2. Can I move all these 45 Physical copy VVs to one volume set and schedule one task.
I have prepared one command, please check if it is right.
createsched "createvvcopy -s -r set:Physical_copy" "0 0 * * *" physical_copy_resync
Thanks in advance.
Regards,
KK
Scheduling the Physical copy
- Richard Siemers
- Site Admin
- Posts: 1333
- Joined: Tue Aug 18, 2009 10:35 pm
- Location: Dallas, Texas
Re: Scheduling the Physical copy
I don't have the ability to test the command, but it looks legit from the admin guide.
Are you getting an error?
Are you getting an error?
Richard Siemers
The views and opinions expressed are my own and do not necessarily reflect those of my employer.
The views and opinions expressed are my own and do not necessarily reflect those of my employer.
Re: Scheduling the Physical copy
Hi Sir,
I have not tried the code yet.
Once you confirm the code I can test.
Because I'm quite afraid to test directly on the production.
Regards,
KK
I have not tried the code yet.
Once you confirm the code I can test.
Because I'm quite afraid to test directly on the production.
Regards,
KK
Re: Scheduling the Physical copy
I'd avoid using a physical copy if at all possible.
Use a snapshot, it takes a couple of seconds max per VV and you're sharing the same wide striped disks anyway whether using a snap or physical copy so there's no performance advantage to a physical copy, with snaps you also gain huge space savings and lower array overheads.
There are a couple of advantages of a physical copy over a snap in a legacy array in that each PC is independent of the source volume. But in a 3PAR world they're probably sitting on the same physical disks (unless you've purposely circumvented the wide striping) so what does that actually buy you ? and if you need to guarantee performance on the source VV you can use Priority Optimization.
If you need the same disk ID etc to simplify mounting then you can create the snaps upfront for each VV and then just issue an updatevv periodically to refresh the data which is a much simpler and cleaner process.
Use a snapshot, it takes a couple of seconds max per VV and you're sharing the same wide striped disks anyway whether using a snap or physical copy so there's no performance advantage to a physical copy, with snaps you also gain huge space savings and lower array overheads.
There are a couple of advantages of a physical copy over a snap in a legacy array in that each PC is independent of the source volume. But in a 3PAR world they're probably sitting on the same physical disks (unless you've purposely circumvented the wide striping) so what does that actually buy you ? and if you need to guarantee performance on the source VV you can use Priority Optimization.
If you need the same disk ID etc to simplify mounting then you can create the snaps upfront for each VV and then just issue an updatevv periodically to refresh the data which is a much simpler and cleaner process.
Re: Scheduling the Physical copy
Hi Richard Siemers Sir,
I have not tested the code yet. I dont have a test environment to test with
I will test once I get the confirmation.
Regards,
KK
I have not tested the code yet. I dont have a test environment to test with
I will test once I get the confirmation.
Regards,
KK
Re: Scheduling the Physical copy
Hi John MH Sir,
For those VVs I'm taking PC dont have any backup solutions.
So we are taking the physical copies and resynching everyday.
If we take the Virtual copy in case if the disk got corrupted wont it affect the LUN?
Regards,
KK
For those VVs I'm taking PC dont have any backup solutions.
So we are taking the physical copies and resynching everyday.
If we take the Virtual copy in case if the disk got corrupted wont it affect the LUN?
Regards,
KK