Centrally Controlled Local Backup System Options
-
@DustinB3403 said in Centrally Controlled Local Backup System Options:
Local repo's with a locally installed piece of software that copies to a cloud provider.
But lack a working "final target" locally. So they do ALL the part that you are worried about.
Veeam does it all, but requires a full Windows Server additionally locally. It has ALL the parts we need, just requires a lot of infrastructure.
-
@scottalanmiller said in Centrally Controlled Local Backup System Options:
@DustinB3403 said in Centrally Controlled Local Backup System Options:
Not a centrally managed interface which reaches into the client network.
No, this is the piece that they all have.
Veeam (afaik) requires a system on-premise to run and manage the backups (which can be saved locally and to the cloud as well).
Nothing is cloud managed from an IT perspective, you don't setup, backup or restore from a cloud interface. It's all locally operated.
-
@scottalanmiller said in Centrally Controlled Local Backup System Options:
@Obsolesce said in Centrally Controlled Local Backup System Options:
By local backups, are you saying as in locally attached disks to each workstation / server and not a shared on-prem backup repo?
Both is best. But ability to handle locally attached (e.g. USB external drive) is critical. If can handle NAS too, is even better.
Hmm, not sure about that one. I've never come across that specific need to require locally attached USB disks in with the backup solution's DB. Those were always adhoc and done via Veeam Free (or Windows Backup) and not managed, just scheduled with email notifications set for failures. But always pushed for no local backup, and to use modern means of working file storage (ODfB, Google Drive File Stream / Backup and Sync, etc).
-
I think the biggest issue you're attempting to address @scottalanmiller is to have some hundreds or thousands of clients reach out to something on Vultr for example, and having whatever that is reach back into each of those disperse networks and write things to something on premise.
-
As an MSP I would think you would feel much better about having standalone systems for each of your clients, this way there is 0 risk of one massive failure domain affecting every one of your clients.
Potentially ransomware'ing all of them in one full swoop.
-
-
Is NTG wanting to be the next PROtek support, because this is what it sounds like you're looking to do @scottalanmiller !
-
@DustinB3403 said in Centrally Controlled Local Backup System Options:
I think the biggest issue you're attempting to address @scottalanmiller is to have some hundreds or thousands of clients reach out to something on Vultr for example, and having whatever that is reach back into each of those disperse networks and write things to something on premise.
Like I say, though, same as every major backup mechanism. They all do this. All. This is actually way, way safer because only status, not data, is being moved outside of the network. All of the ones that I can find do this PLUS move data from onsite to offsite, too.
So like a bazillion times safer only doing local data without any remote from a security perspective.
-
@DustinB3403 said in Centrally Controlled Local Backup System Options:
As an MSP I would think you would feel much better about having standalone systems for each of your clients, this way there is 0 risk of one massive failure domain affecting every one of your clients.
Potentially ransomware'ing all of them in one full swoop.
That's similar to the logic that you'd have separate backups for every desktop, rather than a central backup system for all desktops. Sounds good, but it's not affordable. Clients won't pay for that kind of high touch service. It would be great, because as an MSP you make a fortune for things like that. 15-30 minutes of "logging in to look at your backups" every morning, for every client, adds up quickly.
-
@DustinB3403 said in Centrally Controlled Local Backup System Options:
Is NTG wanting to be the next PROtek support, because this is what it sounds like you're looking to do @scottalanmiller !
You seem to be missing that every backup vendor on the planet pretty much does this, but way riskier. The entire market. All of it.
And it's not for NTG.
-
@scottalanmiller said in Centrally Controlled Local Backup System Options:
All of the ones that I can find do this PLUS move data from onsite to offsite, too.
The issue is the tool you mentioned to me offline, requires that the data reach the server, and is then written to whatever storage is locally mapped.
So the data has to stream out to the VPS, and then back in to whatever storage.
Where as the simple and "cost-effective" system would be to just have each of this separate systems send in an email once a day or week as the backups finish so you as an MSP can manage it.
It keeps the data local ( a critical key for any customer ) as "Backups always need to be local, for any business. Cloud backups are almost always a fallback scenario".
-
@DustinB3403 said in Centrally Controlled Local Backup System Options:
The issue is the tool you mentioned to me offline, requires that the data reach the server, and is then written to whatever storage is locally mapped.
Right, which is why that's only mentioned as "not an option." The need is for that not to happen, hence why there is a thread on this, not on that.
-
@DustinB3403 said in Centrally Controlled Local Backup System Options:
So the data has to stream out to the VPS, and then back in to whatever storage.
Right, in the scenario opposite of the one being discussed here. That's the "not an option scenario", instead of the "scenario I'm asking about".
-
@DustinB3403 said in Centrally Controlled Local Backup System Options:
Where as the simple and "cost-effective" system would be to just have each of this separate systems send in an email once a day or week as the backups finish so you as an MSP can manage it.
No, emailing status is never a viable option. Because it's when an email "doesn't happen", ergo no notification, is when something is wrong. So that's never okay in production. Might be okay when monitoring a single system, but not hundreds.
No, a central console is the only logical and effective scenario. Exactly what I asked about. That's why I asked specifically about products that do the sensible thing as any that send data out or do email or lack a central console simply don't work.
-
@DustinB3403 said in Centrally Controlled Local Backup System Options:
It keeps the data local ( a critical key for any customer ) as "Backups always need to be local, for any business. Cloud backups are almost always a fallback scenario".
Right, but so does the thing I asked about. Except my ask meets the need rather than simply not addressing the problem.
Your solution is the same as saying "ignore the problem and don't address it", even when what it takes to address it well is practically nothing.
-
@scottalanmiller said in Centrally Controlled Local Backup System Options:
@DustinB3403 said in Centrally Controlled Local Backup System Options:
So the data has to stream out to the VPS, and then back in to whatever storage.
Right, in the scenario opposite of the one being discussed here. That's the "not an option scenario", instead of the "scenario I'm asking about".
So you're asking what MSP central backup options exist (and are FOSS)?
-
@DustinB3403 said in Centrally Controlled Local Backup System Options:
So you're asking what MSP central backup options exist (and are FOSS)?
No, to repeat the original question...
I'm asking if a central management or non-central backups exists, in any form.
-
@scottalanmiller said in Centrally Controlled Local Backup System Options:
non-central backups exists
UrBackup!
-
The only way that UrBackup is non-central is that it's Non-Central to the MSP. It's "global" for the customer as it's just another managed service (be it from internal IT or an MSP such as NTG).
-
@Obsolesce said in Centrally Controlled Local Backup System Options:
I've never come across that specific need to require locally attached USB disks in with the backup solution's DB.
Doens't need to be in the DB. You can know if a backup is scheduled, happened, or was successful without sending details about it outside of the network. Doing so would be okay, but it's not needed to control the backups.
