Unsolved
This post is more than 5 years old
1 Rookie
•
1 Message
0
2673
July 28th, 2017 03:00
Avamar 5 gsan failed to rollback
Hi All,
I am battling to start gsan and can not roll back. the checkpoints are available but fails with this error:
y(es), n(o), q(uit/exit): y
dpnctl: INFO: Initiating rollback to "cp.20170723071034" with gsan restart (this may take some time)...
dpnctl: INFO: To monitor progress, run in another window: tail -f /tmp/dpnctl-gsan-restart-output-21078
dpnctl: ERROR: error return from "/usr/bin/yes no | /usr/local/avamar/bin/rollback.dpn --cptag="cp.20170723071034"" - exit status 255
dpnctl: ERROR: 7 errors seen in output of "/usr/bin/yes no | /usr/local/avamar/bin/rollback.dpn --cptag="cp.20170723071034""
dpnctl: ERROR: error return from "/usr/bin/yes no | /usr/local/avamar/bin/rollback.dpn --cptag="cp.20170723071034"" - exit status 255
dpnctl: ERROR: gsan is not up or is exhibiting errors - not performing MCS restore
dpnctl: ERROR: MCS restore did not succeed, so not restarting MCS
dpnctl: INFO: EMS is already running.
dpnctl: ERROR: cannot resume backup scheduler: gsan is down and MCS is down
dpnctl: ERROR: gsan is not up, so not resuming maintenance cron jobs
dpnctl: INFO: dtlt is already running.
dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]
any advice or help would be appreciated
ionthegeek
2 Intern
•
2K Posts
0
July 28th, 2017 06:00
The output from the failed rollback.dpn command would have been recorded in /usr/local/avamar/var/log/dpnctl.log and this output should provide more information about the cause of the failure. However, the dpnctl logs are not easy to read since the entries may not appear in chronological order (this is because the dpnctl log includes log outputs from other commands and the output from each command will appear in one block).
If you can find the rollback.dpn output in the dpnctl.log, please post it here and I can try to assist further. However, opening a service request for this issue would probably be your best option.