β04-24-2012 10:44 AM
Hello Folk!
I need help about the BMR, where I have been problem. I can not run "Prepare to Restore". The following message is displayed:
The requested operation could not be completed. The server returned code 1.
[Error] V-126-8 Cannot find TrueImage date. Please make sure a full backup of this client is available.
[Error] V-126-3 'bmrprep' could not complete the requested operation.
Please see logs for additional information.
[Info] V-126-43 Cleaning up. Please wait...
Follows the configuration of my environment:
The backup policy of this client is correctly configured:
------------------------------------------------------------
Policy Name: Teste_BMR
Policy Type: MS-Windows
Active: yes
Effective date: 10/27/2011 14:50:04
Backup network drvs: no
Collect TIR info: yes, with move detection
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: no
Policy Priority: 7
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: yes
Residence: Stu_DedupObras
Volume Pool: TapeOut
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Application Discovery: no
Discovery Lifetime: 28800 seconds
Granular Restore Info: yes
Ignore Client Direct: no
HW/OS/Client: Windows-x86 Windows2008 SRVXENAPP02
Include: ALL_LOCAL_DRIVES
System State:\
Shadow Copy Components:\
Schedule: Full_Sexta
Type: Full Backup
Frequency: every 1 day
Maximum MPX: 10
Synthetic: 0
PFI Recovery: 0
Retention Level: 4 (2 months)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
------------------------------------------------------------
Can anybody help me?
Tanks!!
Hugs,
Jonas Presse
Solved! Go to Solution.
β05-29-2012 10:17 AM
Hello everyone!
Unfortunately we could not solve this problem, but became clear that this is a problem punctual and specific of server that we are trying to accomplish the DR.
The case at Symantec we had previously opened was closed because the customer no more wishes to perform the DR of the BMR of this server, which will be disabled.
I thank to Nathan Kippen that helped me a lot to try to resolve this case.
Best regards!
Jonas Presse
β04-24-2012 11:03 AM
Did you get a good system state?
β04-24-2012 01:29 PM
Hi Nathan!
Yes, I did. The backup status code was "0", without error messages.
Have you any idea?
Tanks!
Hugs,
Jonas Presse
β04-24-2012 09:26 PM
Check your bprd log on your master when doing the prepare to restore... you'll see that it will validate that you have good backups for the client in question. Sometimes it could be a hostname mismatch or something simple. Post your bprd if you'd like me to take a look. Also please indicate the client name.
β04-25-2012 06:46 AM
Hi Nathan!
I saw several error messages in bprd log, like this:
09:34:17.052 [3884.9384] <2> get_type_of_client_free_browse: db_getCLIENT_by_hostname() failed: no entity was found (227)
But, I could not identify the problem.
The client hostname is "SRVXENAPP02".
The log is attached.
Have you any idea?
Thank you!
β04-25-2012 08:15 PM
Looks like there is something wrong with the system state backup..
It is missing the following paths:
/System State/_SharedHardlinkData_/
/System State/System Files/
You will see the following repeated which references the above paths:
<2> fileslist: begin db communication
<2> fileslist: criteria sent to db mgr
<2> fileslist: unexpected return value from db_FLISTreceive: no entity was found 227
<2> process_request: fileslist failed - EC status = no entity was found
<2> process_request: EXIT STATUS 227
What we should see is:
<2> fileslist: begin db communication
<2> fileslist: criteria sent to db mgr
<2> process_request: EXIT STATUS 0
The only thing I can think of is try backing up the client again with the BPBKAR log enabled on the client
and verbose turned up. Then we can check the log for errors backing up the system state.
Please make sure your are backing up the client using the ALL_LOCAL_DRIVES directive for the backup selection list.
Using that will help avoid missing critical files.
β04-25-2012 08:17 PM
Looks like this was an issue for another user:
https://www-secure.symantec.com/connect/forums/bmr-error-v-126-8-v-126-3#comment-5339561
By using the ALL_LOCAL_DRIVES directive is resolved their problem as well.
Good Luck!
β04-26-2012 02:06 PM
Hi Nathan!
Thank you for your sugestions, but apparently it is all correct.
The 'Include List' is "ALL_LOCAL_DRIVES" and the backups status is "0". I did not see error message in previous backup. Follow attached the backup status log.
However I will do a new backup with verbose logging set up for "5" for analise the "bpbkar" log, according your recomendation.
In parallel, I opened a new case in Symantec Support for help me in this issue.
One more time, thaks by your sugestions.
I will report when I have a new state.
Hugs,
Jonas
β04-26-2012 02:53 PM
1. Enable bmrprep log on the BMR Server.
vxlogcfg -a -p 51216 -o 126 -s DebugLevel=6 -s DiagnosticLevel=6
2. Perform "Prepare to Restore" and once it fails collect the bmrprep log by running following command.
vxlogview -i 126 > /tmp/bmrprep.log
post log.
β04-27-2012 06:46 AM
Hi Nathan!
Follow:
4/27/2012 08:59:37.920 [Error] V-126-3 'bmrprep' could not complete the requested operation.
Please see logs for additional information.
4/27/2012 08:59:37.920 [Info] V-126-43 Cleaning up. Please wait...
4/27/2012 08:59:54.753 [CBmr::readXml(xml, len, filter)] Replaced object in m_vConfig.
4/27/2012 08:59:58.466 [Error] V-126-8 Cannot find TrueImage date. Please make sure a full backup of this client is available.
About the backup with the verbose logging activated, I did not see anyone relevant error message.
Apparently no have problem with the backup. Follow attached the "bpbkar" log.
Thanks!
β04-27-2012 07:51 AM
Hmmmmmm..
I did see:
4/24/2012 10:28:38.230 [Info] V-126-11 BMR client 'srvxenapp02.racional.com' is ready to be restored. Please boot the client to proceed. 4/24/2012 10:29:12.582 [CBmr::readXml(xml, len, filter)] Replaced object in m_vConfig. 4/24/2012 10:29:17.886 [Error] V-126-8 Cannot find TrueImage date. Please make sure a full backup of this client is available.
Does your master server use the FQDN or short name?
check ...\netbackup\db\images\
and see if you have a folder called 'srvxenapp02.racional.com' or if it is just named 'srvxenapp02'.
I'm moving towards it just might be a name resolution issue. Compare the client name in the netbackup policy to the client name setting that is found in the client's host properties .
β04-27-2012 04:23 PM
Hi Nathan!
You are right.
The Master Server use FQDN:
- srvnetbkp.racional.com
The backup policy had the client:
- srvxenapp02
But, the 'Client Name' was:
- srvxenapp02.racional.com
I removed the domain name of this Client. So, the 'Client Name' was:
- srvxenapp02
After that, I removed this Client of the 'Bare Metal Restore Clients' and restarted her full backup.
When the backup finished, I created a 'New Client Configuration' on the 'Bare Metal Restore Clients' about this Client and I retried run 'Prepare to Restore' but, occured the same error again.
So, I did the follow steps:
1) I removed all entries related the Client "srvxenapp02" of all policies.
2) After that, I removed the Client of the 'Bare Metal Restore Clients'.
3) I removed also the entry related the Client "srvxenapp02" into 'Client Attributes' of the 'Host Properties' about the Master Server.
4) Then I reinserted the domain ".racional.com" into her 'Client Name' of this Client ("srvxenapp02.racional.com").
5) After this changes, I inserted the Client "srvxenapp02.racional.com" only in policy "Teste_BMR" and inserted the Client "srvxenapp02.racional.com" into 'Client Attributes' of the 'Host Properties' about the Master Server.
6) After all this, I restarted her full backup.
7) When the backup finished, I created a 'New Client Configuration' on the 'Bare Metal Restore Clients' about this Client and I retried run 'Prepare to Restore' but, occured the same error again.
:(
Hugs!
β04-28-2012 08:02 PM
Hmmm...
So in Backup Archive Restore, on the client, you have set the client name to be srvxenapp02.racional.com (This can also be done through the Administration Console by going to host properities --> clients --> srvxenapp02.racional.com)
You can confirm this by running on the master server ..\netbackup\bin\admincmd\bpgetconfig -M srvxenapp02.racional.com
In the policy the client name has been set to srvxenapp02.racional.com
The policy attributes has BMR enabled
The full backup is exiting with status 0
The bmrsaveconfig process in the parent job is completing successfully
The client version is 7.1.0.3
The master server version is at least 7.1.0.3
If you go to the client configuration in BMR client listing you'll see the client named srvxenapp02.racional.com
In ..netbackup\db\images\ directory on master you see a folder called srvxenapp02.racional.com
If all these things are true and you still get the following error:
4/24/2012 10:28:38.230 [Info] V-126-11 BMR client 'srvxenapp02.racional.com' is ready to be restored. Please boot the client to proceed. 4/24/2012 10:29:12.582 [CBmr::readXml(xml, len, filter)] Replaced object in m_vConfig. 4/24/2012 10:29:17.886 [Error] V-126-8 Cannot find TrueImage date. Please make sure a full backup of this client is available.
..then please let me know the solution once symantec helps you out.. I'm stuck.
β04-30-2012 04:56 AM
Hi Nathan!
Apparently everything is correct. I do not know what can be wrong.
As soon as I receive a new status of Symantec, I will notify.
Thank you!
β05-09-2012 07:38 AM
Any updates?
β05-14-2012 06:05 AM
Hi Nathan!
Unfortunately not yet.
The customer does not need more of the recovery, but I'm awaiting the return of the Symantec Technical Support to find out what the problem was.
Once you have an answer, I will publish.
Thank you for helping me in this case!
Hugs!
Jonas Presse
β05-29-2012 10:17 AM
Hello everyone!
Unfortunately we could not solve this problem, but became clear that this is a problem punctual and specific of server that we are trying to accomplish the DR.
The case at Symantec we had previously opened was closed because the customer no more wishes to perform the DR of the BMR of this server, which will be disabled.
I thank to Nathan Kippen that helped me a lot to try to resolve this case.
Best regards!
Jonas Presse