Symptoms

This health-check reviews automatic backup job configuration and identifies if any are found.Examples of responses for this health-check: Test ResultResult codeResult InterpretationPass0No automatic backup job configurations were found.Warning1Automatic backup job configuration found.Failure2This test has no failure result.Critical3This test has no critical result. Each test that passes is not listed in the summary report, for ease of reading.An example of the VxVerify health-check output is shown below: #========================#======#=========#====================================================================#==============# | Hostname / Category |Status Dell_KB | Warnings or Failures, unless tests Passed ; Product S.N. | #========================#======#=========#====================================================================#==============# | VxRM | Warning 340763| bkp_sched: Backup schedule job found. |

Cause

Update failed during the VxRail Manager postupdate stage. After VxRail Manager reboots, the backup reconfiguration task fails because the backup scheduling service has a running PID. vxr-manager:/mystic/vxm_backup_restore # mcp_python vxm_backup_restore.py -l Current user is root. We can do current job. /tmp/vxm_backup_restore.pid already exists, exiting wait 30 seconds retry[1/10]

Resolution

To avoid issue during an upgrade, follow the steps below: Change the backup setting to manual After completing the update from VxRail Manager, change back the backup configurations as the previous set. To set or change the backup policy using the wizard, enter:cd /mystic/vxm_backup_restore/For VxRail 8.0.240, enter: python vxm_backup_restore.py -cFor VxRail 8.0.300 and later, enter: mcp_python vxm_backup_restore.py -cThen use prompts to change existing settings.

Support Cases