Netbackup 7 - Incorrect disk pool available space

You could try to do an inventory of the disk pool. This is available in the Disk Pools view in the Admin Console, right-click on the disk pool and select Inventory... Maybe it will work.

You could also run nbdevquery -listdp -stype PureDisk -U and see what it says. Also, replace -listdp with -listdv and you get the status of the volume.

AFAIK, no current OST device works with multiple volumes. For PDDE, you would rather have to extend the file system using either Windows disk manager or use Storage Foundation 5.1 and then create a concat device, and grow the file system.

/A

Hello,

Thanks for the quick reply! I had already tried the inventory but it only seem to recalculate usable/raw sizes. Doing the inventory didn't have any impact.

The listdp returned only global info about usable/raw sizes which are correct (1023gb). The listdv command returned the following:

Disk Pool Name      : LabDiskPool
Disk Type           : PureDisk
Disk Volume Name    : PureDiskVolume
Disk Media ID       : @aaaab
Total Capacity (GB) : 1024.00
Free Space (GB)     : 18.32
Use%                : 98
Status              : UP
Flag                : ReadOnWrite
Flag                : AdminUp
Flag                : InternalUp
Num Read Mounts     : 0
Num Write Mounts    : 1
Cur Read Streams    : 0
Cur Write Streams   : 0

As you can see, that command still reports 18gb of free space while Windows report 120gb available. If you have any other idea, let me know!

Thanks! :-)

 I just wanted to share this command with you.  This command provide stat of the configured PDDE.

# /usr/openv/pdde/pdcr/bin/crcontrol --dsstat 1

************ Data Store statistics ************
Data storage       Size   Used  Avail Use%
             590.0G 463.9G 126.1G  79%
Number of containers             : 121
Average container size           : 247650044 bytes (236.18MB)
Space allocated for containers   : 29965655409 bytes (27.91GB)
Space used within containers     : 28524718837 bytes (26.57GB)
Space available within containers: 1440936572 bytes (1.34GB)
Space needs compaction           : 75511082 bytes (72.01MB)
Records marked for compaction    : 1049
Active records                   : 242823
Total records                    : 243872

In addition, you could try to manually run the PDDE maintenance processing;

install_path\Veritas\pdde\Crcontrol.exe --processqueue
install_path\Veritas\pdde\pdcr/bin/crcollect -v -m +1,+2 --noreport

And to watch the result, use the command Nicolai recommended.

Also, If you change the available space outside the control of NBU/PDDE, such as deleting unrelated files also stored on the volume, you have to restart NBU processes in order for it to discovered the new space.

/A

Hello,

Thanks again for the replies! Here is the output of crcontrol --dsstat 1:

************ Data Store statistics ************
Data storage       Size   Used  Avail Use%
                 1024.0G 669.0G 355.0G  66%
Number of containers             : 3590
Average container size           : 268435456 bytes (256.00MB)
Space allocated for containers   : 963683287040 bytes (897.50GB)
Space used within containers     : 712623327356 bytes (663.68GB)
Space available within containers: 251059959684 bytes (233.82GB)
Space needs compaction           : 974237482 bytes (929.11MB)
Records marked for compaction    : 11871
Active records                   : 7032121
Total records                    : 7043992

I'm not quite sure what this is supposed to show. My disk pool is indeed 1TB but has 120gb of free space while it is reporting 355gb here.

I also ran the other 2 commands. Crcontrol.exe --processqueue only outputs "OK" and returns to the prompt. I waited a couple minutes to be sure it would have time to process the queue and then ran crcollect -v -m +1,+2 --noreport which gave me this result:

modes         : +1,+2
report        : disabled
storagepool id: 39
start         : Tue Jul 27 07:22:16 2010
.. 10000 records processed
.. 20000 records processed
.. 30000 records processed
...
.. 7030000 records processed
.. 7032121 records processed
finish        : Tue Jul 27 07:23:50 2010
duration      : 0d:0h:1m:34s

Coming to think about it, it could be the "built-in" 10% threshold in PDDE/PD. Thus, it always report 10% less available in the disk pool, than is available, and 1TB would be ~100GB, so your 18GB sounds right.

In PureDisk, this is possible to set using the webGUI, but I remember having seen it in a configuration file in the PDDE directory structure, but as I don't have a PDDE at hand, I cannot verify.

/A

If you're talking about the disk volume's high water mark, it is set to 98% right now. When I look at the disk pools section in the console, it says the pool is 98.17% full (which is exactly the free space it is reporting: 18.67gb / 1023.99gb). At this point, even catalog backups (which are just a couple hundred mb since this is just a lab environment) are failing because it thinks it doesn't have enough space.

I'll keep searching on my side. If I find something, I'll let you know.

Thanks!

No, it is not the NBU highwater mark, but an internal threshold in PDDE/PD. So in effect you have 12% you cannot use, so ~120GB in your case.
In PureDisk it is configurable in the GUI and is called Lowspace Threshold in the Content Router->Spooler section.

Look at another thread in the PureDisk forum called "PDDO diskpool space free discrepancy", and you will probably have the procedure how to increase the available space, but again, you should rather extend your storage to solve the problem...

/A

I've tried what was described in the forum post you mentioned but it didn't work. When I look at the backups in the catalog, there is only 3 backups left. All others expired (remember this is just a test environment and I hadn't done any new testing for the last 2 weeks which was my retention). Yet, the console is still only reporting 18gb. I've manually expired the last 3 backups and rebooted the whole server just to be sure all services would be restarted but still 18gb with 120gb left.

I'm going to try a backup and see if it overwrites the old expired data (which it should) and then maybe it will update its available space. Otherwise, is there a command that can be used to tell Netbackup to delete all expired data from disk?