Loading...
Loading...
A scheduled Backup Policy that used to run, no longer runs at the scheduled time.
This is caused by a backup group within the schedule no longer containing members. Follow the steps below to check if the scheduled Backup Policy is no longer running: Log in to the Avamar Utility Node as admin. Change to the Management Console Server log directory: cd /usr/local/avamar/var/mc/server_log/ Run the following command: for f in mcserver.log.*; do grep -H "schedName" $f && echo && echo "################################" && echo; done Example output: mcserver.log.11: <deleted non-essential info> SchedID=S1111111111111 schedName=BU_REP_STD11 version=null allowOvertime=true overtimeOption=NEXT_SUCCESS endTime=1665088200000 />################################ mcserver.log.12: <deleted non-essential info> SchedID=S2222222222222 schedName=BU_VM_CLIENTS_STD1_0100-1700_16HRS version=null allowOvertime=true overtimeOption=NEXT_SUCCESS endTime=1665100800000 />################################ In the example above, assume that the backup policy that is not running is called "3_pm". The command shows other scheduled Backup Policy names, but not the " schedName=3_pm " that is expected to be found. In this instance, the backup policy "3_pm" contained several Groups. One of these groups contains no members. This empty group used to contain multiple Virtual Machine clients. The customer had gradually retired and removed the clients from the vCenter, and the group became empty. Avamar does not flag if a group is empty, and the process to run the scheduled 3_pm Backup Policy prevented the schedule from running.
1. Identify which scheduled Backup Policy is no longer running. 2. Check if the backup policy contains multiple groups, and no Group is empty . If an empty Group is found, remove the empty Group from the Backup Policy. 3. Run a manual backup, or allow the backup policy to run as scheduled. 4. In the /usr/local/avamar/var/mc/server_log/ directory, run the following command, to search for the schedule name (schedName) in the mcserver.log.0 log file to see if the Backup Policy name is found. grep "schedName" mcserver.log.0 5. If the Backup Policy schedName is NOT found, contact Dell Support. Note: If the backup was run per schedule, additional logs may require searching: grep "schedName" mcserver.log.? grep "schedName" mcserver.log.*
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.