09-23-2010 12:16 PM
I have the following environment.
Master Server - AIX 5.3 (NBU7.0)
Media Server - Red Hat 5 (NBU 7.0)
Boot Server - Windows 2003 Standart SP2 (NBU 7.0)
When I tried to create a SRT on Boot Server Windows, I received that message.
COULD NOT ADD PLUG AND PLAY DATA FILE TO SRT
I already checked the consistency of my databases (NBDB and BMRDB) and both are OK.
I need to restore a server with my BMR backup! What can I do to resolve this issue?
That is the log.
0,51216,125,125,2,1285267166905,3472,3476,0:,49:Could not find base SRD file, so need to ask user,33:srtproc.cpp:WinPeSrtDataDlgProc(),1
0,51216,125,125,4,1285267172123,3472,3484,0:,111:Failed to open language specific srd file (C:\Program Files\Veritas\NetBackup\BareMetal\server\data\\srdEN.wim),32:srtutils.cpp:ExtractWinPeImage(),1
0,51216,125,125,5,1285267172123,3472,3484,0:,106:Looking for EN version of the srd file (C:\Program Files\Veritas\NetBackup\BareMetal\server\data\\srd.wim),32:srtutils.cpp:ExtractWinPeImage(),1
0,51216,128,125,1,1285267177470,3472,3484,0:,74:There are no entries in data in PnpInfo database for the given OS version.,27:PnpDbSearch.cpp:getPnpDbs(),1
0,51216,128,125,2,1285267177470,3472,3484,0:,46:Could not retrieve PnpInfo db from the server.,42:PnpDbSearch.cpp:getDriverListFromServer2(),1
09-23-2010 11:37 PM
you need to refer proper client installation while creating SRT . Suppose if you want to restore a windows 2003 X64 bit OS then you need copy Netbackup client version for windows X64 bit to a temp location and then give this path while creating SRT's.
09-24-2010 06:09 AM
I don't understand, Explain to me better.
09-24-2010 06:30 AM
Don't use BMR so not sure how serious this is (plus it's only for 6.5?), but there is reference to having to log a call with support :(
The Bare Metal Restore (BMR) Shared Resource Tree (SRT) creation wizard will hang when creating a Fast Restore SRT,and then fail with the error message: "could not add plug and play data file to SRT".
09-24-2010 07:12 AM
I already make this fix and don't work for me.
My databases are OK.
09-25-2010 03:15 AM
Can you please explain more which is the OS you want to recover . Boot servers should be similar to the client, suppose if you want to recover a windows client then you need a windows boot server .
For linux client you should have a linux boot server , you cannot able to create SRT's for linux clients from windows boot server.
refer this BMR videos for more information
09-25-2010 03:58 AM
Here when SRT creation wizard contacted BMR master server for plug-n-play conguration info, it did not get that info from the BMR master server.
1. Please make sure that your BMR Master server database has been updated properly to version 7.
2. Please make sure below files are available on your AIX master at /usr/openv/netbackup/baremetal/server/data/ location.
09-28-2010 05:04 AM
My boot server is Windows 2003 Enterprise Edition SP2 EN and my client to restore is ta same operation system.
I don't know more with to do.
09-28-2010 01:07 PM
Yes, there are all of files.
BMRDB.load.xml PnpDB_2003SP1.xml PnpDB_XPSP1.xml
PnPDB_2003.xml PnpDB_2003SP2.xml PnpDB_XPSP2.xml
PnpDB_2000.xml PnpDB_WinPE_2003SP1.xml RuleDB_WinPE_Compatibility.xml
PnpDB_2000SP1.xml PnpDB_WinPE_2003SP1_X64.xml dos.uncooked
PnpDB_2000SP2.xml PnpDB_WinPE_2008.xml srtDefaults.info
PnpDB_2000SP3.xml PnpDB_WinPE_2008_X64.xml unattend.txt
09-29-2010 03:06 AM
I do suspect that your BMR database is not built properly.
Please can you fire below query on your BMR master server and paste o/p of the query.
bmrs -o query -r database -table PnpInfo
The o/p should show device entries with Version = WINPE_W2K8_X64.
11-20-2010 09:17 AM
dont know whether this will help you - but I ran into the same situation (different master/bmr and boot server combination) however, I patched everything to latest and greatest and as if by magic the plug and play problem went away.
05-17-2011 10:46 AM
I am running into the exact same error. Patching the NBU server to the latest Microsoft patches has not helped. Everything was working fine in NetBackup 7.0 but I upgraded recently to version 7.1 and now when I want to prepare for restore one of the clients, it required me to create a new SRT but I am getting the same error shown at top of this thread "Could not add plug and play data file to SRT". While reading this thread, I noticed though that PnpDB_2003SP2.xml file in Veritas\Netbackup\BareMetal\server\data directory. I have another system where I have upgraded as well and there also I do not have this file..but then I wonder how come it did not complain about this file while creating SRT in NetBackup 7.0..I don't know where to get these files from..please help! Thanks in advance!
05-18-2011 12:21 AM
Did you confirm the points I had mentioned in update dated 25 sep 2010?
Basically confirm if your BMR database has been correctly upgraded to latest version.
05-19-2011 08:17 AM
I have a similar problem...
bmrs -o query -r database -table PnpInfo hangs
Any clues Mandar?
Another error, related seems to be:
0,51216,128,119,1,1305805537569,2796,1636,0:,29:Replaced object in m_vConfig.,31:CBmr::readXml(xml, len, filter),1
0,51216,128,119,1,1305807929865,1740,2124,0:,29:Replaced object in m_vConfig.,31:CBmr::readXml(xml, len, filter),1
0,51216,119,119,1,1305808781454,2796,1636,0:,67:Cannot open lockfile for reading, path=C:\BMR_SRTS\2K8_32\2796.lock,36:CWinPeSrtFacility::readSrtLockFile(),1
0,51216,128,119,2,1305811534552,1740,2124,0:,16:bad header, rc=0,25:sendrecv.cpp:RecvPacket(),1
0,51216,128,119,4,1305811534646,1740,2124,0:,67:BmrOps BMROP_QUERY, BMROP_DB, failed In CBmr::queryRequest. rc =200,55:CBmr::queryRequest(colClause, TableClause, WhereClause),1
0,51216,128,119,5,1305811534646,1740,2124,0:,30:Failed to get packages, rc=200,29:PnpDbSearch.cpp:getPackages(),1
0,51216,128,119,6,1305811534646,1740,2124,0:,46:Could not retrieve PnpInfo db from the server.,42:PnpDbSearch.cpp:getDriverListFromServer2(),1
0,51216,128,119,7,1305811534646,1740,2124,0:,31:Unable to get pnp info database,49:AddDriverFilesToWinPe.cpp:updateWinPeDriverFile(),1
0,51216,128,119,8,1305811534661,1740,2124,0:,65:An error occurred while adding drivers to the WinPE image, rc=200,32:methodsPlat.cpp:PxeAllocateSrt(),1
0,51216,119,119,1,1305811534661,1740,2124,0:,57:Error occured while attempting to unmount image. gle=1168,34:CWinPeSrtFacility::unmountSrtWim(),1
0,51216,128,119,9,1305811534677,1740,2124,0:,36:Failed to unmount the srt wim image.,32:methodsPlat.cpp:PxeAllocateSrt(),1
0,51216,128,119,1,1305812352719,660,740,0:,29:Replaced object in m_vConfig.,31:CBmr::readXml(xml, len, filter),1
0,51216,128,119,1,1305821503447,1612,308,0:,29:Replaced object in m_vConfig.,31:CBmr::readXml(xml, len, filter),1
05-19-2011 10:14 PM
I believe you are using AIX box as master server.
I suspect BMRDB is built partially when "bmrsetupmaster" was executed.
On Aix generally below problem comes, which results into partial information import into database.
I mean during bmrsetupmaster, if pnp info was not/partially populated into bmr db then during SRT creation above problem can come.
If it is ok for you to re-build BMR database then please follow above technote.
1. BMR Boot server registration records will be gone. You need to re-register BMR BS using bmrsetupboot -register
2. Any backed-up BMR client records will be cleaned. Need to take fresh BMR backup.
3. Same for existing SRTs. Create a fresh SRT.
For safer side you can back-up all BMR* files in db/data folder.
05-20-2011 02:11 AM
My master is Solaris, Mandar.
I think I'm hijaking the thread but...its not really possible to destroy it and recreate. Recall it needs to work in context...we can't take fresh BMR backups as this is on a separate network no longer connected to our clients...its in the DR lab specifically to do BMR. Incidentally the original SRT/BMR setup works fine so its not clear how this corruption has happened.
This makes me nervous...BMR is for disaster recovery. If we end up with corruption like this on a real invocation, then DR is effectively cancelled! We have no business. I hope you recognise the significance of this, as a Symantec employee.
05-20-2011 02:33 AM
Yes, definitely, Jim. I clearly understand your concern.
Ok, so here is my recommendation on this problem:
So generally such DB corruption does not happen. If in case DB fails to update or setup, bmrsetupmaster shows proper error message. The technote was the AIX specific case where due to stack memory limit bmrsetupmaster was crashing out.
Even it is possible that the problem in your environment is not because of DB content integrity.
I would recommend you open an SR with symantec on this issue. That would really help to get required information in order to debug this issue or provide any instrumented bianries.
If in case the case is related to PnP DB partial information population; then an Engineering binary solution can be provided.
You can update your SR case number here for my information.