Just an overlook: https://aws.amazon.com/it/blogs/aws/glacier-vault-lock/ .

It should be cheaper than tapes or HDD for that range of data.

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

0_1501712220659_Screenshot from 2017-08-02 17-16-46.png

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.

Simplistically speaking, when it doesn't work.
If it works, then it's a backup.
If it does not work, then it's a waste of time and disk space.

@JaredBusch said in Hardware Design for SAM-DR Small Rackmount Backup Device:

@matteo-nunziati said in Hardware Design for SAM-DR Small Rackmount Backup Device:

@scottalanmiller just a question (sw not hw) why veeam rather than say.. altaro. Just curious!

There is no backup software on this device. It is a storage target. One assumes that @scottalanmiller will be using some base OS that lets you setup basically any type of connectivity.

Ok! Got it wrong! Thanks for clarifying

lol - the ultimate in ransomware protection. watch they don't raise prices, that's a premium feature

@scottalanmiller Replacement as (rather than use vanilla rsync) I'll go with this version.

I've used rsnapshot a good bit and it's a really nice tool for simple backups.

@aaronstuder

Tried it today in Windows enviroment for both server and client, and while it is easy to setup it took forever for 1 image BU to complete. not sure why was not limited in CPU or RAM, and after 45 mins I stopped it and didnt care about it anymore, the client was fresh windows with 14 GB on C :

@scottalanmiller said in Share Your Backup Failure Stories to Celebrate Backup Day:

@RojoLoco said in Share Your Backup Failure Stories to Celebrate Backup Day:

Backup Exec....

Say no more, we feel your pain.

Sadly we have that in one area as well. I don't understand why.

It's true that you can make stateless systems without DevOps tooling and approaches. But the nature and assumptions of those systems is that you cannot. Just letting arbitrary logins (even of administrators) can undermine that. One of the beauties of the pure DevOps model is the lack of logins. Much like functional programming.

If ever there was an RGE*, this would be it.
 
 
 
 
*Resume Generating Event

@Dashrender said in When a Backup Becomes an Archive:

@BRRABill said in When a Backup Becomes an Archive:

@Dashrender said in When a Backup Becomes an Archive:

Way to flip it back on them.

Did you drop an imaginary mike afterwards?

Knowing Scott, he did. Just in his own way.

Knowing Scott he probably had a real one in his pocket, which he pulled out, then dropped.

It's on my calendar. I want to hear about all the new stuff @scale is up to!

@FATeknollogee said in XenServer: Backup & Replication:

I assumed we "are" talking about 7.0?

Yes, it works on XS7.

@DustinB3403 was running into the same issues I was on 6.5.

There is dicsussion that some other process is changing it back, but we have not started to troubleshoot that. (I no longer have any XS6.5 boxes here.)