The correct way to offsite Veeam requires Veeam installed on a system at the remote site. That remote Veeam instance is what talks to the remote data store.

If you are only doing copy jobs, the remote Veeam instance does not require Veeam licensing.

@IRJ said in Windows Server 2012 R2 - Share Auditing for Changes:

I know you use wazuh..

Check this out

https://documentation.wazuh.com/current/user-manual/capabilities/file-integrity/index.html

Thanks! Checking out setting this up. Hopefully, it will reveal the culprit.

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

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

Also what does this mean for updates to the agent

Watch @vmiss33 & @nielsengelen bring you the scoop on what #Veeam announced today at #VeeamON 2018 - Veeam Backup for Microsoft Office 365 v2 (with OneDrive, Sharepoint & OneNote protection), DataLabs & more! Check out the blog post recap too:

At least you found a (somewhat) viable workaround.

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

@scottalanmiller said in SQL Server Backup Design:

@jaredbusch said in SQL Server Backup Design:

@tim_g said in SQL Server Backup Design:

I'm with Jared on this one...

Backing up through the application layer (SQL) as often as you can depending on change frequency. For example, every 15 minutes.

Hourly and daily through the SQL backup tools.

At least daily full VM backup at the hypervisor level.

I prefer backups that use a standard file format, so you don't have to rely on Veeam for example to restore it. Veeam has screwed up too many times for me to want to rely on it like that.

I have never had been fail

Except for statements like this.

For some reason Siri does not like Veeam yet. Even though correct it a lot

@tim_g

Hi, I'm working for Veeam.

Could you be a little bit more specific on the following, please?

When a newer version of Linux (kernel) arrives, the fix no longer works.

What distro do you use?

Many softwares are free that work on CURRENT OSs, that do not automatically break every time there's a new kernel release.

I'm not sure which softwares are you referring to, would you provide an example of a backup software that works on current (not stable) releases?

I asked in their community forum which person I need to private message for a fix this time... and they point me to support to fix a product that's WAY behind.

Did they (support) provide you with the wrong fix?

<...> especially with how they treat the whole issue on their forums.

This one is interesting - no one would point you to the support team for no reason. Whoever forwarded you apparently had an information that support had the fix. Would you give us the link to the forum message that you've mentioned? Also, what's wrong with going directly to support team to obtain a fix, especially if someone form the company advised you to do so?

And yes, Veeam Agent for Linux requires you to install a 3rd party (Veeam's) kernel module to make the thing work. Otherwise there would be no snapshot and CBT (changed block tracking) capabilities in the product.

Thanks

Reinstallation fixed it but I don't know why.