Important Update: Cohesity Products Knowledge Base Articles
All Cohesity Knowledge Base Articles are now managed via the Cohesity Support Portal: https://support.cohesity.com/s/searchunify. The Knowledge Base articles available here will not reflect the latest information or may no longer be accessible.
Linux client backup is initiated, the Bare Metal Restore (BMR) job (bmrsavecfg) fails with "Operation Status: 1" ( V-128-18 )
Problem
When the backup of a Linux client is initiated, the Bare Metal Restore (BMR) job (bmrsavecfg) fails with "Operation Status: 1" reported. Error V-128-18 can also be found in unified logs.
Error Message
BMRERR: Received BMR error: Failed to import Config file. (1)
While running the bmrsavecfg process, the job fails with the following errors seen in the Job Activity Details:
04/05/2008 04:44:51 - started process bpbrm (pid=11019)
04/05/2008 04:44:54 - Error bpbrm (pid=11019) BMRERR: Received BMR error: Failed to import Config file. (1)
04/05/2008 04:44:55 - Error bpbrm (pid=11019) BMRERR: Received BMR error: Failed sending the discovery. (1)
04/05/2008 04:44:55 - Error bpbrm (pid=11019) BMRERR: Received BMR error: BMR information discovery failed. (1)
04/05/2008 04:44:55 - end writing
Operation Status: 1
Solution
The logging levels may need to be increased. To accomplish this, from the master, run:
# /usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 119 -s DebugLevel=5 -s DiagnosticLevel=6
and on the client, run:
# /usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 121 -s DebugLevel=5 -s DiagnosticLevel=6
Run the job once more to recreate the failure.
To generate the bmrd (119) logs on the master server,
# /usr/openv/netbackup/bin/vxlogview -p 51216 -o 119 -t 01:00:00 -d all > bmrdo.txt
# /usr/openv/netbackup/bin/vxlogview -p 51216 -i 119 -t 01:00:00 -d all > bmrdi.txt
(generates for the previous hour - adjust value as necessary)
To generate bmrsavecfg (121) logs on the client, use the following commands:
# /usr/openv/netbackup/bin/vxlogview -p 51216 -o 121 -t 01:00:00 -d all > bmrsavecfgo.txt
# /usr/openv/netbackup/bin/vxlogview -p 51216 -i 121 -t 01:00:00 -d all > bmrsetuplogi.txt
(generates for the previous hour - adjust value as necessary)
Log Files:
Look for entries within the bmrd log similar to the following:
04/14/2008 08:52:32.480 [ParseClientInformation.cpp:ParseClientInformation()] Critical task 'PARTED_NUM' did not run successfully.
04/14/2008 08:52:32.480 [ParseClientInformation.cpp:ParseClientInformation()] Exiting in ParseClientInformation.cpp at 755.
04/14/2008 08:52:32.480 V-128-18 [ImportCfg.cpp:ImportConfig()] unable to parse client information
04/14/2008 08:52:32.485 [sendrecv.cpp:SendPacket()] Entering, line=524
04/14/2008 08:52:32.486 [sendrecv.cpp:SendPacket()] Exiting, line=561, return rc=5
If the error does not exist within this log, the four generated log files will need to be provided to Technical Support for research.
Resolution:
1. Ensure the parted command is available on the client. BMR runs the parted command when capturing the client disk partition information. If the command is not available on the client, the parted package will need to be installed on the client.
2. After the package is installed, the backup will need to be initiated again to ensure proper client registration to the BMR database.
Note: Revert the logging levels to default of DebugLevel=1 DiagnosticLevel=6 when troubleshooting is completed.
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.