Avamar – expiring snapups

 

 

il_fullxfull.329221825

In a perfect world, you should never need this command. As my friend Ian Anderson wrote in a great Ask the experts session  where he spoke of achieving  “Avamar Zen”.

Avamar Zen is a state of harmony, where you have achieved a steady state of data ingestion vs data expiration. Where hopefully, you have more data expiring and being cleaned by the garbage collection than you have new data coming in.  However, zen can be hard to achieve. Avamar is an amazing product. If the SE’s have done their job and sized it properly, you should realize steady state. What does happen sometimes is, the client is so impressed they begin adding more systems and workloads that were outside of the initial sizing scope.

Years ago, when I was embedded onsite we ran into such an issue. It wasn’t so much about adding to many systems, but one in particular.  We had some groups, one configured to cross mount points and another to only protect local data. A co-worker spun up a new system and instead of checking with me, added the system himself to Avamar, and the wrong group.

The next day I arrive and find my Avamar grid is filled, also this was replicated over to the secondary. Quite the mess. So just roll the system back to a previous checkpoint? You may think, unfortunately when an Avamar system has reached capacity there is not enough space for the required overhead to engage the checkpoint roll-back. Now, lets meet our friend expire-snapshots.

What does it do? What do you think it does? It expires snaps! Awesome, right? What is really cool is how it does this. The command runs with switches where you can granulary target specific data to remove. For example, if you wanted to remove all data from Nov 30, 2015 and the previous 25 days, you would run the following

expire-snapups –before=’2015-11-30′ –days=25 –domain=/ > do-expire.sh

This will create a script in tmp you can then run and wipe out the offending data.

There are other switches available to target specific data and clients. When complete, settle in for a long garbage collect to run and turf the offending client.

When complete, I hope you can achieve “Avamar Zen” as I did. I also changed the admin password, so my helpful co-worker could not again repeat the same mistake.

 

Category: avamar, backup recovery |

no comments

Comments are closed.