cancel
Showing results for 
Search instead for 
Did you mean: 

RESTORE VMWARE POLICY ERROR 24

Hi all,

 

I have a problem during restore of VM machine with SAN trasport, backups are ok, but the restore I have vmware policy error 2080 and bptm exit with error "cannot write socket" error 24

 

my environment is:

1 master server 7.6.0.4 linux (6.6)

4 media server windows 2012R2 7.6.0.4 --->SAN--->datastore

vcenter + 4 esx 5.5v1

with nbd transport is ok

I tried  some solutions as:

original provisioning

thick provisionig

restore to not original esx

I changed vm hostname for destination

I have used original user of vcenter

we don't have firewall

For only (because we don't have also DD emc), I created external volume for backups image type advanced disk on media server.

 

Thans in advance

 

Rick

1 Solution

Accepted Solutions
Accepted Solution!

Some environments present the

Some environments present the VM datastores as read-only to Media servers/backup hosts.

This means that backups are fine but the media does not have write access for restores.

Another possibility is that the datastore's lun may be offline:

Extract from NBU for VMware Guide:

■ For the SAN transport mode and a restore host on Windows 2008R2, the restore
fails if the datastore’s lun is offline. The detailed status log contains messages
similar to the following:

5/22/2013 4:10:12 AM - Info tar32(pid=5832) done. status: 24:
socket write failed
5/22/2013 4:10:12 AM - Error bpbrm(pid=5792) client restore EXIT STATUS 24:
socket write failed

Make sure the status of the SAN disk on the restore host is online (not offline).
Disk status can be checked or changed using the Windows diskpart.exe utility
or the Disk Management utility (diskmgmt.msc). When the disk status reads
online, retry the restore.

View solution in original post

3 Replies
Accepted Solution!

Some environments present the

Some environments present the VM datastores as read-only to Media servers/backup hosts.

This means that backups are fine but the media does not have write access for restores.

Another possibility is that the datastore's lun may be offline:

Extract from NBU for VMware Guide:

■ For the SAN transport mode and a restore host on Windows 2008R2, the restore
fails if the datastore’s lun is offline. The detailed status log contains messages
similar to the following:

5/22/2013 4:10:12 AM - Info tar32(pid=5832) done. status: 24:
socket write failed
5/22/2013 4:10:12 AM - Error bpbrm(pid=5792) client restore EXIT STATUS 24:
socket write failed

Make sure the status of the SAN disk on the restore host is online (not offline).
Disk status can be checked or changed using the Windows diskpart.exe utility
or the Disk Management utility (diskmgmt.msc). When the disk status reads
online, retry the restore.

View solution in original post

Good...resolved changed

Good...resolved changed status SAN DISK online..

 

Thank's Marianne

 

Rick

Moved:

Re: Good...resolved changed