Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

image write failed: error 2060022: software error

Created: 27 Jun 2012 | 16 comments
beaumont1's picture

 

Hello,
my environment is NBU 7.5.0.3 Master + ESX 4.1. Our target storage is a Netbackup 5000 appliance as puredisk STU.
VMware backups are running fine, except for one VM on which we are getting error 84 during incremental backups ONLY.
 
Can you help fixing this issue? is it a bug?
 
Logs below:
27-giu-2012 13.21.21 - Info bpbkar32 (pid=1164) INF - Transport Type = san

27-giu-2012 13.21.26 - Critical bptm (pid=3592) image write failed: error 2060022: software error

27-giu-2012 13.21.30 - Error bptm (pid=3592) cannot write image to disk, Invalid argument

27-giu-2012 13.21.30 - Info bptm (pid=3592) EXITING with status 84 <----------

27-giu-2012 13.21.30 - Error bpbrm (pid=2820) from client 172.28.10.11: ERR - tar file write error (14)

27-giu-2012 13.21.32 - Info bpbkar32 (pid=1164) bpbkar waited 32 times for empty buffer, delayed 202 times.

27-giu-2012 13.21.33 - Info netbackupmedia (pid=3592) StorageServer=PureDisk:netbackup5000; Report=PDDO Stats for (netbackup5000): scanned: 112642 KB, CR sent: 1081 KB, CR sent over FC: 0 KB, dedup: 99.0%

27-giu-2012 13.21.34 - Error bpbrm (pid=2820) could not send server status message

bptm

 

13:21:03.734 [3592.3640] <4> write_backup: begin writing backup id 172.28.10.11_1340796053, copy 1, fragment 1, destination path PureDiskVolume

13:21:03.734 [3592.3640] <2> signal_parent: set bpbrm media ready event (pid = 2820)

13:21:03.734 [3592.3640] <2> write_data: twin_index: 0 active: 1 dont_process: 0 wrote_backup_hdr: 0 finished_buff: 0 saved_cindex: -1 twin_is_disk 1 delay_brm: 0

13:21:03.734 [3592.3640] <2> write_data: Total Kbytes transferred 0

13:21:11.409 [3592.3640] <2> write_data: first write, twin_index: 0 cindex: 0 dont_process: 1 wrote_backup_hdr: 0 finished_buff: 0

13:21:11.409 [3592.3640] <2> write_data: received first buffer (262144 bytes), begin writing data

13:21:11.487 [3592.3640] <2> send_media_kbytes_written_establish_threshold: CINDEX 0, RB Kbytes for monitoring = 1000000

13:21:26.479 [3592.3640] <16> 4060:bptm:3592:netbackupmedia2: [ERROR] PDSTS: fbu_fill_bitmap: (33936) stream_offset(1258507264) + length(8192) > (33937) stream_offset(1258507264)

13:21:26.479 [3592.3640] <16> 4060:bptm:3592:netbackupmedia2: [ERROR] PDSTS: fbu_scan_buf: fbu_fill_bitmap() failed (2060022:software error)

13:21:26.479 [3592.3640] <16> 4060:bptm:3592:netbackupmedia2: [ERROR] PDSTS: write_special_buf: fbu_scan_buf failed: (2060022:software error)

13:21:26.479 [3592.3640] <16> 4060:bptm:3592:netbackupmedia2: [ERROR] PDSTS: write_unknown_len_buf: write_special_buf() failed, byteswritten:<0>, status:<0x1> (2060022:software error)

13:21:26.479 [3592.3640] <16> 4060:bptm:3592:netbackupmedia2: [ERROR] PDSTS: impl_write_image: write_unknown_len_buf() failed (2060022:software error)

13:21:26.479 [3592.3640] <16> 4060:bptm:3592:netbackupmedia2: [ERROR] PDSTS: impl_write_image: STAT contents:

st_type=0 [NONE]

st_len=320

st_flags=0x1 [SIZE_UNKNOWN]

st_seqno=7

flags=0 [OTHER]

extents=[1]

offset=115343360

length=215552

fname=NULL


13:21:26.479 [3592.3640] <16> 4060:bptm:3592:netbackupmedia2: [ERROR] PDSTS: impl_write_image: exit (0 0x1 2060022:software error)

13:21:26.479 [3592.3640] <16> 4060:bptm:3592:netbackupmedia2: [ERROR] PDSTS: pi_write_image_v7: impl_write_image() failed (2060022:software error)

13:21:26.479 [3592.3640] <32> do_write_image: sts_write_image failed: byteswritten = 0, len = 215552

