Upgrading our Veeam backup server
-
Furthermore, with several (maybe most) Synology models you can expand/add storage via optional enclosures that would be completely transparent to the devices you are presenting the volumes to. So it would not even need the Veeam scale-out feature to allow you to increase storage capacity.
-
Is it ok to run Veeam server as a VM on the host that you want to backup, or should it always be on a separate host? Or can you install it on two hosts for redundancy? We only use local storage for VMs.
Is you repository part of a VM or just raw storage outside of any hypervisor?
-
You can install Veeam where ever you want. Just keep in mind that if you install it as a VM on your one and only VM host, when that host is down, so is your ability to restore any data, So this means that you need to have a plan on who you are going to gain access to your backups so you can restore them to another VM Host.
As for the backup data - @wrx7m did mention that he is backing up his data to a Synology 1813+ which he called a backup repository. While he didn't specifically say it, we can only hope that his VMs aren't running from that same appliance. If that assumption is true, and he has a VM host failure, his recovery scenerio could be like the following:
install Veeam on a desktop in the office
import backups from Synology
install hypervisor on new VM host
restore VMs to new VM hostThis is a very top level view of steps, but as you can see it's really not that complicated.
-
@Dashrender said:
You can install Veeam where ever you want.
Well, yeah. But just because I can doesn't mean I should.
My second question is basically asking if the repository is a CIFs share on the NAS, or storage on a Windows/Linux VM (with the VMs storage being a datastore on the NAS) . I'm inclined to use the latter, but don't know what's best.
-
@Carnival-Boy said:
@Dashrender said:
You can install Veeam where ever you want.
Well, yeah. But just because I can doesn't mean I should.
I suppose that's true. If you have a Windows license free to run Veeam on the VM host, I'd probably do that.
My second question is basically asking if the repository is a CIFs share on the NAS, or storage on a Windows/Linux VM (with the VMs storage being a datastore on the NAS) . I'm inclined to use the latter, but don't know what's best.
If the ultimate location of the data is on a NAS, I'd skip the intermediary step of the VM.
here's my setup:
VM running AppAssure Replay (it's like Veeam, mostly) attached to that I have DAS storage - a Drobo Pro that only works with either USB 2.0 or iSCSI. So I have the appliance mapped directly inside my Replay VM. In case of VM host failure, I can move the iSCSI connection to another host, install Replay, import the backups and be back in business. -
@Carnival-Boy You can run as a VM and Veeam will backup itself/its own VM. I only use local storage too. If you add the NAS in Veeam, you don't need it to be a VMware datastore.
-
I am not running any VMs off of the NAS that I backup to. That would just be stupid.
I do have a file share for my Graphic design team on another NAS (older Synology 1812+) that does have a VMware datastore on it and a single VMDK for data. That VMDK is backed up during the normal Veeam backup to the normal backup repository.
-
@Carnival-Boy Mine is a CFIS share on my NAS that is not shared via Windows but by Synology, itself.
-
Another thing is that with Veeam you should also be backing up the config. This would allow you to install Veeam wherever and import/restore the config to another box. Access it by going to the Menu and selecting Configuration Backup.
-
@wrx7m said:
@Carnival-Boy You can run as a VM and Veeam will backup itself/its own VM. I only use local storage too. If you add the NAS in Veeam, you don't need it to be a VMware datastore.
@wrx7m said:
@Carnival-Boy Mine is a CFIS share on my NAS that is not shared via Windows but by Synology, itself.
These two posts seem to contradict themselves. First you mention only using local storage, then mention using a NAS. Do you mean you only use local storage for the VMDKs? If so, that's contradicted by this post.
@wrx7m said:
I do have a file share for my Graphic design team on another NAS (older Synology 1812+) that does have a VMware datastore on it and a single VMDK for data. That VMDK is backed up during the normal Veeam backup to the normal backup repository.
where you mention that you have a VMDK on a different NAS.
-
@Dashrender I mentioned that I only use local storage as it applied to the Veeam server itself. Sorry if that wasn't clear. I also specifically mentioned that a VM has a separate VMDK that is on the secondary NAS.
-
@wrx7m said:
@Dashrender I mentioned that I only use local storage as it applied to the Veeam server itself. Sorry if that wasn't clear. I also specifically mentioned that a VM has a separate VMDK that is on the secondary NAS.
thanks for the clarity
-
I've run Veeam both (in the past for over a year) on a VM on one of my hosts and now on a physical server. The latter is recent and I'm doing B2D2T and my LTO hangs off the physical server. Just was a free box. Whether physical or virtual, definitely keep the backup config in a different location. With that, it really doesn't take long to get it back somewhere else. My target is still a NAS using CIFS, but that will change probably when I redo my storage and hosts. You get a decent performance boost by using it as a iSCSI target vs CIFS. Mine works fine with the latter, so YMMV.
