Netbackup-compression of backup on tape (h/w level)

[paroksha]

hello all

We regularly take backup for SAP systems, recently i faced some abnormal behaviour..

The policies configured 1 year ago are able to compress backup h/w level(tape drive level), but when i configure new policy with all parameters same... it is not able to compress

old policies can write 1.5 Tb data on single tape (IBM LTO 4 tape 800/1600Gb) , new policy is barely able to write 800Gb.

what is wrong with me ... even if i copy old policy to create new ..it wont compress.

what is the issue and the solution if any one have solved this issue....

on old policies software level compression is not enabled and still it compesses perfectly but new r not..???

Please Help!!!!!

[paroksha]

[Mark_Solutions]

I still cannot see the column titled "Media Status" in that screen shot.

Right click the top row and select Columns - Layout

Select Media Status and set it to "show" then move it up so that it is next to the Kilobytes column and screen shot it again

Thanks

[paroksha]

backup1_development-->  full

[Mark_Solutions]

Sorry - that picture is so shrunk i cannot make out the figures

I see that there are 4 tape shown as Full - what are the kb figures for those?

[paroksha]

[Mark_Solutions]

OK - so the full tapes range from 1.1TB down to 850GB - so not great.

As this is simply a difference between identical policies then that is where you need to look as we have said before

the nbpemreq --updatepolicies just make NBU re-read then all to make sure they and all settings are up to date - so no worries running this any time.

I would still be inclined to start from scratch with a new policy and try that one though.

I am curious though - why do you have 2 identical policies anyway?

[paroksha]

hi 

i dont want identical policies, rather i want compression of data.

i want my all policies should compress data upto 1.5/1.6 Tb on single tape(H/W level), my old policies are able to do that but new policies are not able to compress even tapes are similar , data is similar ...

[Will_Restore]

noticed the "non-working" policy contains

COLLECT_TIR_INFO 2

COLLECT_BMR_INFO 1

where the "working" policy has

COLLECT_TIR_INFO 0

COLLECT_BMR_INFO 0

[paroksha]

the other working policies has thos settings 

************************************************************

root@BackupServer # more info

CLIENT_TYPE 0

FOLLOW_NFS_MOUNTS 0

CROSS_MOUNT_POINTS 0

CLIENT_COMPRESS 0

PRIORITY 1

CLIENT_ENCRYPT 0

DISASTER_RECOVERY 0

MAX_JOBS_PER_CLASS 2147483647

MAX_FRAG_SIZE 0

ACTIVE 0

EFFECTIVE_TIME 1291721400

COLLECT_TIR_INFO 2

EXTENDED_SECURITY_INFO 0

IND_FILE_RESTORE_FROM_RAW 0

BLOCK_INCREMENTAL 0

STREAMING 0

FROZEN_IMAGE 0

BACKUP_COPY 0

NUMBER_OF_COPIES 1

FAIL_ON_ERROR 0

CHECKPOINT 0

CHKPT_INTERVAL 0

ENABLE_PFI 0

OFFHOST_BACKUP 0

USE_ALT_CLIENT 0

USE_DATA_MOVER 0

DATA_MOVER_TYPE 2

COLLECT_BMR_INFO 1

RES_IS_SS 0

GRANULAR_RESTORE_INFO 0

JOB_SUBTYPE 0

USE_VIRTUAL_MACHINE 0

GENERATION 47

CLASS_ID 00B713261DD211B2BB4900144F8CBB44

RESIDENCE BackupServer-hcart-robot-tld-0 *NULL* *NULL* *NULL* *NULL* *NULL*

 *NULL* *NULL* *NULL* *NULL*

POOL backup_STG_tuesday NetBackup NetBackup NetBackup NetBackup NetBackup N

etBackup NetBackup NetBackup NetBackup

SHARE_GROUP *ANY*

DATA_CLASS *NULL*

#VMD5_DIGEST=a8 22 ce a8 ba 74 5b 75 aa ac bf db dd d7 07 e5

root@BackupServer # pwd

/usr/openv/netbackup/db/class/tuesday

root@BackupServer #

************************************************************

please see the media it is still in active state and finished writing 1.2 Tb

backup_STG_tuesday is working working same as monday..

my original question is how older policies are able to write 1.5Tb and not new created..

now pl ans following :

1.. does NFS mount point makes any difference

2.. does netbackup anyhow can control drive level compression: (as same drive is been used and compressing properly) 

3... nbpemreq --updatepolicies command will make any changes in older policies, these are PROD backup policies.. other i m trying are DEV and Quality .

[Mark_Solutions]

You say your old policies and you new policies - this is what is confusing me here ...

Why, if you have working old policies are you creating new ones ....

You say they are identical but if you are making new policies it suggests that you are backing up different clients or different data - so this is where the differences may come from .....

We need to know what a "good" policy backs up - client name, O/S, backup and data type and then the same for the "bad" policy.

I hope you see my point .... if you have a working policy then why do you need to make a new one? ... i suspect that the new one is a different client / data location and so that is where you should be looking for data difference

[paroksha]

Hmm I Know what you want to know....

see my old policies are backing up PROD SAP data..

i created new policies to backup development & quality servers SAP data..

the data type is same and yes the clients are different offcourse......

other things are same like OS ... type etc all are SOlaris OS .

[Mark_Solutions]

If that is the case then you need to look at the SAP data on the dev servers - i think the script used was mentioned earlier as well - the cause will be on the client, not the policy