13:21:26.479 [3592.3640] <32> do_write_image: sts_write_image failed: error 2060022 (115343360 215552 0)

13:21:26.479 [3592.3640] <2> ConnectionCache::connectAndCache: Acquiring new connection for host netbackupsrv, query type 1

13:21:26.479 [3592.3640] <2> vnet_pbxConnect: pbxConnectEx Succeeded

13:21:26.479 [3592.3640] <2> logconnections: BPDBM CONNECT FROM 172.28.28.124.62091 TO 172.28.28.30.1556 fd = 1432

13:21:26.479 [3592.3640] <8> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2

13:21:26.495 [3592.3640] <2> db_end: Need to collect reply

13:21:26.495 [3592.3640] <32> write_data: image write failed: error 2060022: 

13:21:27.197 [3592.3640] <2> delete_image_disk_sts: Deleting disk header for 

13:21:27.384 [3592.3640] <2> ConnectionCache::connectAndCache: Acquiring new connection for host netbackupsrv, query type 161

13:21:27.384 [3592.3640] <2> vnet_pbxConnect: pbxConnectEx Succeeded

13:21:27.384 [3592.3640] <2> logconnections: BPDBM CONNECT FROM 172.28.28.124.62103 TO 172.28.28.30.1556 fd = 1444

13:21:27.384 [3592.3640] <8> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2

13:21:27.384 [3592.3640] <2> db_end: Need to collect reply

13:21:30.957 [3592.3640] <2> ConnectionCache::connectAndCache: Acquiring new connection for host netbackupsrv, query type 1

13:21:30.957 [3592.3640] <2> vnet_pbxConnect: pbxConnectEx Succeeded

13:21:30.957 [3592.3640] <2> logconnections: BPDBM CONNECT FROM 172.28.28.124.62104 TO 172.28.28.30.1556 fd = 1444

13:21:30.957 [3592.3640] <8> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2

13:21:30.957 [3592.3640] <2> db_end: Need to collect reply

13:21:30.957 [3592.3640] <16> write_data: cannot write image to disk, Invalid argument

13:21:30.957 [3592.3640] <4> write_backup: Calling close_all_ft_pipes

13:21:30.957 [3592.3640] <2> bptm: EXITING with status 84 <----------
 
 
 
Thanks for your kind help
Discussion Filed Under:

Comments 16 CommentsJump to latest comment

revaroo's picture

Check this Technote out, it's not exact but it **may** help

http://www.symantec.com/business/support/index?pag...

edit: Actually I don't think it's relevant.

 

CRZ's picture

I suspect it is a bug, but as you're at 7.5.0.3 I'm not sure if it's a bug we know about yet.  You'll need to open a support case and have some logs ready to send your TSE (bptm and pdplugin to start).


bit.ly/76LBN | APPLBN | 75LBN

beaumont1's picture

we are facing this issue since weeks running on 7.5.0.1 . Yesterday we applied the maintenance pack 7.5.0.3 with no luck...

CRZ's picture

Understood.

Have you opened a support case?  Please see my previous post.


bit.ly/76LBN | APPLBN | 75LBN

Jupe's picture

Hi,

same problem with version 7.5.0.4 when backing up on large vmware server to MSDP. Any ideas ?

shmoolm's picture

Hello,

Is there a solution for this bug?

I have 7.5.0.4 and I have it too.

 

Thanks.

Marianne's picture

@beaumont1 has not been back since June....

Either start your own discussion or log a call with Symantec.

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

Jupe's picture

I have opened support case, it is now on level 2. Waiting for solution/workaround.

shmoolm's picture

Its happend to you too? on what servers (Virtual?) Linux, Windows?

 

Thanks.

Jupe's picture

Full backup of virtual server is working, but incremental do not. And they are Windows servers.

Thanks

shmoolm's picture

Thank you Jupe,

I have the same problem but on Linux Virtual Server.

Full backup is working fine.

If you are working with the SAN method try to change it to Network and see if its help.

Its worked for me but not anymore.

 

Thanks

 

Abesama's picture

Same here.

7.5.0.4

Windows VM backup (full, not incremental) to MSDP showing status 84 ...

Anger Management

Marianne's picture

Have you opened a Support call yet?

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

Jupe's picture

Hi, i got an eeb hotfix from support. I installed that on media server which has msdp. No status 84 after that. More backup tests are running. Looks good in this while.

Abesama's picture

Thanks Jupe, what's the EEB / Etrack ID ...?

Anger Management

Jupe's picture

Hi,

eebinstaller.2954551.1.AMD64.exe

And after installation to media server what is writing to msdp the full and incremental backups are working of vm backup of Windows 2003.