v7 Backup Copy Deduplication Data

[barrywells]

Hi Everyone,

We are looking at upgrading to v7 shortly and would like to offer more services for customers in regards to retention period with the Backup Copy looking perfect for the task.

We need to purchase some additional hardware for a "backup" repository at each site and am trying to spec up the required storage.

We currently have 22 Jobs setup (due to ease of management with multiple customers) 90% of which are 2008r2 boxes with 7 restore points using around 2.7TB of Storage on our primary repository.

I would like to understand the efficiency the dedupe of the backup copy. If anyone has installed in what sort of saving have you seen with Dedupe across multiple jobs?

We would be looking to implement a standard GFS system on the majority of existing tasks to our new (not yet purchased) storage, 7 dailies 4 weeklies 12 Monthlys possibly yearlies what sort of impact will this have on the storage will it be deduped against all the other restore points in the backup copy job? We don't want to be in a position to have to be purchasing more storage hardware a year down the line.

Alternatively would Tape achieve a similar result with a low initial and ongoing cost?

Many Thanks!

Barry

[foggy]

I would like to understand the efficiency the dedupe of the backup copy. If anyone has installed in what sort of saving have you seen with Dedupe across multiple jobs?

Barry, actually there is no deduplication across different jobs (either for the backup copy job or for normal backup job). You are probably confused by the traffic deduplication performed by WAN accelerators if backup copy is performed with acceleration enabled, however this is another story.

[chrisdearden]

That said if you used a single backup copy job to consolidate multiple customers jobs you would get better dedupe in that job. however if you are looking at GFS retention I would highly recommend de-duplicating storage ( eg windows 2012 / hardware dedupe boxes )

[barrywells]

Hi Guys thanks for your response.

The idea would be to have an additional service for long term retention of restore points.

So we would have a single job with multiple customer jobs contained within. Would the expected Dedupe between these tasks be comparable to a normal backup job with 10 x2008r2 boxes (with a mixture of exchange/sql etc)?

Based on your response are the Sealed retention points (1st Month etc) not used for deduplication and would consume the same size as the initial full backup (with the compression/deduplication)? If thats the case we will definitely look at 2012s dedupe functionality.

Thanks Again.

Barry

[foggy]

So we would have a single job with multiple customer jobs contained within. Would the expected Dedupe between these tasks be comparable to a normal backup job with 10 x2008r2 boxes (with a mixture of exchange/sql etc)?

In terms of space required on the target storage, I would say it should be the same.

Based on your response are the Sealed retention points (1st Month etc) not used for deduplication and would consume the same size as the initial full backup (with the compression/deduplication)?

Yes, since there is no deduplication between different fulls in GFS scheme.