Start a Conversation

Unsolved

This post is more than 5 years old

AA

1474

June 18th, 2019 22:00

Windows 2016 BMR

I am trying to have a BMR backup and test how can I protect my environment from disaster according to https://www.emc.com/collateral/TechnicalDocument/docu61066.pdf page 15 I need to setup a group with specific settings, couldn't verify step 2 since I couldn't locate the option. when I try to start the backup it failed with the following error message

6/19/2019 8:47:07 AM Step (1 of 5): nsrjobd has made a request to start this savegrp with PID-10284.
6/19/2019 8:47:07 AM Action backup traditional 'backup' has initialized as 'backup action job' with job id 227093
6/19/2019 8:47:07 AM Step (2 of 5): Querying the group or policy for the configured group of clients with the savegrp PID-10284.
6/19/2019 8:47:07 AM protbmr:All requested level=incr
6/19/2019 8:47:07 AM Step (3 of 5): The group or policy information has been successfully returned.
6/19/2019 8:47:07 AM Action backup traditional will run up to 100 jobs in parallel
6/19/2019 8:47:07 AM Step (4 of 5): Creating a savefs job for all the configured clients.
6/19/2019 8:47:07 AM Creating a 'All' job on the host 'protbmr'.
6/19/2019 8:47:07 AM Policy 'FileSystem', workflow 'FileSystem-Daily', action 'backup', group 'test'.
6/19/2019 8:47:07 AM Starting action backup traditional 'backup', which has 1 clients.
6/19/2019 8:47:07 AM Starting a session on the host 'protbmr' to execute the job 'protbmr:All', which scans the file system to determine the files for backup.
6/19/2019 8:47:07 AM The job 'protbmr:All' has been started on the client 'protbmr'.
6/19/2019 8:47:07 AM protbmr:All started
6/19/2019 8:47:07 AM savefs -s backupserver -c protbmr -g test -p -l full -R -v
6/19/2019 8:47:12 AM Group test waiting for 1 jobs (0 awaiting restart) to complete.
6/19/2019 8:47:25 AM protbmr:C:\
6/19/2019 8:47:25 AM level=full, vers=pools, p=4
6/19/2019 8:47:25 AM protbmr:D:\
6/19/2019 8:47:25 AM level=full, vers=pools, p=4
6/19/2019 8:47:25 AM protbmr:WINDOWS ROLES AND FEATURES:\
6/19/2019 8:47:25 AM level=full, vers=pools, p=4
6/19/2019 8:47:25 AM protbmr:DISASTER_RECOVERY:\
6/19/2019 8:47:25 AM level=full, vers=pools, p=4
6/19/2019 8:47:25 AM The job 'protbmr:All' on the host 'protbmr' has been completed.
6/19/2019 8:47:25 AM protbmr:All succeeded.
6/19/2019 8:47:25 AM protbmr:All The job has successfully scanned the file system on the host 'protbmr'. The main save will now be started.
6/19/2019 8:47:25 AM test:protbmr:All See the file 'E:\nsr\logs\policy\FileSystem\FileSystem-Daily\backup_227093_logs\227094.log' for command output.
6/19/2019 8:47:25 AM Probe result returned DISASTER_RECOVERY save set for client protbmr.
6/19/2019 8:47:25 AM Step (5 of 5): Creating a pseudo_saveset job for all the configured clients.
6/19/2019 8:47:25 AM Creating a save job for the save set 'pseudo_saveset' on the host 'protbmr'.
6/19/2019 8:47:25 AM Constructing the save command for the save set 'pseudo_saveset' on the host 'protbmr': save -LL -s backupserver -g FileSystem/FileSystem-Daily/backup/test -a "*policy action jobid=227093" -a "*policy name=FileSystem" -a "*policy workflow name=FileSystem-Daily" -a "*policy action name=backup" -y "Fri Jul 19 23:59:59 GMT+0300 2019" -w "Fri Jul 19 23:59:59 GMT+0300 2019" -m protbmr -b FS_Bkp_Pool -o "\"RENAMED_DIRECTORIES:index_lookup=on;REQUESTED_LEVEL:level=incr;\"" -l incr -q -W 78 -N pseudo_saveset "C:\\" "D:\\" "WINDOWS ROLES AND FEATURES:\\" "DISASTER_RECOVERY:\\".
6/19/2019 8:47:25 AM Executing a 'pseudo_saveset' job on the host 'protbmr'. This job is an anchor save set for the workflow, and will be completed at the end of the client's backup.
6/19/2019 8:47:25 AM protbmr:pseudo_saveset started
6/19/2019 8:47:25 AM save -LL -s backupserver -g FileSystem/FileSystem-Daily/backup/test -a "*policy action jobid=227093" -a "*policy name=FileSystem" -a "*policy workflow name=FileSystem-Daily" -a "*policy action name=backup" -y "Fri Jul 19 23:59:59 GMT+0300 2019" -w "Fri Jul 19 23:59:59 GMT+0300 2019" -m protbmr -b FS_Bkp_Pool -o "\"RENAMED_DIRECTORIES:index_lookup=on;REQUESTED_LEVEL:level=incr;\"" -l incr -q -W 78 -N pseudo_saveset "C:\\" "D:\\" "WINDOWS ROLES AND FEATURES:\\" "DISASTER_RECOVERY:\\"
6/19/2019 8:47:50 AM Unable to handle job monitor message: Unable to add the job to monitor list: No entry found for save set '\\?\VOLUME{A9626CD2-0000-0000-0000-100000000000}\' in client 'protbmr'.
6/19/2019 8:47:54 AM The save job for the save set 'D:\' on the host 'protbmr' has been completed.
6/19/2019 8:47:54 AM Job 227098 for client protbmr exited with return code 5
6/19/2019 8:47:54 AM Job 227098 host: protbmr savepoint: D:\ had ERROR indication(s) at completion
6/19/2019 8:47:54 AM protbmr:D:\ failed.
6/19/2019 8:47:54 AM protbmr:D:\ will retry 1 more time(s).
6/19/2019 8:47:54 AM protbmr:D:\ next retry in 1 seconds.
6/19/2019 8:47:54 AM The save job for the save set 'C:\' on the host 'protbmr' has been completed.
6/19/2019 8:47:54 AM Job 227097 for client protbmr exited with return code 5
6/19/2019 8:47:54 AM Job 227097 host: protbmr savepoint: C:\ had ERROR indication(s) at completion
6/19/2019 8:47:54 AM protbmr:C:\ failed.
6/19/2019 8:47:54 AM protbmr:C:\ will retry 1 more time(s).
6/19/2019 8:47:54 AM protbmr:C:\ next retry in 1 seconds.
6/19/2019 8:48:03 AM The save job for the save set 'pseudo_saveset' on the host 'protbmr' has been completed.
6/19/2019 8:48:03 AM Job 227095 with command 'save -LL -s backupserver -g FileSystem/FileSystem-Daily/backup/test -a "*policy action jobid=227093" -a "*policy name=FileSystem" -a "*policy workflow name=FileSystem-Daily" -a "*policy action name=backup" -y "Fri Jul 19 23:59:59 GMT+0300 2019" -w "Fri Jul 19 23:59:59 GMT+0300 2019" -m protbmr -b FS_Bkp_Pool -o "\"RENAMED_DIRECTORIES:index_lookup=on;REQUESTED_LEVEL:level=incr;\"" -l incr -q -W 78 -N pseudo_saveset "C:\\" "D:\\" "WINDOWS ROLES AND FEATURES:\\" "DISASTER_RECOVERY:\\"' for client protbmr exited with return code 1
6/19/2019 8:48:03 AM Job 227095 host: protbmr savepoint: pseudo_saveset had ERROR indication(s) at completion
6/19/2019 8:48:03 AM protbmr:pseudo_saveset failed.
6/19/2019 8:48:03 AM protbmr:pseudo_saveset will retry 1 more time(s).
6/19/2019 8:48:03 AM protbmr:pseudo_saveset next retry in 1 seconds.
6/19/2019 8:48:03 AM test:protbmr:pseudo_saveset See the file 'E:\nsr\logs\policy\FileSystem\FileSystem-Daily\backup_227093_logs\227095.log' for command output.
6/19/2019 8:48:04 AM Group test waiting for 1 jobs (1 awaiting restart) to complete.
6/19/2019 8:48:04 AM Constructing the save command for the save set 'pseudo_saveset' on the host 'protbmr': save -LL -s backupserver -g FileSystem/FileSystem-Daily/backup/test -a "*policy action jobid=227093" -a "*policy name=FileSystem" -a "*policy workflow name=FileSystem-Daily" -a "*policy action name=backup" -y "Fri Jul 19 23:59:59 GMT+0300 2019" -w "Fri Jul 19 23:59:59 GMT+0300 2019" -m protbmr -b FS_Bkp_Pool -o "\"RENAMED_DIRECTORIES:index_lookup=on;REQUESTED_LEVEL:level=incr;\"" -l incr -q -W 78 -N pseudo_saveset "C:\\" "D:\\" "WINDOWS ROLES AND FEATURES:\\" "DISASTER_RECOVERY:\\".
6/19/2019 8:48:04 AM Executing a 'pseudo_saveset' job on the host 'protbmr'. This job is an anchor save set for the workflow, and will be completed at the end of the client's backup.
6/19/2019 8:48:04 AM protbmr:pseudo_saveset started
6/19/2019 8:48:04 AM save -LL -s backupserver -g FileSystem/FileSystem-Daily/backup/test -a "*policy action jobid=227093" -a "*policy name=FileSystem" -a "*policy workflow name=FileSystem-Daily" -a "*policy action name=backup" -y "Fri Jul 19 23:59:59 GMT+0300 2019" -w "Fri Jul 19 23:59:59 GMT+0300 2019" -m protbmr -b FS_Bkp_Pool -o "\"RENAMED_DIRECTORIES:index_lookup=on;REQUESTED_LEVEL:level=incr;\"" -l incr -q -W 78 -N pseudo_saveset "C:\\" "D:\\" "WINDOWS ROLES AND FEATURES:\\" "DISASTER_RECOVERY:\\"
6/19/2019 8:48:09 AM Group test waiting for 1 jobs (0 awaiting restart) to complete.
6/19/2019 8:48:28 AM Unable to handle job monitor message: Unable to add the job to monitor list: No entry found for save set '\\?\VOLUME{A9626CD2-0000-0000-0000-100000000000}\' in client 'protbmr'.
6/19/2019 8:48:30 AM The save job for the save set 'C:\' on the host 'protbmr' has been completed.
6/19/2019 8:48:30 AM Job 227102 for client protbmr exited with return code 5
6/19/2019 8:48:30 AM Job 227102 host: protbmr savepoint: C:\ had ERROR indication(s) at completion
6/19/2019 8:48:30 AM protbmr:C:\ failed.
6/19/2019 8:48:30 AM protbmr:C:\ will retry 1 more time(s).
6/19/2019 8:48:30 AM protbmr:C:\ next retry in 1 seconds.
6/19/2019 8:48:30 AM The save job for the save set 'D:\' on the host 'protbmr' has been completed.
6/19/2019 8:48:30 AM Job 227101 for client protbmr exited with return code 5
6/19/2019 8:48:30 AM Job 227101 host: protbmr savepoint: D:\ had ERROR indication(s) at completion
6/19/2019 8:48:30 AM protbmr:D:\ failed.
6/19/2019 8:48:30 AM protbmr:D:\ will retry 1 more time(s).
6/19/2019 8:48:30 AM protbmr:D:\ next retry in 1 seconds.
6/19/2019 8:48:42 AM The save job for the save set 'pseudo_saveset' on the host 'protbmr' has been completed.
6/19/2019 8:48:42 AM Job 227099 with command 'save -LL -s backupserver -g FileSystem/FileSystem-Daily/backup/test -a "*policy action jobid=227093" -a "*policy name=FileSystem" -a "*policy workflow name=FileSystem-Daily" -a "*policy action name=backup" -y "Fri Jul 19 23:59:59 GMT+0300 2019" -w "Fri Jul 19 23:59:59 GMT+0300 2019" -m protbmr -b FS_Bkp_Pool -o "\"RENAMED_DIRECTORIES:index_lookup=on;REQUESTED_LEVEL:level=incr;\"" -l incr -q -W 78 -N pseudo_saveset "C:\\" "D:\\" "WINDOWS ROLES AND FEATURES:\\" "DISASTER_RECOVERY:\\"' for client protbmr exited with return code 1
6/19/2019 8:48:42 AM Job 227099 host: protbmr savepoint: pseudo_saveset had ERROR indication(s) at completion
6/19/2019 8:48:42 AM protbmr:pseudo_saveset failed.
6/19/2019 8:48:42 AM test:protbmr:pseudo_saveset See the file 'E:\nsr\logs\policy\FileSystem\FileSystem-Daily\backup_227093_logs\227099.log' for command output.
6/19/2019 8:48:47 AM Action backup traditional 'backup' with job id 227093 is exiting with status 'failed', exit code 1


