This post is more than 5 years old
2 Intern
•
309 Posts
0
1841
May 19th, 2015 09:00
Rolling snaps on VMAX20
Is there a slick way to maintain rolling VP snaps on a VMAX device without having to write a huge, complicated Solutions Enabler script. I'm reviewing the docs I found but don't see a simple way to do this. Even VNX snaps can at least auto-expire. Any ideas??
I'm running 5876.272.177
Thanks.
No Events found!
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
May 19th, 2015 10:00
upgrade to VMAX3
. I think i saw in one EMC World presentation a few weeks ago auto-expire snapshots (TTL, time to live parameter).
On your 20k you will need to script something, appsync if you got some $$$.
DanPJ
2 Intern
•
309 Posts
0
May 19th, 2015 11:00
One more thing. When working with VP Snaps, do the target and the source need to live in the same virtual pool? I would like bind the target TDEVs to a different pool where I have more room.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
May 19th, 2015 11:00
looks like it must be the same pool, take a look on page 8
https://www.emc.com/collateral/hardware/white-papers/h10498-timefinder-vp-snap-local-repl-wp.pdf
DanPJ
2 Intern
•
309 Posts
0
May 19th, 2015 11:00
No VMAX3, no Appsync. Guess I'm kicking it old school.
Thanks.
Daniel P. Jastredowski
Technology Support Services Infrastructure (Storage) Engineer
JONES DAY® - One Firm Worldwide℠
901 Lakeside Ave.
Cleveland, OH 44114
Office +1.216.586.1215
pete2c
1 Rookie
•
76 Posts
0
May 19th, 2015 11:00
The source and target do NOT need to be in the same pool. If there are multiple targets, however, all of the targets need to be in the same pool.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
May 19th, 2015 12:00
Thank you, that sentence in the middle of that document needs some work then.
pete2c
1 Rookie
•
76 Posts
1
May 19th, 2015 12:00
Your impression about VDEVs is correct, that's only for TF/Snaps. As far as I know they cannot be used for VP Snap.
Not sure if it helps or if you're already aware, but keep in mind you won't need a full copy for each snap in your target pool. You'll have one full copy of the source data plus any changes (for each target).
pete2c
1 Rookie
•
76 Posts
0
May 19th, 2015 12:00
I agree, I stumbled on that when I first read it too.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
May 19th, 2015 12:00
@pete2c corrected me, sounds like you can have your "protected" writes go to another pool.
DanPJ
2 Intern
•
309 Posts
0
May 19th, 2015 12:00
Yup. I'm aware. Thanks.
DanPJ
2 Intern
•
309 Posts
0
May 19th, 2015 12:00
Any chance on using VDEVs for the VP Snaps? I need to keep 35 days worth of a source but that will seriously over-subscribe by thin pool. I guessing VDEVs only apply to old school snaps, not the newer VP style.