CrashPlan - Bug?
-
@aaronstuder said in CrashPlan - Bug?:
Screenshot?
I had uninstalled everything. I'm setting it up again and will generate some shortly.
-
This post is deleted! -
-
See how the source starts disappearing? Users have to manually purge that list.
-
I've seen that and find it annoying, but if I am restoring often enough to make that a big issue, then something else is wrong.
definitely needs fixed though. just a UI bug to not have a scroll bar there.
-
@JaredBusch said in CrashPlan - Bug?:
I've seen that and find it annoying, but if I am restoring often enough to make that a big issue, then something else is wrong.
definitely needs fixed though. just a UI bug to not have a scroll bar there.
I just heard back from CrashPlan. They said "just tell your users to select the X on each line". Nice work around there.
Users would unlikely restore that much, it's just weird little things like that. Another thing I noticed during testing... If you Create a file called Test. In that file you write "This is old." and back it up. Then delete that file and create a new file called Test and put in data that says "This is new." Restore the old file and choose "rename", renames the new file to original1.test ... That's funny because it's not the original, it's the newer version. Why wouldn't you just give control to the user about the naming convention? On-premises solutions over control over the naming. Just little things like that made me shy away.
Both BackBlaze and iDrive take hours to index and make available the data eligible for restore. I didn't think that would be a huge problem, but the CEO immediately shot down anything with that kind of latency.
Looking at a staggered Time Machine (locally attached and a Mini on the network). Also looking at OSX Server & Xsan. Why does this have to be so complicated? All I want is an off-site method that allows for immediate availability of data from an Apple computer, and not to cost a ton of money since there are only a dozen computers that execs have.
-
@BBigford said in CrashPlan - Bug?:
Both BackBlaze and iDrive take hours to index and make available the data eligible for restore. I didn't think that would be a huge problem, but the CEO immediately shot down anything with that kind of latency.
I will point out again what others have pointed out. This should never matter. If you are looking for such fast restore, then you should be looking local.
You should not expect that kind of immediate restore availability on offsite.
You have built up the wrong expectations.
-
Does it take that long to index once everything has been done the first time?
I haven't used CP in a while myself (have no local data on my machine anymore, a new ML test) but I seemed to remember files being available pretty quickly.
-
@JaredBusch said
I will point out again what others have pointed out. This should never matter. If you are looking for such fast restore, then you should be looking local.
And with CrashPlan you do always have the option of backing up locally as well as the cloud.
Though that doesn't help if they are on the road.
-
@JaredBusch said in CrashPlan - Bug?:
@BBigford said in CrashPlan - Bug?:
Both BackBlaze and iDrive take hours to index and make available the data eligible for restore. I didn't think that would be a huge problem, but the CEO immediately shot down anything with that kind of latency.
I will point out again what others have pointed out. This should never matter. If you are looking for such fast restore, then you should be looking local.
You should not expect that kind of immediate restore availability on offsite.
You have built up the wrong expectations.
Possibly, but some of these solutions offer up a hybrid of on-site/off-site such as setting up a CrashPlan central storage within your network.
Nonetheless, maybe I'm expecting too much.
-
@BRRABill said in CrashPlan - Bug?:
Does it take that long to index once everything has been done the first time?
I haven't used CP in a while myself (have no local data on my machine anymore, a new ML test) but I seemed to remember files being available pretty quickly.
CP offers instant recovery points. It's other companies like BackBlaze & iDrive that take most of the work day to become available. It's because of CP's nearly instant access that make me feel like my expectation of quick access is not completely far-fetched. There were just a couple UI bugs that users would call constantly about, that we couldn't look past.
-
@BBigford said
CP offers instant recovery points. It's other companies like BackBlaze & iDrive that take most of the work day to become available. It's because of CP's nearly instant access that make me feel like my expectation of quick access is not completely far-fetched. There were just a couple UI bugs that users would call constantly about, that we couldn't look past.
Like the one above?
One question I had is: how often would they be restoring that many files all over the place?
Usually it is just a file or two, or a folder.
-
@BRRABill said in CrashPlan - Bug?:
@BBigford said
CP offers instant recovery points. It's other companies like BackBlaze & iDrive that take most of the work day to become available. It's because of CP's nearly instant access that make me feel like my expectation of quick access is not completely far-fetched. There were just a couple UI bugs that users would call constantly about, that we couldn't look past.
Like the one above?
One question I had is: how often would they be restoring that many files all over the place?
Usually it is just a file or two, or a folder.
Each line, is a single restore. Whether that is a file, folder, etc. 13 restores... could be a month, could be a year, but I know I would start getting calls that people can't see the source points since they've exceeded 13. Then more time would pass and I'd receive calls again. Just trying to mitigate some of the more menial tickets.
-
@BRRABill said in CrashPlan - Bug?:
@BBigford said
CP offers instant recovery points. It's other companies like BackBlaze & iDrive that take most of the work day to become available. It's because of CP's nearly instant access that make me feel like my expectation of quick access is not completely far-fetched. There were just a couple UI bugs that users would call constantly about, that we couldn't look past.
Like the one above?
One question I had is: how often would they be restoring that many files all over the place?
Usually it is just a file or two, or a folder.
Yeah the pics from above are taken of the local CP Pro console on a MacBook Pro. I was saving folders/files and restoring right away to overload the UI.
-
@BBigford said
Each line, is a single restore. Whether that is a file, folder, etc. 13 restores... could be a month, could be a year, but I know I would start getting calls that people can't see the source points since they've exceeded 13. Then more time would pass and I'd receive calls again. Just trying to mitigate some of the more menial tickets.
I have 5 users using CP, and we've never had one restore. I've been lucky.
Also if you are using PRO you can do the restores for them.
Just something to think about.
I wonder if you could delete the restore.log and make that go away? Does it stay on each reboot?
-
@BRRABill said in CrashPlan - Bug?:
@BBigford said
Each line, is a single restore. Whether that is a file, folder, etc. 13 restores... could be a month, could be a year, but I know I would start getting calls that people can't see the source points since they've exceeded 13. Then more time would pass and I'd receive calls again. Just trying to mitigate some of the more menial tickets.
I have 5 users using CP, and we've never had one restore. I've been lucky.
Also if you are using PRO you can do the restores for them.
Just something to think about.
I wonder if you could delete the restore.log and make that go away? Does it stay on each reboot?
It stays with each reboot. You'd have to clear out the CP cache, which is the same as manually purging each line. It's not a huge deal, it's just something I'm shocked CP didn't correct since it's something stupidly small.
-
I'm still waiting for my first CP upload to finish. 73 days.
-
@johnhooks said in CrashPlan - Bug?:
I'm still waiting for my first CP upload to finish. 73 days.
I have approximately 1.5 TB on crash plan and it only took like 10 15 days to upload on my home cable connection
-
@BBigford said in CrashPlan - Bug?:
., but the CEO immediately shot down anything with that kind of latency.
Why is this the CEO decision? He shouldn't even be in involved. That should be the IT Director and CIO.
-
@JaredBusch said in CrashPlan - Bug?:
@johnhooks said in CrashPlan - Bug?:
I'm still waiting for my first CP upload to finish. 73 days.
I have approximately 1.5 TB on crash plan and it only took like 10 15 days to upload on my home cable connection
I had my laptop's backups in there. It was only around 200GB, but the backup I use (backintime) uses hard links and I think it was screwing with CrashPlan. It said I had something around 6TB to back up. I removed that folder and it went down to 1.6TB.
Once the other stuff is initially uploaded I'll add the laptop backup in and see if it really takes forever (it shouldn't because the hard links don't take up any space). I think it just screwed with the way it calculates everything.
