This should be fine. I have a similar configuration with restore points and it works as designed.

@NashBrydges said in Leveraging Veeam Cloud Tier - Backups To Wasabi: @wrx7m said in Leveraging Veeam Cloud Tier - Backups To Wasabi: I upload Veeam backups to Wasabi (and before that, S3) outside of Veeam. I pull down the backups and import them back into Veeam, via the import feature. I would like to see how well it works when everything is natively done in Veeam. If that is even possible. How do you upload your backups to Wasabi? Are you using a 3rd party tool? Yeah. I use a file compare tool called, BeyondCompare that runs on a windows task schedule.

@scottalanmiller I was considering rolling them back to last night as a last-ditch scenario is all fails since it is on Veeam and I have a Full from last night.

Our go-to solution for VSS problems is to set up a dedicated snapshot volume. Otherwise we were getting timeouts and M$ does ugly things that don't make sense when VSS doesn't work properly.

@smartkid808 said in Veeam Backup & Replication Community Edition: @JaredBusch my bad. They just posted it on SW couple days ago about it, and the blog on the Veeam site is only 2 days old, didn't realize it was here already Don't be afraid to repost. Hell I've done it before. I just want all the things cross linked whenever possible. Makes it easier to find details in 6 months. In this case I even mis-remembered where the fuck I read about it. Thanks @dbeato.

@NashBrydges said in Backing up Office 365: @Dashrender @Jimmy9008 My largest client to use this for their Office 365 backup has 42 mailboxes and it works very well for them. I can't confirm with anything larger than that though. In theory then it should work well for me. Will test and see. Thanks

So, circling back. How is the backup project going?

Also what does this mean for updates to the agent

@jaredbusch said in Backup server - Software layout: I use teams, even if there is only one NIC in the team most of the time, because I can add and remove NICs without impacting the higher layers. Good idea. This server I just got has the onboard GB NICs, but also 2 dual port Intel GB NICs as well. I could create a BIG team if I wanted.

@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.