Forum Discussion

unkn0wnn's avatar
unkn0wnn
Level 4
2 years ago

High disk space usage - tried manual reclaim

Hi,

Disk space usage is high on my PureDisk media server, I've checked and on disk I currently should have less than 1TB of data used for Copy 1 however after doing manual reclaim (processqueue + garbage collection then processqueue twice), only reclaimed about 500MB.

On disk I only store copy 1 and oldest backup is from last week (Catalog GUI).

Also spotted a lot of old files back to 2014 in /storage/data directory even a tough all copy 2 are on tapes:

-rw-r----- 1 root root 256M Jan 15 2014 6239.bin
-rw-r----- 1 root root 256M Jan 15 2014 6238.bin
-rw-r----- 1 root root 256M Jan 15 2014 6237.bin
-rw-r----- 1 root root 256M Jan 15 2014 6236.bin
-rw-r----- 1 root root 256M Jan 15 2014 6235.bin
-rw-r----- 1 root root 1.3M Jan 15 2014 6225.bhd
-rw-r----- 1 root root 256M Jan 15 2014 6225.bin
-rw-r----- 1 root root 694K Jan 15 2014 6224.bhd
-rw-r----- 1 root root 558K Jan 15 2014 6223.bhd
-rw-r----- 1 root root 828K Jan 15 2014 6222.bhd
-rw-r----- 1 root root 717K Jan 15 2014 6221.bhd
-rw-r----- 1 root root 256M Jan 15 2014 6224.bin
-rw-r----- 1 root root 256M Jan 15 2014 6223.bin
-rw-r----- 1 root root 256M Jan 15 2014 6222.bin
-rw-r----- 1 root root 256M Jan 15 2014 6221.bin
-rw-r----- 1 root root 867K Jan 15 2014 6209.bhd
-rw-r----- 1 root root 256M Jan 15 2014 6209.bin
-rw-r----- 1 root root 571K Jan 15 2014 6199.bhd
-rw-r----- 1 root root 256M Jan 15 2014 6199.bin
-rw-r----- 1 root root 410K Jan 15 2014 6198.bhd
-rw-r----- 1 root root 256M Jan 15 2014 6198.bin
-rw-r----- 1 root root 362K Jan 15 2014 6197.bhd
-rw-r----- 1 root root 256M Jan 15 2014 6197.bin
-rw-r----- 1 root root 256M Jan 3 2014 1596.bin
-rw-r----- 1 root root 256M Jan 3 2014 745.bin
-rw-r----- 1 root root 637K Sep 29 2013 3997.bhd
-rw-r----- 1 root root 16M Sep 29 2013 3997.bin

n5220w:/disk/data # du -h
8.0K ./749/0/_0
8.0K ./749/0
8.0K ./749
1003M ./journal
3.1T .

Below output /usr/openv/pdde/pdcr/bin/crcontrol --dsstat:

************ Data Store statistics ************
Data storage Raw Size Used Avail Use%
4.5T 4.4T 3.3T 1.0T 76%

Number of containers : 18600
Average container size : 177409748 bytes (169.19MB)
Space allocated for containers : 3299821316678 bytes (3.00TB)
Space used within containers : 3205753046031 bytes (2.92TB)
Space available within containers: 94068270647 bytes (87.61GB)
Space needs compaction : 11411996203 bytes (10.63GB)
Reserved space : 199918100480 bytes (186.19GB)
Reserved space percentage : 4.0%
Records marked for compaction : 309850
Active records : 43121730
Total records : 43431580

What is possibly wrong? I'm concerned it could be due to some orphaned images, Can anyone please advise ?

12.x and Earlier
Linux

16 Replies

Sort By
  • Michal_Mikulik1's avatar
    Michal_Mikulik1
    Moderator
    2 years ago

    Hello,

    this topic has been discussed more times here on the forum. When you are in a deduplication environment, you cannot apply practice based on a non-deduplication env experience.


    A few related points to mention here:
    - when your backups are deduplicated well for a certain client/DB, you will see space release only after you move/expire ALL its backup images, not only SOME of even MOST images
    - you will see space release after moving/expiring of some individual images only in the case that the client/DB deduplicates wrong
    - data/blocks from 2014 can remain in the system up to 2023 when it has been continuously founded as a dedup baseline for any other backups

    Regards

    M.

    • unkn0wnn's avatar
      unkn0wnn
      Level 4
      2 years ago

      Thanks Michal, once a week I have 1 DB server like 3TB scanned and deduplication rate is like 75-80% (sent around 600MB).

      I understand that you are suggesting there are dependant fragments in the DB and filesystem.

      Apart from extending what's the best action to take next?

      • davidmoline's avatar
        davidmoline
        Level 6
        2 years ago

        Hi 

        I would suggest logging a case with support to check for orphaned images. They will provide a utility to perform a scan on the MSDP pool (and additionally collect data from the master server). From that they will look to identify backup images in the MSDP pool that no longer exist in the NetBackup catalog. These can then be deleted (which is done with a script and data file provided by support). 

        The first phase is called PoGather - this will need to be run on your system. 

        David