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.
-
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.
-
@Jason said in CrashPlan - Bug?:
@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.
Apparently the CEO thinks that his value as a CEO isn't time well spent and that his desktop support skills are where his value to the company is.
-
@Jason said in CrashPlan - Bug?:
@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.
We restructured. IT was reporting to Engineering Manager > IT Director > VP of Operations > CEO (who writes off all big stuff). Took forever for approvals to do anything. EM quit after 10 years so we reported to the VP of Ops for 2 weeks. Then we're told IT is a corporate function, not Engineering/Ops, so started reporting to the CEO for everything. Approvals that took years just to get shot down because of the chain, started getting approved in minutes. We can now use a ton of hosted services we were told go against contracts. All in all, I'm totally cool with the transition even if some of the smaller, stupid stuff gets dragged along.
-
@BBigford said in CrashPlan - Bug?:
@Jason said in CrashPlan - Bug?:
@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.
We restructured. IT was reporting to Engineering Manager > IT Director > VP of Operations > CEO (who writes off all big stuff). Took forever for approvals to do anything. EM quit after 10 years so we reported to the VP of Ops for 2 weeks. Then we're told IT is a corporate function, not Engineering/Ops, so started reporting to the CEO for everything. Approvals that took years just to get shot down because of the chain, started getting approved in minutes. We can now use a ton of hosted services we were told go against contracts. All in all, I'm totally cool with the transition even if some of the smaller, stupid stuff gets dragged along.
So they decided that things were bad and .... did this as the fix? Sounds like a problem from the top. Even with the new structure, this makes zero sense. The CEO is still getting involved where no manager should be. Sounds like the CEO is likely the root cause here.
