@nerdydad - That is very soon.

@dbeato said in Synology NAS - Can't delete: @bbigford said in Synology NAS - Can't delete: @dbeato said in Synology NAS - Can't delete: As an aside question, do you have it that it recycles the storage after certain time with Synology to Synology backuP? What do you mean recycles? It's not doing an offsite move-delete if that's what you mean, it's copying it in case either building is lost. Maybe I don't understand the question. So when I setup the backup between Synology devices, I make sure that after a certain time/age the backup device deletes the older snapshots/backups. Ah, got it. What are you using for backup software that you'd rather your backup software not delete it? Also, are you using Synology CLI for that? I don't know that I've noticed that option in the GUI as part of the task creation.

@dustinb3403 said in Veeam Free Windows Server Backup Agent: @jaredbusch said in Veeam Free Windows Server Backup Agent: @dustinb3403 said in Veeam Free Windows Server Backup Agent: So the biggest item missing from the Veeam Agent for Microsoft Windows is it lacks a central management component. Which isn't horrible but it does leave some things to be desired. . . No, it is not missing. That is a feature of the Veeam B&R product. You can (or soon can) manage Veeam Endpoints that point to a Veeam B&R instance. Yea with licensing, the topic is solved. Veeam Endpoint works without limits. But it lacks a central management interface. B&R is a licensed product, right? Yes, it is.

At least you found a (somewhat) viable workaround.

@manheraz This may help a bit: https://www.virtualtothecore.com/en/permissions-for-veeam-backup-linux-repositories/

Veeam also has a Linux based recovery environment that can provide full recovery of Linux VM's into the HC3 system. Unlike windows, the virtio drivers are already built in to the Veeam Linux Recovery ISO so there is no additional step required for it to see the disk to recover to ... so in this example, I just want to restore all of disk vda from the backup repostory to the blank vda disk. Restore the entire disk.

100% correct. I misread my quote, and thought it was X per socket, rather than X for two sockets.

@dustinb3403 said in Cross-Post Hyper-V and Backup recommendations: My question is, should I also run backup agents (I use Veeam), on the Hyper-V environments and back them up as if they were physical boxes? Or is the daily backup fine. General practice is to not back up the host itself. You should have a process to rebuild the host and, in theory, this should be incredibly fast and simple. Since restoring bare metal is always a pain because you have to get the restore going without an agent, rebuilding a nearly stateless host is generally faster and simpler and doesn't require storage and management.

@eddiejennings said in Food for Thought: Backups - from terrible to functional: @jaredbusch Wow. Was an initial seed of a server. So totally expected when the WAN pipe is only 10mbps up. 120GB of real data on a thin provisioned 500GB vhdx.

@tim_g said in UrBackup vs Veeam: I don't think urbackup supports hyperv vss for backing up VMs without downtime. You will need to back up VMs from inside them, as if they are a physical server. So if you want to back up VMs at the host level, which is a major benefit of virtualization, then you are stuck using a non open source backup solution. If you want free, then you will just have to use the built in Windows Server Backup or hope you are within the limits of the free stuff like Unitrends. If you have the time to figure out how to get AMANDA to use hyperv vss for example, do share! Right, it's simple agent only.

Veeam DOES recommended avoiding low end NAS devices, and recommends SAN over NAS because Veeam wants block protocols. These parts are true and we don't need to watch videos as they are available in writing from @Rick-Vanover - we even have the author of the best practices here in the community! https://www.veeam.com/blog/vmware-backup-repository-configuration-best-practices.html The keys here are "low end" which is an issue around support. The misleading bit is that NAS means server, so low end servers are every bit affected in the same ways. The QNAP, Synology, ReadyNAS and other such devices are not actually NAS but Unified Storage, SAN as much as NAS. That Veeam recommends SAN instead of NAS is a protocol choice, it does not make those devices any less applicable. We should not be calling them NAS, as that is misleading, they are equally both. If we really look at the guidance and consider what it could mean, the only real concern is "low end" and low end is always of some concern. Why spend so much on Veeam and Windows licensing and then get cheap on the hardware? You want solid storage hardware and solid support. But nothing here is telling us that there is anything wrong at all with these kinds of devices and certainly the issue is not some kind of corruption caused by the fact that they are in this product category.

@Dashrender said in How Do You Use USB HD for Veeam on Hyper-V: @scottalanmiller said in How Do You Use USB HD for Veeam on Hyper-V: @JaredBusch said in How Do You Use USB HD for Veeam on Hyper-V: Don"t use USB disks. If you want a USB disk that can be removed, use a NAS with a USB port that can replicate data in a certain folder to the USB. Or use a NAS with Starwind VTL so that you get the behaviour of tapes. And the protection of RAID. I'm going to have to look at that It's a cool product.

Here is a link to what the rest of us missed from VeeamOn 2017 - https://www.veeam.com/veeamon/product-announcements#announcements-section

Reinstallation fixed it but I don't know why.

@Dashrender said in Shadow Protect SPX vs Veeam: @BRRABill said in Shadow Protect SPX vs Veeam: @JaredBusch said in Shadow Protect SPX vs Veeam: I cannot believe I just read the last few posts. You should start a thread on SW called "I Can't Even" and post it there. You are just not helpful. Come on now, it's Monday. Laugh a little.

@Dashrender said in Deploying Veeam Endpoint Backup on Windows with PDQ Deploy: I'm not sure where else to mention this, but Chocolately would be another deployment method to consider. Yes, no native package, though. So we need to make one for it. That would be my personally preferred method, of course.