NetBackup and HP VLS 9200 with dedupe

OK - so cartridge is 25GB with logical of 46GB which i assume is representing compression.

NetBackup says it has written 46GB to it so it has become Full - which would be what the VTL reports back to NetBackup.

The Used Capacity of 436MB i also assume if the actual used capacity of the system after de-dupe - not bad!.

So that means if all of your tapes are now full that you can create some more as the dedupe rate you are getting is good enough

This is where dedupe VTLs are a real balancing act - make too many tapes and you could run out of physical storage, make not enough and you run out of tapes.

You also have to deal with the retention periods carefully to avoid filling the system up

You VTL vendor really should have given you guidance and advice on this

Hope this helps

You also have to deal with the retention periods carefully to avoid filling the system up

Ok, i have 10 politics for full backup SQL with retention period 1 month, but starting different time. And have 10 politics for log backup with start different time.

1 politic have 10 sql servers (timezone +2), 2 - 40 sql servers (timezone +4), ...., 10 - 20 sql servers (timezone +9).

All 10 politics for full backup use 1 Volume Pool.

All 10 politics for log backup use 2 Volume Pool.

In a previous report the situation as an example, in reality, the situation looks like this:

All physical capasity VLS 39,6 Tb, for sql created Library with 25 Gb physical capacity (other space need for file backup).

1. SQL Data volume pool - 900 cart * 25 Gb (deduplicated) 785 cart have status FULL or FULL MPX, 36 with status active and contains data, 79 active and empty.

2. Log volume pool - 100 cart * 25 Gb (not deduplicated, restriction HP VLS for sql log backup)

Maybe need create 10 volume pool for each full backup  politics?

You shouldnt actualy need different volume pools - if the retention of the backup is different then the jobs wont write (by default) to the same tape anyway.

The less volume pools in use the more efficient use of tape you will have.

You will need to look at the VTL GUI to get a feel for the real used capacity of the system.

Shame about the SQL Logs not de-duping - using NBU Dedupe with compression enabled they dedupe really well.

You will need to look at the VTL GUI to get a feel for the real used capacity of the system.

On VLS GUI  Library for SQL:

Allocated Capacity - 25 TB

Logical Data - 54.08 TB

Used Capacity - 6.90 TB

Available Capacity - 18.10 TB

Ratio: 7.8:1

On NetBackup Admin Console:

1. SQL Data volume pool - 900 cart * 25 Gb (deduplicated) 785 cart have status FULL or FULL MPX, 36 with status active and contains data, 79 active and empty.

2. Log volume pool - 100 cart * 25 Gb (not deduplicated, restriction HP VLS for sql log backup)

On 1 Media pool:

79 empty * 25 GB + 36 *25 Gb (active with data as empty) = 2875 Gb Free

785 FULL * 25Gb = 19625 Gb FULL

summary 22500 GB

On 2 Media Pool (for log):

19 FULL * 25 = 475 Gb

61 empty * 25 Gb + 20 with data as empty * 25 Gb = 2025 Gb

475 Gb Full and 2025 Gb FREE

summary 2500 Gb

TOTAL Media pool 1+2:

FULL 20100 Gb

FREE 4900 Gb

20100+4900=25TB

VLS see 18 Tb free, NBU see 4.9 Tb

On VLS GUI  Library for SQL: Allocated Capacity - 25 TB Logical Data - 54.08 TB

Used Capacity - 6.90 TB Available Capacity - 18.10 TB Ratio: 7.8:1