11-19-2012 09:30 AM
Master = 7.1.0.3 2008 R2
Client = 7.1 2 2008 R2
Running a test restore of a Symantec EV server with an attached JBOD. The restore is being sent back to the original system to a temp dir. It fails with a status code 24. See job details below. The system has two local drives. The C: partition and a E: for the direct attached JBOD. The verbose shows "Critical bptm(pid=5644) sts_get_lsu_prop_byname on LSU P:\ failed: 2060013 no more entries
11/19/2012 12:21:26 PM - Critical bptm(pid=5644) Invalid storage device: P:\ no more entries", not sure what the P:\ is. Any help is greatly appreciated.
11/19/2012 12:21:11 PM - begin Restore
11/19/2012 12:21:14 PM - restoring image ma-atl191_1353165460
11/19/2012 12:21:17 PM - Info bpbrm(pid=7544) ma-atl191 is the host to restore to
11/19/2012 12:21:17 PM - Info bpbrm(pid=7544) reading file list from client
11/19/2012 12:21:21 PM - connecting
11/19/2012 12:21:21 PM - Info bpbrm(pid=7544) starting bptm
11/19/2012 12:21:25 PM - Info tar32(pid=59692) Restore started
11/19/2012 12:21:25 PM - connected; connect time: 00:00:04
11/19/2012 12:21:25 PM - Info bptm(pid=5644) start
11/19/2012 12:21:26 PM - started process bptm (5644)
11/19/2012 12:21:26 PM - Info bpdm(pid=5644) reading backup image
11/19/2012 12:21:26 PM - Info bptm(pid=5644) using 32 data buffers
11/19/2012 12:21:26 PM - Info bptm(pid=5644) spawning a child process
11/19/2012 12:21:26 PM - Info bptm(pid=5644) child pid: 8232
11/19/2012 12:21:26 PM - Info bptm(pid=8232) start
11/19/2012 12:21:26 PM - started process bptm (8232)
11/19/2012 12:21:26 PM - Critical bptm(pid=5644) sts_get_lsu_prop_byname on LSU P:\ failed: 2060013 no more entries
11/19/2012 12:21:26 PM - Critical bptm(pid=5644) Invalid storage device: P:\ no more entries
11/19/2012 12:21:26 PM - Critical bptm(pid=5644) failure to open disk at path P:\: plug-in reports error 2060013
11/19/2012 12:21:27 PM - Info bptm(pid=5644) EXITING with status 83 <----------
11/19/2012 12:21:27 PM - Error bptm(pid=8232) The following files/folders were not restored:
11/19/2012 12:21:27 PM - Error bptm(pid=8232) UTF - /E/EnterpriseVault/MBAVS01/MBAVS01PTN02/2012/10-25/
11/19/2012 12:21:27 PM - Error bptm(pid=8232) UTF - /E/EnterpriseVault/MBAVS01/MBAVS01PTN02/2012/10-25/1/
11/19/2012 12:21:28 PM - Error bptm(pid=8232) UTF - /E/EnterpriseVault/MBAVS01/MBAVS01PTN02/2012/10-25/1/07A/
11/19/2012 12:21:28 PM - Error bptm(pid=8232) UTF - /E/EnterpriseVault/MBAVS01/MBAVS01PTN02/2012/10-25/1/07A/107A9EA98CF6267994842EED7B801461.DVS
11/19/2012 12:21:28 PM - Error bptm(pid=8232) UTF - /E/EnterpriseVault/MBAVS01/MBAVS01PTN02/2012/10-25/1/07A/107AB7F29B0E13430D264C914169AA41.DVS
11/19/2012 12:21:28 PM - Error bptm(pid=8232) UTF - /E/EnterpriseVault/MBAVS01/MBAVS01PTN02/2012/10-25/1/07A/107AF0400F5F311371760C0DD3BB15D1.DVS
11/19/2012 12:21:28 PM - Error bptm(pid=8232) UTF - /E/EnterpriseVault/MBAVS01/MBAVS01PTN02/2012/10-25/1/07A/107AF05245CF1E3AD0A8A26F9945C8A1.DVS
11/19/2012 12:21:28 PM - Error bptm(pid=8232) UTF - /E/EnterpriseVault/MBAVS01/MBAVS01PTN02/2012/10-25/1/07A/107AF05245CF1E3AD0A8A26F9945C8A1~05~21630E30~00~1.DVSSP
11/19/2012 12:21:28 PM - Error bptm(pid=8232) UTF - /E/EnterpriseVault/MBAVS01/MBAVS01PTN02/2012/10-25/1/07A/107AF0BF0A006C7982AD7813EF96D261.DVS
11/19/2012 12:21:28 PM - Error bptm(pid=8232) UTF - /E/EnterpriseVault/MBAVS01/MBAVS01PTN02/2012/10-25/1/07A/107AF0BF0A006C7982AD7813EF96D261~69~D8BDD802~00~1.DVSSP
11/19/2012 12:21:28 PM - Error bptm(pid=8232) more than 10 files were not restored, remaining ones are shown in the progress log.
11/19/2012 12:22:27 PM - Warning bprd(pid=51828) Restore must be resumed prior to first image expiration on 12/18/2012 10:17:40 AM
11/19/2012 12:22:27 PM - end Restore; elapsed time: 00:01:16
socket write failed(24)
Solved! Go to Solution.
11-26-2012 01:09 PM
Probably because you have Media host override configured in Host Properties -> Master -> General Server ?
Please check and let us know.
11-19-2012 11:23 AM
bpimagelist -backupid ma-atl191_1353165460 -L
please post the output.
11-19-2012 12:35 PM
The backup was done to a Storage Unit located on the P-drive on the media server.
Backup was done on Sat, 17 Nov 2012 at 15:17 to this STU. What has happened to this Disk STU since Saturday?
11-19-2012 12:57 PM
marianne,
i wonder, how did you say about the backup time.. any trick?
did you revirce calucated from this
11/19/2012 12:22:27 PM - Warning bprd(pid=51828) Restore must be resumed prior to first image expiration on 12/18/2012 10:17:40 AM
11-19-2012 01:17 PM
I should have caught that. This backup was aimed to a DSU. The P: is still connected to the media server. It's a NTFS and was configured via SnapDrive as a LUN.
11-19-2012 01:20 PM
Client: ma-atl191
Backup ID: ma-atl191_1353165460
Policy: MA-ATL191-EV-MBAVS01_02
Policy Type: MS-Windows (13)
Proxy Client: (none specified)
Creator: root
Name1: (none specified)
Sched Label: Full
Schedule Type: FULL (0)
Retention Level: 1 month (3)
Backup Time: 11/17/2012 10:17:40 AM (1353165460)
Elapsed Time: 74806 second(s)
Expiration Time: 12/18/2012 10:17:40 AM (1355843860)
Compressed: no
Client Encrypted: no
Kilobytes: 122364897
Number of Files: 4838847
Number of Copies: 1
Number of Fragments: 1
Histogram: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
DB Compressed: no
Files File Name: MA-ATL191-EV-MBAVS01_02_1353165460_FULL.f
Previous Backup Files File Name: (none specified)
Parent Backup Image File Name: (none specified)
SW Version: (none specified)
Options: 0x0
MPX: 0
TIR Info: 0
TIR Expiration: 12/31/1969 7:00:00 PM (0)
Keyword: (none specified)
Ext Security Info: no
File Restore Raw: no
Image Dump Level: 0
File System Only: no
Object Descriptor: (none specified)
Previous BI Time: 12/31/1969 7:00:00 PM (0)
BI Full Time: 12/31/1969 7:00:00 PM (0)
Request Pid: 0
Backup Status: 0
Stream Number: 2
Backup Copy: Standard (0)
Files File size: 709838993
PFI type: 0
IMAGE_ATTRIBUTE: 0
Primary Copy: 1
Image Type: 0 (Regular)
Job ID: 62644
Num Resumes: 0
Resume Expiration: 12/31/1969 7:00:00 PM (0)
Data Classification: (none specified)
Data_Classification_ID: (none specified)
Storage Lifecycle Policy: (none specified)
Storage Lifecycle Policy Version: 0
STL_Completed: 0
Remote Expiration Time: 12/31/1969 7:00:00 PM (0)
Origin Master Server: (none specified)
Origin Master GUID: (none specified)
Snap Time: 11/17/2012 8:37:01 AM (1353159421)
Copy number: 1
Fragment: 1
Kilobytes: 122364897
Remainder: 0
Media Type: Disk (0)
Density: qscsi (0)
File Num: 0
ID: P:\\ma-atl191_1353165460_C1_F1
Host: ma-atlmaster1.us.manh.com
Block Size: 262144
Offset: 0
Media Date: 12/31/1969 7:00:00 PM (0)
Dev Written On: -1
Flags: 0x0
Media Descriptor: ma-atlmaster1.us.manh.com
Expiration Time: 12/18/2012 10:17:40 AM (1355843860)
MPX: 0
retention_lvl: 1 month (3)
Try to Keep Time: 12/31/1969 7:00:00 PM (0)
Copy Creation Time: 11/18/2012 7:04:26 AM (1353240266)
checkpoint: 0
resume num: 0
Key tag: *NULL*
STL tag: *NULL*
11-19-2012 01:22 PM
It is the 10-digit number in the image id: ma-atl191_1353165460
To convert Unix time to normal, run this on the master:
bpdbm -ctime <10-digit-number>
See http://www.symantec.com/docs/TECH11522
When I don't have access to NBU server, I use this URL: http://www.onlineconversion.com/unix_time.htm
11-19-2012 09:51 PM
Thank you very much Marianne, its a great info..
11-19-2012 09:53 PM
yes,
bpimagelist also confirming that..
Snap Time: 11/17/2012 8:37:01 AM (1353159421)
Copy number: 1
Fragment: 1
Kilobytes: 122364897
Remainder: 0
Media Type: Disk (0)
Density: qscsi (0)
File Num: 0
ID: P:\\ma-atl191_1353165460_C1_F1
Host: ma-atlmaster1.us.manh.com
you need to make P Drive accessable.
11-26-2012 12:25 PM
The DSU P: is still present to the system, in this case happens to be the Master server. Why during a restore woould this drive not been seen?
11-26-2012 12:36 PM
It is present when you looked now - can we say it was present when the restore was run ?
11-26-2012 12:46 PM
11/19/2012 12:21:26 PM - Critical bptm(pid=5644) sts_get_lsu_prop_byname on LSU P:\ failed: 2060013 no more entries
11/19/2012 12:21:26 PM - Critical bptm(pid=5644) Invalid storage device: P:\ no more entries
11/19/2012 12:21:26 PM - Critical bptm(pid=5644) failure to open disk at path P:\: plug-in reports error 2060013
Invalid storage device - says it all, there was a problem with this drive at the time of restore!
11-26-2012 01:09 PM
Probably because you have Media host override configured in Host Properties -> Master -> General Server ?
Please check and let us know.
11-26-2012 01:19 PM
Good thinking Marianne, that could certainly cause this.
11-27-2012 01:16 PM
That was it. I wasn't aware of such an option. Thanks.