VMware Cloud Community
vmproteau
Enthusiast
Enthusiast

Corporate Snapshot Policies

I've had to address this in every environment I have supported and it's always a mine field. As end users have learned about snapshots, they naturally want to use them as protections against changes to their production systems. The problem is that once you open this door and word spreads, you will get flooded with these requests. Eventually people are wanting them before every minior patch cycle. For larger environments, with thousands of VMs, this isn't suppotable. I've have implemented varying global policies and red tape to try to stem the tide but it is always difficult to defend against individually requests.

I'm curious how others have addressed this. Please share your snapahot policies and how you protect against this slippery slope.

0 Kudos
1 Reply
Gortee
Hot Shot
Hot Shot

I love this problem.  We put a time limit on all snapshots and implemented powershell to enforce it.  Simply put you have 48 hours to enjoy that snapshot then it's gone.  It has solved tons of snapshot related issues.  Most of my users think VMware forces it gone after 48 hours they don't know any better... problem solved.

Joseph Griffiths http://blog.jgriffiths.org @Gortees VCDX-DCV #143
0 Kudos