Networker version 9.2.1.5

OS hosts Networker server and client Window server 2016

I have removed full server name from log file

2.4K Posts

June 19th, 2019 04:00

'return code 5' represents the Windows error message "Access denied". I am not sure what you are doing. - What you refer to is the BMR. The document referes to BMR with NMM 9.0 - According to his procedure/document Windows 2016 is not yet supported with NW 9.2.1. - You mention 'your environment' which lets me guess that you want to deal with NW/Windows clients in general. In this case, you do not need NMM but the standard NW client software and the Windows DR disk which is delivered with the NW software. For more details how to run a DR for a standard NW/Windows client, please see the NW Admin Guide. - Make sure that the NW client has been installed with the appropriate rights/user account.

1 Rookie

 • 

4 Posts

June 20th, 2019 04:00

Hi Bingo.1

I'm trying to take something similar to snapshot using BMR in case of disaster recover, I can rollback to this snapshot without having to reinstall my application.

 

Regarding Windows 2016 I have asked our professional service team (one of DELL EMC subcontractors) and they advised BMR is supported, I guess I will have to stick to the document and downgrade my test machine to Windows server 2012 and try again, since it is not working at all for me.

Thank you.

2.4K Posts

June 21st, 2019 02:00

I do not think that switching to an older OS will solve the issue.

And I personally think that this is a good solution.

 

If we are talking about a virtual environment (especially VMware), may I suggest that you install the NetWorker Virutat Protection (NVP) solution. We have done it for a few servers. It is pretty simple to install, very effective (due to Change Block Tracking, CBT), reliable, easy to use and very fast with respect to recover a VM. However, it need a Data Domain Boost backup device.

 

No Events found!

Top