BackBlaze - Business Options Available
-
With any solution like this, you can backup anything you want, you just have to use a linked folder. I have no idea why this is not better known in the Windows world, but it has existed for a long time.
I backup my NAS at home with my CrashPlan account ($60/year) this way.
For one client with a small Veeam repository, I backup their entire local repository (a NAS) with CrashPlan Pro ($10/month) I simply have a linked folder sitting there.
mklink /J C:\Veeam \\nas\VeeamThen you point CrashPlan at C:\Veeam
I began abusing this years and years ago to get around DropBox issues.
-
I think that linked folders are not just poorly known as a workaround to this specific issue but are, in general, not well known. I never see people talking about them or using them.
-
Of course this opens you to a cryptolocker problem.
-
Your NAS would be open to that by the nature of being able to be linked in this way.
-
@scottalanmiller said:
Your NAS would be open to that by the nature of being able to be linked in this way.
Yeah I suppose so.
Best to have a dedicated account on that share that has write ability and don't log in anywhere I possible as that user...
The backup software runs as that user... The link could be setup with a read only account.
-
Crypto is not a problem. you simply restore a prior version.
-
We use Backblaze for Business and have for a couple of years now (the domain license that Aaron mentions). I had been using it at home on my wife's computer (2 internal drives and an external HD backed up for $50 per year) when I found out they had a business option. We have around 30 pcs in the account now, mostly C-level and outside sales computers on which you are most likely going to find local files of a very important nature. It definitely works really well, and I do like the alerts for when machines have not backed up in X number of days. You get a weekly alert for all computers in the account telling you the last backup of each machine, how much data may be left to backup based on change rates, etc.
The web portal for restores is easy to use. The only thing missing from Backblaze in my opinion is the ability to store file revisions as well as Crashplan does (allowing specific retention period for revisions to be backed up). That is why I like Crashplan better for some use cases (i.e. backing up the server with all of our enterprise software). I must say Backblaze has worked very well for us thus far based on our use case.
I am definitely curious about B2 like others here.
-
@JaredBusch said:
Crypto is not a problem. you simply restore a prior version.
Sure you can restore the files, But that mean waiting for the Veeam Zip backup to come back to the local network before performing other restores from that specific file.
-
@Dashrender said:
@JaredBusch said:
Crypto is not a problem. you simply restore a prior version.
Sure you can restore the files, But that mean waiting for the Veeam Zip backup to come back to the local network before performing other restores from that specific file.
And so?
The entire point of this thread is an offsite backup a solution. You will always be waiting if you need to resort to it for restoral. This is not a thread about general backup or what is best for crypto recovery.
Offsite backup should never replace onsite.
-
@JaredBusch said:
@Dashrender said:
@JaredBusch said:
Crypto is not a problem. you simply restore a prior version.
Sure you can restore the files, But that mean waiting for the Veeam Zip backup to come back to the local network before performing other restores from that specific file.
And so?
The entire point of this thread is an offsite backup a solution. You will always be waiting if you need to resort to it for restoral. This is not a thread about general backup or what is best for crypto recovery.
Offsite backup should never replace onsite.
You're right, it's not about general backup or crypto recovery, but I think crypto recovery should be part of the consideration. Because of the SMB/NFS type sharing crypto badness makes it more likely you'll have to resort to your offsite backups versus other options you could implement.
Isn't it equally important to setup your environment to use the quickest backup available assuming that doing so doesn't drive the price over the edge, etc?
-
@NetworkNerd said:
The web portal for restores is easy to use. The only thing missing from Backblaze in my opinion is the ability to store file revisions as well as Crashplan does (allowing specific retention period for revisions to be backed up). That is why I like Crashplan better for some use cases (i.e. backing up the server with all of our enterprise software). I must say Backblaze has worked very well for us thus far based on our use case.
Can you explain this a little more? About the revisions?
-
@NetworkNerd said:
We have around 30 pcs in the account now, mostly C-level and outside sales computers on which you are most likely going to find local files of a very important nature.
See @scottalanmiller, it;s not just me.
-
@aaron said:
(Win -- not server OS -- & Mac)
How does it back up servers?
-
This post is deleted! -
@aaron said:
The Backblaze backup client for personal backup and business is not meant to backup servers, it's targeted for individual computers.
Is it allowed to backup servers?
We used to do a regular backup, but also had CrashPlan running on the servers. For $10 a month it was a nice way to do versioning offsite.
-
This post is deleted! -
@aaron said:
@BRRABill No it will not install on a server OS.
I am curious as to why not... ? Some of us prefer to use Server OSes as our daily drivers. Why treat the server OS any differently than the client OS?
-
@dafyre said:
@aaron said:
@BRRABill No it will not install on a server OS.
I am curious as to why not... ? Some of us prefer to use Server OSes as our daily drivers. Why treat the server OS any differently than the client OS?
To prevent abuse. Though it's a poor man's way of doing so.
-
-
@Dashrender said:
@dafyre said:
@aaron said:
@BRRABill No it will not install on a server OS.
I am curious as to why not... ? Some of us prefer to use Server OSes as our daily drivers. Why treat the server OS any differently than the client OS?
To prevent abuse. Though it's a poor man's way of doing so.
Yup, no effective way to use a desktop for huge storage or many systems.
