Comprehensive data protection for all workloads
Post Reply
smurugun
Veeam ProPartner
Posts: 6
Liked: never
Joined: May 08, 2015 2:48 pm
Full Name: Murugan S
Contact:

DataDomain As a Primary and GFS Storage

Post by smurugun » May 07, 2016 11:45 pm

Hi,

Please find my below architecture and give me the advise for the recommended configuration.

1. Vshpere 6.0 with 2 VMs having 1 TB Data Each
2. Veeam B & R 9.0 U1
3. DataDomain 2200 with DD boost (there is no additional repository)
4. Primary storage DataDomain - Cifs, Secondary storage Datadomain - DDboost( for GFS retention )
5. Backup Policy,
Backup job - Forwarder Incremental - 7 restore points
Weekly - Thursday synthetic full
Monthly - Active full

Backup copy - Restore points 7
Weekly - 5
Monthly - 12
Yearly - 1

- Backup job is going fine with CIFS @ 260 Mb/S, but backup copy jobs are running very slow like 26 Mb/S

how to improve the Backup copy job speed. Please advise,

Thanks in advance.
Thanks,
Murugan. S

Gostev
SVP, Product Management
Posts: 24656
Liked: 3471 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: DataDomain As a Primary and GFS Storage

Post by Gostev » May 08, 2016 8:52 pm

Hi, depends on the bottleneck statistics for backup copy job - basically you need to improve the weakest element it shows. Thanks!

Shestakov
Veeam Software
Posts: 6916
Liked: 700 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: DataDomain As a Primary and GFS Storage

Post by Shestakov » May 09, 2016 2:11 pm

Besides bottleneck statistics, what is the WAN link bandwidth the sites? Do you leverage WAN acceleration?
Thanks!

jeremy.porter
Service Provider
Posts: 5
Liked: 1 time
Joined: Oct 17, 2012 11:38 am
Full Name: Jeremy Porter
Contact:

Re: DataDomain As a Primary and GFS Storage

Post by jeremy.porter » Jul 23, 2016 6:54 am

Hi Smurugun,
I have came across this too, and seen it a few times.
A flaw that you will find when doing a Backup Copy Job back to the same DataDomain for GFS is that it is NOT DDBoost'ed.
In fact is completely the opposite and the performance sucks, I'm guessing as it has to both read/re-hydrate and de-duplicate/write the data within itself at the same time as it is transferred from the primary repository to GFS copy.
We were hoping this would of been fixed when v9 came out, but wasn't maybe v9.5 or v10?
To get around this just ended up having three separate backup jobs for each of the retentions (daily-weekly / end of Month / end of Year) as running an Active Full which DOES use DDBoost takes only moments compared to many weeks that multi Terabyte Backup Copy takes dribbling along at around 10 to 20Mb/S.

veremin
Product Manager
Posts: 16789
Liked: 1410 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: DataDomain As a Primary and GFS Storage

Post by veremin » Jul 25, 2016 10:28 am

A flaw that you will find when doing a Backup Copy Job back to the same DataDomain for GFS is that it is NOT DDBoost'ed.
Just to clarify - the same device is added twice to a backup console? As a repository for backup job and as a repository for backup copy job? Thanks.

smurugun
Veeam ProPartner
Posts: 6
Liked: never
Joined: May 08, 2015 2:48 pm
Full Name: Murugan S
Contact:

Re: DataDomain As a Primary and GFS Storage

Post by smurugun » Aug 14, 2016 11:47 am

YES. the same device added twice.

because we don't have a storage space other than the Datadomain. with datadomain we need to store the data with GFS policy. we dont have any offsite storage or Tape loader.

Please let me know if there is any other way to have backup data with GFS on Data Domain as above explained my architechture.

FYI,

Backup Policy,
Backup job - Forwarder Incremental - 7 restore points
Weekly - Thursday synthetic full
Monthly - Active full

Backup copy - Restore points 7
Weekly - 5 Full Copies
Monthly - 12 Full Copies
Yearly - 1 Full Copy

Thanks.
Thanks,
Murugan. S

Gostev
SVP, Product Management
Posts: 24656
Liked: 3471 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: DataDomain As a Primary and GFS Storage

Post by Gostev » Aug 14, 2016 6:28 pm 1 person likes this post

I don't see any other way if you literally don't have any other storage.

However, you have very little data to protect as far as total size, so really you should very easily be able to "do it right" instead of storing all your backups on the same storage device, which is a huge risk. I would recommend following our reference architecture and creating a primary backup repository by adding a couple of large hard drives to any server in your environment. Then you would have primary backup job backing up to this repository with a very short retention policy, and then perform a backup copy to Data Domain. This way, you will have 2 copies of your backups on different devices.

Thanks!

Post Reply

Who is online

Users browsing this forum: argolafshan and 22 guests