Oldest backup image & size information on a diskpool

Master server - Linux

Diskpool - PureDisk

Appliance - 5330

Hello All, recently I am getting bunch of exit status 129. Diskpool free space currently showing me 10TB free out of 128TB total. I am convince something is not right somewhere. Either some expire images are not completely been removed or something is just amise. So as a start to isolate issue, I am searching for a command, or opscenter query to list following from the affected diskpool :

List of all images, their respective sizes, and retention/expiration period or time. Thank you

Linux

RamNagalla
7 years ago
Do you see any failuers or partial successfull for the image clean up jobs? if yes fixing the image cleanup jobs is the right place to start to make sure netbackup is properly expiring the images.

bpimmedia command can help you to list the all images in the specific disk pool or from GUI--> reports -> Disk report -> images or Disk will list all the images on disk ( it will pull the infomration form the netbackup catalog)

if you see the images that are not suppose to be there then its issue with in the netbackup.

once you make sure there is no issue in netbackup side, get into the MSDP server and make sure processqueue is properly running , you can also check the queuesize using the command crcontrol -queueinfo to verify the last processed queue.

if you see no issues in MSDP cleaning , the next step will be comparing the images listing in netbackup catalog with the Images in MSDP( veritas support has the script to do this comparassion)

RamNagalla
Moderator
7 years ago
Do you see any failuers or partial successfull for the image clean up jobs? if yes fixing the image cleanup jobs is the right place to start to make sure netbackup is properly expiring the images.

bpimmedia command can help you to list the all images in the specific disk pool or from GUI--> reports -> Disk report -> images or Disk will list all the images on disk ( it will pull the infomration form the netbackup catalog)

if you see the images that are not suppose to be there then its issue with in the netbackup.

once you make sure there is no issue in netbackup side, get into the MSDP server and make sure processqueue is properly running , you can also check the queuesize using the command crcontrol -queueinfo to verify the last processed queue.

if you see no issues in MSDP cleaning , the next step will be comparing the images listing in netbackup catalog with the Images in MSDP( veritas support has the script to do this comparassion)
- Marianne
  Level 6
  7 years ago
  You can run bpimmedia against the disk pool :
  
  bpimmedia -stype PureDisk -dp <disk-pool-name> -d 01/01/1970
  
  You may want to add an end-date (-e mm/dd/yyyy) as well to exclude recent images.
  
  Curious to know what is the HWM on the disk pool set to?
  You will see status 129 when HWM is reached, even though there is seemingly lots of space left.
  - Amol_Nair
    Level 6
    7 years ago
    As Marianne mentioned, 10 TB may seem pretty large for you but if you say 10 TB is free out of 128 TB it makes it around 8% free space only.. If you High waterMark is set at 80 or 90 % den jobs would definitely report failure as the storage has already exceeded that point..
- Dollypee
  Moderator
  7 years ago
  Thank you all for your response. RamNagalla response sorted out my concern. Thanks again
Nicolai
Moderator
7 years ago
Netbackup tries to pre-allocate disk space, if the size of the jobs exceed high watermark for the disk storage unit, you will get status code 129.

You can disable the the function by setting the high water mark to 100% - but you should really consider the consequences before doing so.

Forum Discussion

Oldest backup image & size information on a diskpool

Related Content