netbackup 129 error & storage unit's high water mark

[thesunlover]

Hi,

I've got lots of 129 errors recently for many policies. I've checked the Storage Unit and found the 'High water mark' is set to 10% and the 'Low water mark' is set to 5%. Is this 10% 'High water mark' the problem cause? The default should be 98%, right?

Please advise! Thank you in advance!

[Will_Restore]

The High water mark setting (default 98%) is a threshold that triggers the

following actions:

■ When an individual disk volume of the underlying storage reaches the High

water mark, NetBackup considers the volume full. NetBackup chooses a

different volume in the underlying storage to write backup images to.

■ When all volumes in the underlying storage reach the High water mark, the

BasicDisk storage is considered full. NetBackup fails any backup jobs that are

assigned to a storage unit in which the underlying storage is full. NetBackup

also does not assign new jobs to a BasicDisk storage unit in which the

underlying storage is full.

■ NetBackup begins image cleanup when a volume reaches the Highwatermark;

image cleanup expires the images that are no longer valid. NetBackup again

assigns jobs to the storage unit when image cleanup reduces any disk volume's

capacity to less than the High water mark.

If the storage unit is in a capacity-managed storage lifecycle policy, other

factors affect image cleanup.

[Mark_Solutions]

Depending on you NVIDIA version and whether it is basic or advanced disk the HWM may not matter and it runs until full - the next backup to run will estimate the space needed based on previous backups If it is a staging area make sure duplications are up to date but if just disk then see if there is any space on the drive as it may actually be full so you need to.clear some.space down manually Either way 95% and 80% would be better figures to use Hope this helps

[Marianne · Accepted solution]

bperror -S 129 -r
Disk storage unit is full

Do you have Disk Staging to tape or other storage in place?

Those Water Marks look like sabotage!!! No wonder you are seeing status 129.

Confirm in STU config that staging is configured. Verify that schedules for staging is running as per configuration and they are going through succesfully.

[thesunlover]

Will do and keep you posted. Thanks a lot!