server backup

[pcpete]

We don't do a lot of servers, well actually just one, as our vet clinic we take care of upgraded their software and needed a server. What would be best practices to back it up? What specifics would you recommend. It is mainly just hosting their db and some other stuff, but not lots of GBs.

 

[Moltuae]

Presumably just a single physical system and no VMs?

My personal preference is to use Macrium Reflect (Server Ed.), an internal/local backup drive, a NAS and cloud storage.

Schedule Reflect to make encrypted* FULL drive image backups of the system drive and data drive(s) once a week, with incremental backups daily, hourly or at whatever frequency is required, to both the internal/local drive and the NAS. For off-site backups, I would schedule Reflect to make (encrypted) file/folder backups of all business-critical data, and have it drop them into a cloud-sync'd folder (eg OneDrive). The local backup is useful if you need to quickly restore the system, especially if you use Reflect's rescue media wizard to add the Reflect (Windows PE) option to the boot menu. The NAS should ideally be sited as far away from the server as possible to reduce the likelihood of both the server and the NAS being affected by disasters such as fire, flood, theft, etc.

*For GDPR compliance I'd recommend enabling Reflect's backup encryption for all backups, but especially for backups that are to be uploaded to cloud storage.

 

[pcpete]

thanks @Moltuae

 

[Moltuae]

No problem.

Forgot to add: If you do use Reflect, be sure to enable automatic backup verification (it's off by default) and configure email notifications for backup failures. And to save yourself some work, I would recommend configuring both of those in Reflect's default settings, before you start configuring scheduled backups.

 

[YeOldeStonecat]

How "fast" do they need it back up and running...if the server were to..catch fire?

I always start with that question. And then realistically tell them (spell out) how long it takes to restore a server based on which type of backup product/service.

Could be a week or more...(quote a new server, specs, create invoice, receive payment, order server, receive server, build, and then...begin the restore process. Could be several days or more!) Or, do you need it running within an hour? If so...step up to business continuity type of backup...like Datto Siris.

 

[Big Jim]

Veeam was reccomended to me and its free for the first few machines.

 

[HCHTech]

How "fast" do they need it back up and running...if the server were to..catch fire?

I always start with that question. And then realistically tell them (spell out) how long it takes to restore a server based on which type of backup product/service.

Could be a week or more...(quote a new server, specs, create invoice, receive payment, order server, receive server, build, and then...begin the restore process. Could be several days or more!) Or, do you need it running within an hour? If so...step up to business continuity type of backup...like Datto Siris.

This is the right way to approach it. It lets them know upfront that there are many ways to do "backup" and the faster you can restore, the more it costs. You can use Windows Server Backup (free) with a couple of external drives (cheap) and be fine as long as they are happy with a week or more potential downtime. Or you can go the Datto route (costs a lot) and have your downtime be as little as "minutes". This way, **they** are the ones making the selection and the tradeoff between price & continuity. If you do it any other way, then all they will remember is that "You chose the backup", so you will be the one they direct their anger towards if that week of downtime ever materializes.

I don't have any Dattos in the field, although I have pitched them. My fanciest backup setup is using Quest Rapid Recovery. Hourly backups to a dedicated onsite machine, which replicates hourly to a dedicated offsite machine through a site-to-site VPN. The protected machines are all VMs so restores would be fairly quick, although we've never had a meltdown so we've only done test restores. They definitely spent a few bucks on the setup, but we've had very few problems over the years - I'd absolutely do it again.

 

[Mick]

@pcpete - From what you said originally - are you sure they actually need a server? If it's just hosting a db (so basically just a file-server), wouldn't they be as well off with a NAS? Lots to go wrong with a server, not so much with a NAS.

 

[YeOldeStonecat]

I don't know of any veterinarian clinic software that doesn't need a Windows box to be served off of.
I see about the same points of failure between a NAS and a server. Mostly it's hard drive related...use proper server grade ones, maintain those, and back it up!

 

[pcpete]

@pcpete - From what you said originally - are you sure they actually need a server? If it's just hosting a db (so basically just a file-server), wouldn't they be as well off with a NAS? Lots to go wrong with a server, not so much with a NAS.

It is for Avamark vet software. When they wanted one db for two locations they were told they needed a server os. It seems to only work as a simple file server, so I am not sure what the server is doing that the old desktop with a share was