Video Screencast Help

EXIT STATUS 185: tar did not find all the files to be restored

Created: 10 Sep 2012 • Updated: 04 Oct 2012 | 6 comments
This issue has been solved. See solution.

Hi Guys,

 

when i try to restore a VM i get the following error:

07/09/2012 10:56:19 - begin Restore
07/09/2012 11:00:08 - restoring image CSLAB-LOCSLAB16-6_1346689380
07/09/2012 11:00:08 - requesting resource @aaaaM
07/09/2012 11:00:08 - granted resource MediaID=@aaaaM;DiskVolume=emeacheddr1_lsu1;DiskPool=emealonnbu01_DR;Path=emeacheddr1_lsu1;StorageServer=emeacheddr1eth3;MediaServer=emeachenbu01
07/09/2012 11:00:17 - started process bpdm (6124)
07/09/2012 11:00:18 - started process bpdm (11536)
07/09/2012 11:00:20 - begin reading
07/09/2012 11:00:21 - end reading; read time: 00:00:01
07/09/2012 11:26:06 - requesting resource @aaaaM
07/09/2012 11:26:06 - granted resource MediaID=@aaaaM;DiskVolume=emeacheddr1_lsu1;DiskPool=emealonnbu01_DR;Path=emeacheddr1_lsu1;StorageServer=emeacheddr1eth3;MediaServer=emealonnbu01
07/09/2012 11:26:08 - connecting
07/09/2012 11:26:10 - connected; connect time: 00:00:02
07/09/2012 11:26:11 - started process bptm (13120)
07/09/2012 11:26:11 - started process bptm (19100)
07/09/2012 11:26:13 - begin reading
07/09/2012 15:47:15 - Critical bpbrm(pid=17088) from client emeachenbu01: FTL - Virtual machine restore: file write failed 
07/09/2012 15:47:15 - Critical bpbrm(pid=17088) from client emeachenbu01: FTL - Virtual machine restore: file write failed 
07/09/2012 15:47:15 - Critical bpbrm(pid=17088) from client emeachenbu01: FTL - Virtual machine restore: file write failed 
07/09/2012 15:47:15 - Critical bpbrm(pid=17088) from client emeachenbu01: FTL - Virtual machine restore: file write failed 
07/09/2012 15:47:16 - Critical bpbrm(pid=17088) from client emeachenbu01: FTL - Virtual machine restore: file write failed 
07/09/2012 15:47:16 - Critical bpbrm(pid=17088) from client emeachenbu01: FTL - Virtual machine restore: file write failed 
07/09/2012 15:47:16 - Critical bpbrm(pid=17088) from client emeachenbu01: FTL - Virtual machine restore: file write failed 
07/09/2012 15:47:16 - Critical bpbrm(pid=17088) from client emeachenbu01: FTL - Virtual machine restore: file write failed 
07/09/2012 15:47:16 - Critical bpbrm(pid=17088) from client emeachenbu01: FTL - Virtual machine restore: file write failed 
07/09/2012 15:47:16 - Critical bpbrm(pid=17088) from client emeachenbu01: FTL - Virtual machine restore: file write failed 
07/09/2012 15:47:16 - Info bpbrm(pid=17088) from client emeachenbu01: TRV - last message being suppressed after 10 occurrences
07/09/2012 16:12:21 - end reading; read time: 04:46:08
07/09/2012 16:12:26 - Error bpbrm(pid=17088) client restore EXIT STATUS 185: tar did not find all the files to be restored
07/09/2012 16:13:33 - restored image CSLAB-LOCSLAB16-6_1346689380 - (the restore failed to recover the requested files(5)); restore time 05:13:25
07/09/2012 16:13:37 - end Restore; elapsed time: 05:17:18
the restore failed to recover the requested files(5)

 

currently using Netbackup 7.0.1

 

any ideas?

Thanks

Wale

Comments 6 CommentsJump to latest comment

MuhammadFaysal's picture

 Vmware requires to use the naming resolution amongst VMware servers. please check your dns.. Is any name resolultion issue.

Marianne's picture

Please start at the beginning and share all the steps that you have taken?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Wale's picture

Hi All,

 

Sorry guys this was sort of not a netbackup issue more of a vmware issue.

The issue was because someone provisioned an IDE disk with the VM as opposed to a SCSI disk.

I was able to get around the issue by using Converter as mentioned above.

When you get the options Screen in Converter

- Edit the Devices > for "Disk Controller" Drop down and select "Scsi Bus Logic".

- If you want to set the size of the Disk at the same time, you can edit the "Data to copy" > Select "Data copy type" and drop down to "Select Volumes to copy" > Change the "Destination Size" for the disk that you want to increase

 

once done i took a backup and restored the vm with no issue.

Hope this helps someone.

 

Wale's picture

This issue has been resloved.

The issue was that the vm was originally a physical machine which was converted to a VM but was converted with the wrong option.

IDE disk was selected instead of SCSI

VM was converted out and back in again with SCSI controller selected instead of IDE. Backup and restore test was successful.  

SOLUTION