Salta al contenuto principale

Recommended solution for backup of 2 VMs

Thread needs solution

I have a Hyper-V Windows 2012 server running 2 VMs

The VMs are

1 x Windows server 2012 R2 (DC - includes file shares and active directory)
1 x Windows server 2012 R2 (database server - includes sharepoint and another couple of programs running MSSQL Express)

We would like to backup to a NAS every night. What would be your recommended solution for carrying this out?

should we just install the software onto the host and backup the whole VM's or should we install agents onto the VM's and run it from there?

first time using Acronis so not sure what is best practice

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 22
Commenti: 3800

Hi Tony,

Typically it's always recommended to use agent-less backup approach as it causes less effect onto the services running on VMs. Agent-based approach is recommended only if you have some unsupported configuration of the VMs, such as external devices connected to them in pass-through mode (the devices which are not affected by Hyper-V snapshots).

Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager

If your virtualization host server is not a member of the domain, but the management server is a member of the domain, be aware that the "Plan permissions" of each backup plan created on the management server will default to a domain account and cause all backup jobs you attempt to run on the host server to fail.
You must specify for both the backup source credentials and the "plan" credentials: an account with administrator and logon as a service rights to the virtualization server.
We discovered this the hard way after days of chasing driver updates, new accounts, reinstallation, etc., until we found that the "plan" credentials were defaulting to the AMS server's account and not the backup target's account.
Support was unable to solve this issue, they assumed that the host server accepted domain credentials, even after being informed it wasn't part of the domain. In the case of small sites with just one host server and no other DC's to authenticate against when restarting the host server, best practices dictate your host should not be a member of its own VM's domain to prevent cyclic dependency issues.