I agree not scalable but it functioned/worked. The only server I never
restored was the virtual DC all the others in this instance restored and
functioned. Client refused to purchase a better system. Client had dedicated
hardware for the primary DC. It was backed up separately.
Jon
> From: [email protected]
> Date: Tue, 6 Aug 2013 22:25:21 -0400
> Subject: Re: [NTSysADM] RE: Veeam or Altaro?
> To: [email protected]
>
> On Tue, Aug 6, 2013 at 8:17 PM, Jon Harris <[email protected]> wrote:
> > Under 2008 it worked had it running at night full backups not typical but
> > for the setup I was doing this on it was the best option. VM's were up and
> > running on the host backed up the entire host.
>
> FYI, Microsoft's official guidance on several things (notable Active
> Directory) is that the only way to properly backup a VM is by running
> the backup on the guest OS, inside the VM. Backing up the host,
> snapshotting the VMs, is Not Supported(TM).
>
> We've been tinkering with running backups via Windows Backup and
> WBADMIN. Rather like NTBACKUP, the documentation isn't the best, the
> diagnostic message stink, and it's somewhat touchy, but we eventually
> got it be stable, for some definition of stable. It doesn't seem like
> a very scalable solution, though. I'm trying to get approval for a
> more sophisticated solution.
>
> -- Ben
>
>
