That resource library is really light on content. How did StarWind Virtual SAN solve their manual backup problem? "High performance and data high availability (HA) were not the only benefits for the company, meaning StarWind support t hat continues to solve the problems with ease." Is having to contact support for problems with the VSAN another benefit? It might as well say: Problem: Company needs to make a stew. Solution: Company bought a pot.

@StorageNinja said in Veeam with NetApp?: Netapp E-Series is the same as the old Dell MD36xxx or the LSI enginio code base (IBM also sold a similar low-end modular array). These things were wicked fast/cost-effective at streaming workloads (got used for Lustre clusters a lot as the DAS on the nodes). Dell's abandoned reselling them for Seagate (Dothill) but they still around Not wicked fast compared to building your own. And the staggering lack of internal support if anything goes wrong is a big deal... storage is one of those things you want to have work, especially at these price ranges. Having been a NetApp customer, I know that their support is helpless when it comes to trying to do high performance, their crap just falls over and so do their engineers.

Worth noting on this that while sync works, copy is the much safer option. So rclone copy source:/path dest:/path is what I'll likely end up using. In any case, the resulting solution still works. Still need to tweak OSX a bit as it seems to kill the SSH session after some time for sporadic reasons - still testing but I may end up having to add ServerAliveInterval 120 to /etc/ssh/ssh_config to resolve that issue.

@IRJ said in Duplicati Retention Policy, which do YOU choose?: @JasGot said in Duplicati Retention Policy, which do YOU choose?: The options are: Keep all backups Delete Backups older than Keep a Specific number of backups Smart backup retention Custom Which do you use and why? I am interested in your choice and why you choose it. Generally NO longer than legally required. Unless the legal requirement is something really lax. You generally dont want to keep data for longer than 7 years in any circumstance where there is no legal requirement, because you can become legally obligated to share data in a court case or something of that sort. Exactly. Desired retention is more like 6 months. Only legal requirements make us go longer.

I've been using Duplicati where I need a standalone backup of a thing. Web based management interface makes it super simple to manage.

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

@Dashrender said in Make an osTicket Database Backup: Total DB Admin noob here - so bare with me. Does this include the username/password setup for this DB? or does that need to be maintained separately? i.e. you have to rebuild from this backup - do you just create a brand new SQL user and grant them rights to this DB upon import, then use that new account to give access to the app? In typing out my question I kinda assume the answer is the second bit - you just create a new user and assign them rights. Correct. The user and the database are separate things.

Can you reassign disks between VMs yet? The hot add disks was a huge pain before. I couldn't believe I wasn't able to do that.

@CCWTech said in Restoring Google Drive Folders Instead of Individual Files: Unfortunately what they did ended up orphaning the files. https://support.google.com/a/answer/6008339?hl=en Ouch

@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

@wrx7m said in Why DR Plans are Important and Need to be Tested: This is a good reason to have more than one credit card from more than one bank. This isn't just a credit issue though. It's people literally unable to access their own money, not money on credit. More so if people have the money in their checking/savings account to pay their bills why should they have to pay their bills on credit?! The bank had better pay off any interest if their customers had to use a credit card to pay for anything during this time to get things back to Zero.

@DustinB3403 said in Backup Options - Licensing Costs - Storage Targets: @dafyre said in Backup Options - Licensing Costs - Storage Targets: When we start looking, we'll start with the usual culprits like Veeam. ShadowProtect comes highly recommended to me by several folks (Including the guy who just built the ReadyNAS)... We'd hit the other major players as well. So cost is going to bite you in the ass, since you said there were concerns about licensing. But they are all valid options. @dafyre said in Backup Options - Licensing Costs - Storage Targets: Good Backup Compression / Deduplication is a must. We have ~30TB of systems and data. You can perform the compression on your storage layer or use dedup or both. This may affect the overall performance though. @dafyre said in Backup Options - Licensing Costs - Storage Targets: We don't care if it's full install, agent based, or Hypervisor based. It just needs to work. Based on this I would think Agent based would be a decent option. But didn't you say you have something along the lines of 300 VMs? Might become tedious. Yeah, we'd likely do the dedupe at the Storage layer. Our Current Nimble devices do this relatively well with our live data. Something like 1.3 or 1.4 to 1 compression is what i remember. It may be more or less. If we went Agent based, we can push the agents via PDQ Deploy for Windows and a shell script or something for Linux. (Most of our Production Linux systems are SLES 12)... If reboots are required, systems can be rebooted during our patch window... (5-7am every day).

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

In the event now.