fspeece wrote:Each vHost will have a RAID10 set of disks for the VMs to run on normally, plus a single 1TB drive to hold backups (we don't have a lot of data). I plan on backing up the VMs so that (for example) VM1 on HostA gets backed up on HostA and also replicated or backed up to HostB, in the case that HostA dies, I can restore the VM manually on HostB. Does that sound like a good plan?
fspeece wrote:I have another server that runs our physical server backups currently with spare RAM/CPU, I'm thinking I can run veeam and vCenter software on that physical server, so that if something happens to the physical virtual hosts, I can manipulate VMs and do Restores.
fspeece wrote:How does the veeam software connect to the storage on the virtual hosts? Do I just create a datastore on top of the 1TB drive I have, and veeam uses vCenter to view that space? I have no experience with veeam, and some experience with vmware but its been a while. Using veeam so that we do not need higher vmware licensing and shared storage, plus we have at least 2 servers for each critical role (database servers are not virtualized).
fspeece wrote:I believe veeam and vcenter using the SQL Express DB and being on the same server would probably be fine for my small deployment (I don't see us going over 50 VMs for a very long time) from a resource perspective.
fspeece wrote:Am I correct that it would be a bad idea to have veeam and vcenter both in VMs sitting on HostA, then if hostA went down, I would not be able to run restores, before somehow getting veeam working again?
fspeece wrote:But vCenter on a VM is recommended so that I can do easy backups and restores on it I assume (no vMotion consideration because no shared storage)? I do need to worry about the backups on that physical server now though (if I put vcenter and veeam on it).
fspeece wrote:Is veeam dependant on vCenter for restores?
fspeece wrote:"place a proxy server on each host" does that require another VM and windows license on each host then?
fspeece wrote:We got new virtual host servers with storage on them, no extra storage on the spare physical server, plus if I can get the backup traffic just on the virtual hosts I figured that would be better. We don't have a separate backup network either (probably don't need one).
fspeece wrote:If I put veeam on my spare physical server how does veeam connect to that spare and use it as a backup destination?
fspeece wrote:It would go over the normal network, or possibly over another network if I wanted to configure that.
fspeece wrote:For the space it would be a simple single disk at the hardware level, with a datastore on top of that, then a VMDK on top of that, with the VM backups and replicas inside the VMDK(s)?
fspeece wrote:Does that space need to be attached to a VM? Not sure if I have that whole logical structure/design correct in my head.
Users browsing this forum: felipehanciau and 1 guest