I have a customer where I discovered that the snapshots were not expiring and were filling up storage. I thought this was strange because I could swear I created the snapshots with an expiration time.
After some experimentation it seems like in SSMC 3.2 running against
3.3.1.215 (GA)+P01,P02,P04,P06,P13,P16 I was able to recreate a scenario where the snapshots don’t contain an expiration when scheduled.
Here is the snapshot schedule that actually gets created: Note that the scheduled command is actually missing the -exp flag which means it never expires. This ends up being a time bomb and fills up the storage.
A schedule I created manually through PuTTY is “createsv -exp 72h @vvname@@a@@b@@d@@k@@M@ set:R2CLUSTER-VVS”
| Attachments: |
|
File comment: Screenshot2 ssmc2.png [ 37.78 KiB | Viewed 7642 times ] |
|
File comment: Screenshot1 ssmc1.png [ 43.09 KiB | Viewed 7642 times ] |