VEEAM - Best Practise

[Simcfc73]

Morning,

 

I'm trialling VEEAM after finding my DPM was getting unreliable and annoying. The terminology is different obviously and its taking a bit of working out as its alot different from DPM.

 

I used to have 14 days restore then a monthly saved for 6 months on tapes (firestreamer).

 

I'd be interested to know how others have set theirs up. I've connected it to a blob Azure storage centre too but not sure what I am going to store in there... my DPM database backup used to be stored in Azure. Does anyone save Exchange365 emails in VEEAM?

 

Any guidance/tips would be a great help.

[CHiLL]

We've been using VEEAM fora few years now and here is our basic setup:

• Each server has it's own job (instead of grouping together) and jobs are all scheduled to start at 10pm daily, with the jobs limited to 4 concurrent jobs
  
• VEEAM backs up production data to local SAN using the forward incremental method with a 30 day retention. (Other job settings include things like vmware quiescencing, change block tracking, application-aware processing, guest file system indexing, etc)
  
• The jobs are also set to create weekly synthetic backup files (these are load spread across the week to help load on the backup device - synethic jobs create new full backup files based on merging previous incremental backups together - the load is entirely on the storage device, not the server/network)
  
• Three more jobs also configured; End of Term 1 - 24th December each year, End of Term 2 - 2nd Sunday of April each year and End of Year - 31st July each year. These are for long term data retention and the EoY files can be copied off to other media or cloud for archiving
  
• A backup copy job is configured for each job with the target as another NAS in a different building (as a fire safety precaution)
  
• We use RClone monthly to copy off the synthetic backup file to our cloud repository
  
• Backup jobs are encrypted within the job settings
  

We do not currently backup Office 365, which with VEEAM, requires a separate license and application if I recall correctly.

 

I don't know how that stacks up with other configurations, but it's served us well over the years.

Edited November 19, 2019 by CHiLL

[flyinghaggis]

• We use RClone monthly to copy off the synthetic backup file to our cloud repository
  

 

Thanks for the info. It's helpful to know what others are doing!

 

What Cloud Repository are you using by the way as we've been comparing Veeam Cloud Connect to other generic cloud storage space?

[Simcfc73]

We've been using VEEAM fora few years now and here is our basic setup:

• Each server has it's own job (instead of grouping together) and jobs are all scheduled to start at 10pm daily, with the jobs limited to 4 concurrent jobs
  
• VEEAM backs up production data to local SAN using the forward incremental method with a 30 day retention. (Other job settings include things like vmware quiescencing, change block tracking, application-aware processing, guest file system indexing, etc)
  
• The jobs are also set to create weekly synthetic backup files (these are load spread across the week to help load on the backup device - synethic jobs create new full backup files based on merging previous incremental backups together - the load is entirely on the storage device, not the server/network)
  
• Three more jobs also configured; End of Term 1 - 24th December each year, End of Term 2 - 2nd Sunday of April each year and End of Year - 31st July each year. These are for long term data retention and the EoY files can be copied off to other media or cloud for archiving
  
• A backup copy job is configured for each job with the target as another NAS in a different building (as a fire safety precaution)
  
• We use RClone monthly to copy off the synthetic backup file to our cloud repository
  
• Backup jobs are encrypted within the job settings
  

We do not currently backup Office 365, which with VEEAM, requires a separate license and application if I recall correctly.

 

I don't know how that stacks up with other configurations, but it's served us well over the years.

 

Thanks for this, really useful to know. I asked VEEAM for a bit of advice and they redirected me to their video tutorials so I need to sort that out.

 

I need to do a bit of tweaking. We are a smallish school so all storage is internal in the server (around 10tb). I was running a backup job of our file server which is around 1tb which failed after 2 days.. really slow.

[supportman]

We've been using VEEAM fora few years now and here is our basic setup:

• Each server has it's own job (instead of grouping together) and jobs are all scheduled to start at 10pm daily, with the jobs limited to 4 concurrent jobs
  
• VEEAM backs up production data to local SAN using the forward incremental method with a 30 day retention. (Other job settings include things like vmware quiescencing, change block tracking, application-aware processing, guest file system indexing, etc)
  
• The jobs are also set to create weekly synthetic backup files (these are load spread across the week to help load on the backup device - synethic jobs create new full backup files based on merging previous incremental backups together - the load is entirely on the storage device, not the server/network)
  
• Three more jobs also configured; End of Term 1 - 24th December each year, End of Term 2 - 2nd Sunday of April each year and End of Year - 31st July each year. These are for long term data retention and the EoY files can be copied off to other media or cloud for archiving
  
• A backup copy job is configured for each job with the target as another NAS in a different building (as a fire safety precaution)
  
• We use RClone monthly to copy off the synthetic backup file to our cloud repository
  
• Backup jobs are encrypted within the job settings
  

We do not currently backup Office 365, which with VEEAM, requires a separate license and application if I recall correctly.

 

I don't know how that stacks up with other configurations, but it's served us well over the years.

Nice! I didn't even know about the backup copy functionality!

 

I'd be interested in if anyone has managed to get this working with Azure.