Forum Discussion
44 Replies
- cmautnerPuritanI hate adding all the functions into code and bloating a script
- adam_sennottNovice IOk, good to know
- adam_sennottNovice II found Copy-PfaSnapshotToNewVvolVmdk in the library you linked. That is close, but doesn't address Protection groups snapshots which contain more than one volume; Im still trying to figure that part out.
- cmautnerPuritanYea codyhosterman has made my life easier with with those modules, I love that they are open source and I can kind of pick and choose what to use and change out
- adam_sennottNovice IYeah it really is. I can probably make a rough go of it with Copy-PfaSnapshotToNewVvolVmdk for now by getting the volume names from within the PG s and creating the target volumes one-by-one
- adam_sennottNovice Iand figure out how to make it more efficient later
- adam_sennottNovice II didnt realize the volume snapshot name wrt the use of PGs was just the pgsnapshotname.volumename
- cmautnerPuritanYup yup, and you can just query all of snaps for a given PG for a specified date and find one closest to a point in time in the past, that allows you to roll a given machine back to a point in time in the past
- cmautnerPuritanOr, with vvols, make a new machine, make disks of equivalent sizes and over write them. Then you can stand up a new VM that is a copy of one from a point in time in the past. For ransomware recovery that can be useful to spin up multiple copies from the past for forensics.
- adam_sennottNovice IKeeping some snapshots around for recovery sounds like a good use case.