Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Can not decompress file - after update to 7.5.0.6

Created: 03 Jul 2013 | 11 comments

Hello!

i'm have this message in log after update to 7.5.0.6 

c;\program files\veritas\netbackup\db\error\log_1372881600

...

1372887172 1 2 16 backup-server 0 0 0 *NULL* bpdbm can not decompress file  - events out of sequence - image inconsistency (229)
1372887172 1 2 16 backup-server 0 0 0 *NULL* bpdbm can not decompress file  - events out of sequence - image inconsistency (229)
1372887172 1 2 16 backup-server 0 0 0 *NULL* bpdbm can not decompress file  - events out of sequence - image inconsistency (229)
1372887172 1 2 16 backup-server 0 0 0 *NULL* bpdbm can not decompress file  - events out of sequence - image inconsistency (229)
1372887172 1 2 16 backup-server 0 0 0 *NULL* bpdbm can not decompress file  - events out of sequence - image inconsistency (229)
...
 
in c;\program files\veritas\netbackup\logs\bpdbm\
...
01:32:51.578 [4688.4392] <2> image_path_r: cannot parse j
01:32:51.578 [4688.4392] <16> remove_tir_info: can not decompress file  - events out of sequence - image inconsistency (229)
01:32:51.578 [4688.4392] <2> ReadVxDBMS_ConfFile: Acquiring mutex
01:32:51.578 [4688.4392] <2> ReadVxDBMS_ConfFile: Acquiring read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
01:32:51.578 [4688.4392] <2> ReadVxDBMS_ConfFile: Acquired read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (1096)
01:32:51.578 [4688.4392] <2> ReadVxDBMS_ConfFile: unlocking on fd (1096) for C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
01:32:51.578 [4688.4392] <2> ReadVxDBMS_ConfFile: Releasing mutex
01:32:51.594 [4688.4392] <2> image_path_r: cannot parse j
01:32:51.594 [4688.4392] <2> image_path_r: cannot parse j
01:32:51.594 [4688.4392] <2> image_path_r: cannot parse j
01:32:51.594 [4688.4392] <16> remove_tir_info: can not decompress file  - events out of sequence - image inconsistency (229)
01:32:51.594 [4688.4392] <2> ReadVxDBMS_ConfFile: Acquiring mutex
01:32:51.594 [4688.4392] <2> ReadVxDBMS_ConfFile: Acquiring read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
01:32:51.594 [4688.4392] <2> ReadVxDBMS_ConfFile: Acquired read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (1052)
01:32:51.594 [4688.4392] <2> ReadVxDBMS_ConfFile: unlocking on fd (1052) for C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
01:32:51.594 [4688.4392] <2> ReadVxDBMS_ConfFile: Releasing mutex
01:32:51.609 [4688.4392] <2> image_path_r: cannot parse j
01:32:51.609 [4688.4392] <2> image_path_r: cannot parse j
01:32:51.609 [4688.4392] <2> image_path_r: cannot parse j
01:32:51.609 [4688.4392] <16> remove_tir_info: can not decompress file  - events out of sequence - image inconsistency (229)
01:32:51.609 [4688.4392] <2> ReadVxDBMS_ConfFile: Acquiring mutex
01:32:51.609 [4688.4392] <2> ReadVxDBMS_ConfFile: Acquiring read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
01:32:51.609 [4688.4392] <2> ReadVxDBMS_ConfFile: Acquired read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (1048)
...

Can you help me?

Operating Systems:

Comments 11 CommentsJump to latest comment

Marianne's picture

Probably best to log a support call with Symantec ASAP.

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

Dyneshia's picture

The Error can be observed if you have compresses data backup for any of the client.
While image cleanup is running its not able to decompress the file and cleanup the images which should be cleaned.

Please run thecommand to decompress the files:
<install_path>\NetBackup\bin> bpimage -decompress -allclients

After this please run:
<install_path>\NetBackup\bin> bpimage -cleanup
 

dgwhitt's picture

@Dyneshia - is this a 7506 bug?  image cleanups and decompress client images can happen at anytime, are you saying they cant run (clash) at the same time?

I wouldnt run "bpimage -decompress -allclients" unless I knew I had plenty of space

Dyneshia's picture

Please clairfy, you are just seeing the error in the error log ?  Are any of your backups failing ?

Does bpimage -cleanup complete with status 0 ?

sstepanenko's picture

in debug log logs\bpdbm

...

08:32:52.034 [576.5912] <2> ss_db: query return value = 227(no entity was found)
08:32:52.034 [576.5912] <2> process_request: request complete: exit status 227 no entity was found; query type: 274
...
 
In Console - Report - Problems:
...
bpdbm can not decompress file  - events out of sequence - image inconsistency (229)
bpdbm can not decompress file  - events out of sequence - image inconsistency (229)
....
 
PS C:\Program Files\Veritas\NetBackup\bin> .\bpdbm -consistency
Checking NetBackup database consistency
NetBackup 7.5 2013061020
 
 
check images for clients
________________________________________________
checking image file <FreeBSD_1372224123_FULL>
checking files file <FreeBSD_1372224123_FULL.f>
<C:\Program Files\Veritas\NetBackup\db\images\cli1\1372000000\FreeBSD_1372224123_FULL.f> does not exist
checking image file <Windows-WS_1372237200_INCR>
checking files file <Windows-WS_1372237200_INCR.f>
<C:\Program Files\Veritas\NetBackup\db\images\cli2\1372000000\Windows-WS_1372237200_INCR.f> does not exist
checking image file <Windows-Standart-WS_1373000845_INCR>
checking image file <Windows-Standart-WS_1373000847_INCR>
checking image file <FreeBSD_1372248000_INCR>
checking files file <FreeBSD_1372248000_INCR.f>
<C:\Program Files\Veritas\NetBackup\db\images\cli3\1372000000\FreeBSD_1372248000_INCR.f> does not exist
checking image file <Windows-Standart-WS_1373000879_INCR>
checking files file <Windows-Standart-WS_1373000879_INCR.f>

cli1,cli2,cli3 - old clients, I was trying import old tape with images this old clients.

Ed3's picture

I had a similar problem. Contacted Symantec support. It took some time, but they provided an EEB. See TECH209826 .

Stumpr2's picture

Don't mess around with your catalog. Open a support call with symantec. You need to have one open to get an EEB.

VERITAS ain't it the truth?

CRZ's picture

FYI, TECH209826 now comes with a downloadable hotfix so you don't have to open a case and request an EEB:

In NetBackup 7.5.0.6, TIR (True Image Restoration) catalog data pruning fails, leading to unexpected growth in the size of catalog.
 http://symantec.com/docs/TECH209826

...although I hope our original poster got the EEB back a lot closer to when he started this thread!


bit.ly/76LBN | APPLBN | 761LBN

Stumpr2's picture

LOL I just noticed the timestamp.

VERITAS ain't it the truth?