Comprehensive data protection for all workloads
Post Reply
Incred
Lurker
Posts: 2
Liked: never
Joined: Feb 05, 2024 5:21 am
Full Name: Henry McLaughlin
Contact:

Replacing a Datto

Post by Incred »

New to VBR and looking to replace a Datto device with VBR.

We have a site with limited upload bandwidth.

I would like to setup VBR to achieve the same as the Datto being.
1) Hourly backups to local performance storage with 30 day retention (not sure if this should be a 30 day chain)
2) Daily backups to offsite capacity storage with 365 day retention using GFS

I was originally thinking of using a "scale out repository" however I think to achieve this I will need to create two separate backup jobs.

I would appreciate any feedback/suggestions on how best to achieve this goal.
Mildur
Product Manager
Posts: 8785
Liked: 2313 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Replacing a Datto

Post by Mildur »

Hello Henry

Two jobs will always be required:
1.) hourly Backup Job to local storage
2.) daily Backup Copy job, type periodic (it will grab the latest restore point and copy it to the second storage)

Enable regular synthetic fulls (daily or weekly) for the backup job. Or you will have really long backup chains. With an ReFS or XFS backup repository, synthetic fulls are spaceless (FastClone technology).

I recommend to rethink which machines require hourly backups. Maybe not all workloads would require it.

You can also use transaction log backups for MSSQL or Oracle within a backup job. No need to run image level backups every hour when you have the opportunity to just grab the transaction logs. A restore will allow you to do a point in time recovery of those applications.

Best,
Fabian
Product Management Analyst @ Veeam Software
Incred
Lurker
Posts: 2
Liked: never
Joined: Feb 05, 2024 5:21 am
Full Name: Henry McLaughlin
Contact:

Re: Replacing a Datto

Post by Incred »

Hi Fabian,

Thanks for the reply. I have checked the Datto backups and see they:
1) 0 - 7 days (Hourly backups stored locally)
2) 8 - 30 days (Daily backups stored locally)

3) 0 - 14 days (daily backups stored offsite)
4) 14 - 90 days (weekly backups stored offsite)
5) 90 - 365 days (monthly backups stored offsite)

How can I implement this using VEEAM?
Gostev
Chief Product Officer
Posts: 31590
Liked: 6731 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Replacing a Datto

Post by Gostev »

Veeam uses different principles that do not necessarily map directly to what some other vendors are doing, or at least not directly. For example, we don't have "variable RPO" capability (hourly backup frequency changing to daily) as it's not the requirement most businesses have, instead usually there's always a well-defined RPO that is constant and depends only on the workload tier/importance. However, as it comes to retention policies we do support Weekly/Monthly/Yearly backups aka GFS retention, each with their own retention, as this is likewise a common requirement most businesses have. And this functionality maps to what you're trying to achieve pretty closely.

So I suggest you contact your Veeam sales rep and ask for an intro session on our product capabilities with one of the pre-sales engineers or architects. Some may even have prior experience with Datto in particular. And for help with actual implementation, you may contact any Veeam Accredited Service Partner. Please appreciate that we're with development and thus won't be able to guide you through the implementation, especially over forum posts. We are happy to explain how some feature works if User Guide is not clear enough, but we have no product implementation specialists on staff, they are a part of our Sales org.
Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 73 guests