This post is more than 5 years old
12 Posts
0
2825
May 14th, 2013 08:00
Client On-Demand Backup Group
Hello,
I'm have two Avamar grids (6.0 and 6.1). On each of these grids, there are some clients who backup using their normal groups (such as Exchange 2010 Database or Win 2003 File Systems), but then they kick off a second backup using the group "Client On-Demand Group". This group is not listed anywhere in the "groups" list in the interface. By the name, I can only assume that this is a backup that's kicked off on the client end, but I checked the clients and they don't have anything in the scripts folder that would kick off this backup. How and where is this backup being initiated?
Thanks for your help!
Josiah
fdxpilot
2 Intern
•
143 Posts
0
May 14th, 2013 12:00
Is it possible that anyone is running manual backups from the client via the Avamar client interface? If you right-click on the Avamar icon in the taskbar notification area, you can choose "Back Up Now" which will generate a "Client On-Demand Group" backup work order when viewed from the Avamar GUI.
If you look at the avagent.log file in the avs var folder on the client and search for "user=", you should see the user name that is triggering these jobs if this is how they are being initiated.
fdxpilot
2 Intern
•
143 Posts
0
May 14th, 2013 13:00
That is funny! The replication script on the source utility node essentially initiates an ad hoc backup from the source grid to the destination grid so that is why replication jobs show up as the "Client On-Demand Group" in the GUI. I certainly agree it is a bit confusing. The new Backup & Recovery Manager tool does a better job logically grouping replication jobs than the Avamar GUI currently does.
JosiahE
12 Posts
0
May 14th, 2013 13:00
Hello and thanks for the reply!
We confirmed that no-one is actually kicking off any jobs manually from the client. The jobs are starting a little after 10AM, and there is not an entry in avagent.log advising of a backup initiated at this time. There is also no "user=" entry in the log (I checked 3 different clients that are having this issue).
Looking at the Activity screen, I was able to see the Client On-Demand Groups there and it looks like this is related to replication of those grids back to our main grid. I was looking at the groups under Policy and didn't think to browse the Activity Monitor.
I'm not sure why this would have been named "Client On-Demand", but I think it's safe to say that we know what this is now
Thanks again!
Josiah