Ok everyone, Im gonna throw this one out there and see what everyone else does...
First, the requirements and settings...
The company Im working at is contractually obligated for the following:
- keep a backup of the systems for 45 days (ie, be able to restore a VM for up to 45 days from current day)
- as part of the backup/45 day restore combined with other business processes, do 1 full backup only, on every system 1 once per week
- Audit data (proof of backup, backup outcome, restore outcome, etc) must be available for any system (still running or deleted) for 1 year.
So, now my big question is, what/how should maintenance be carried out on the vRanger instances we have running?
Ideally, I would like the following:
- to keep the actual file contents of the repos as small as possible (deleting any old contents that doesn't fit into the above req's) as they are deduped/replicated via DataDomain to a DR site.
- to keep the vRanger DB as clean/small as possible
- to keep ALL report/job search data available for any system vRanger touched for up to 1 year from current day.
I'm seeing this as potentially a PoSH script to read vRanger job data, purge Repo data, purge savepoints, purge DB data (although Im not sure how these objects work in context of vranger, it would be great if someone could clarify the mechanism, or point me to the tech doc that does, thx)
Anyone done any housekeeping like this? I have a rather large environment (2700 vm's) and we are looking into the re-architecture of it for scalability and cleanliness over time.
Thanks!