Unsolved
This post is more than 5 years old
2 Intern
•
132 Posts
0
1270
March 22nd, 2018 06:00
Sanity check - does Avamar "unilaterally" retire VM clients?
Looking for clarification on whether Avamar "unilaterally" retires VM clients.
Scenario - customer was backing up a VM using Avamar VM image backup, and had to restore it. Around the date of the restore, that older VM and its backups appear to have been retired, presumably because the new version of the VM was now the active one and the old one didn't exist in VMware anymore, so there wasn't much point in having it around and conflicting with another VM of the same name.
Fast forward one month, and the VM needs to be restored again - however, there is a degree of "disconnect" at the customer level and they can't figure out why they only have backups going back one month. I locate the older version of the VM under MC_RETIRED - except none of the customer contacts remembers actually having to retire the VM - so they are "assuming" that Avamar retired the VM on its own.
Avamar version is v7.5.0 - will be looking at documentation but wanted to ping here as well to see if anyone had any insight to share.
All comments/feedback appreciated - thanks.
connolly
2 Intern
•
132 Posts
0
March 22nd, 2018 06:00
I thought about that - but do the GUI logs go back one month? I thought they were like the Activity Monitor logs, in that they only went back a few days at most.
connolly
2 Intern
•
132 Posts
0
March 22nd, 2018 06:00
Well, I'll be damned - the audit logs are like a couple of other things in Avamar where the filtering is not immediately evident (it's located under the Actions menu as opposed to being a "button" in the window).
And, it lets you focus in on a domain, and filter out those copious login/logout messages.
I found an entry that indicates that the client was retired at the time that corresponds to what the retired client name was updated to - and it was retired by MCUser, which leads me to believe that someone logged in as that admin user retired it.
Of course, that is based on the theory that if Avamar was going to "automatically" retire it, it would do so as the "root" user, and that only folks logged in to the Admin GUI would be listed as "MCUser" (that is, that no internal Admin GUI process would also use MCUser for its credentials).
Cool.
ionthegeek
2 Intern
•
2K Posts
1
March 22nd, 2018 06:00
I'd recommend reviewing the audit logs in MC GUI.
ionthegeek
2 Intern
•
2K Posts
0
March 22nd, 2018 06:00
By default I believe they're pruned after 6 months but you can always extract the database flush from an older MCS backup and review its contents if you need to go back further than that.