08-21-2013 07:55 AM
Hi
I know it's good practice to locate the Dedupe database onto a different volume for performance reasons and so I've done that - all fine :o)
And I think (even though I can't recall where I read it) that, despite relocating the database, NetBackup will still reserve 4% space within the dedupe pool for the database (even though it resides elsewhere).
My question is - did I imagine reading the bit about the space reservation even if the database resides elsehwere? and if I didn't imagine it, can that reserved space be reclaimed and made part of the dedupe pool?
many thanks in advance.....
KL
Solved! Go to Solution.
08-21-2013 08:20 AM
from the Dedup Guide
About deduplication storage capacity
The maximum deduplication storage capacity is 64 TBs. NetBackup reserves 4
percent of the storage space for the deduplication database and transaction logs.
Therefore, a storage full condition is triggered at a 96 percent threshold.
For performance optimization, Symantec recommends that you use a separate
disk, volume, partition, or spindle for the deduplication database. If you use
separate storage for the deduplication database, NetBackup still uses the 96 percent
threshold to protect the data storage from any possible overload.
08-21-2013 08:20 AM
from the Dedup Guide
About deduplication storage capacity
The maximum deduplication storage capacity is 64 TBs. NetBackup reserves 4
percent of the storage space for the deduplication database and transaction logs.
Therefore, a storage full condition is triggered at a 96 percent threshold.
For performance optimization, Symantec recommends that you use a separate
disk, volume, partition, or spindle for the deduplication database. If you use
separate storage for the deduplication database, NetBackup still uses the 96 percent
threshold to protect the data storage from any possible overload.
08-21-2013 08:50 AM
Many thanks - so I'm not going mad.... :o)
But it looks like the space can't be reclaimed as it's there to protect against corruption
Thanks again