Crashplan Pro Issue



  • @BRRABill said in Crashplan Pro Issue:

    @JaredBusch said

    While this is not an optimal situation, you should have received an email from your system informing you that it had not reached the backup target in X days.

    I did, and that is why I contacted them.

    However, that's like getting an e-mail that your house burned down. Not particularly helpful and nothing can be done about it.

    Guess you need to change that setting to every one day then.



  • @Dashrender said in Crashplan Pro Issue:

    @BRRABill said in Crashplan Pro Issue:

    @JaredBusch said

    While this is not an optimal situation, you should have received an email from your system informing you that it had not reached the backup target in X days.

    I did, and that is why I contacted them.

    However, that's like getting an e-mail that your house burned down. Not particularly helpful and nothing can be done about it.

    Guess you need to change that setting to every one day then.

    It doesn't change the point you can't do backups or restores.

    What difference does it make if I get 9 days of e-mails telling me the service is broken?



  • @BRRABill said in Crashplan Pro Issue:

    @Dashrender said in Crashplan Pro Issue:

    @BRRABill said in Crashplan Pro Issue:

    @JaredBusch said

    While this is not an optimal situation, you should have received an email from your system informing you that it had not reached the backup target in X days.

    I did, and that is why I contacted them.

    However, that's like getting an e-mail that your house burned down. Not particularly helpful and nothing can be done about it.

    Guess you need to change that setting to every one day then.

    It doesn't change the point you can't do backups or restores.

    What difference does it make if I get 9 days of e-mails telling me the service is broken?

    Because you know something failed immediately and can take action as required by how critical the information is.



  • @BRRABill said in Crashplan Pro Issue:

    @Dashrender said in Crashplan Pro Issue:

    @BRRABill said in Crashplan Pro Issue:

    @JaredBusch said

    While this is not an optimal situation, you should have received an email from your system informing you that it had not reached the backup target in X days.

    I did, and that is why I contacted them.

    However, that's like getting an e-mail that your house burned down. Not particularly helpful and nothing can be done about it.

    Guess you need to change that setting to every one day then.

    It doesn't change the point you can't do backups or restores.

    What difference does it make if I get 9 days of e-mails telling me the service is broken?

    Things break - that's fine. and while you work to repair them, you decide how else you're going to protect them, if there's an option for that.

    For example, if you were make aware 9 days ago, you could have told you users to backup daily to USB stick until the problem is resolved, or you could have moved them to another service. Instead, you're now out a restore opportunity, and still have a broken system.



  • @BRRABill said in Crashplan Pro Issue:

    @JaredBusch said

    While this is not an optimal situation, you should have received an email from your system informing you that it had not reached the backup target in X days.

    I did, and that is why I contacted them.

    However, that's like getting an e-mail that your house burned down. Not particularly helpful and nothing can be done about it.

    If you did get this, then why did you try to restore something when you knew it was not working? You make completely no sense here.

    And it is nothing like a house burning down. This is a backup failure. It affects nothing under normal circumstances. That is why it is a backup.



  • @Dashrender said in Crashplan Pro Issue:

    @BRRABill said in Crashplan Pro Issue:

    @Dashrender said in Crashplan Pro Issue:

    @BRRABill said in Crashplan Pro Issue:

    @JaredBusch said

    While this is not an optimal situation, you should have received an email from your system informing you that it had not reached the backup target in X days.

    I did, and that is why I contacted them.

    However, that's like getting an e-mail that your house burned down. Not particularly helpful and nothing can be done about it.

    Guess you need to change that setting to every one day then.

    It doesn't change the point you can't do backups or restores.

    What difference does it make if I get 9 days of e-mails telling me the service is broken?

    Things break - that's fine. and while you work to repair them, you decide how else you're going to protect them, if there's an option for that.

    For example, if you were make aware 9 days ago, you could have told you users to backup daily to USB stick until the problem is resolved, or you could have moved them to another service. Instead, you're now out a restore opportunity, and still have a broken system.

    The CrashPlan application has settings for this even in the home version. He could have easily set it to backup to a local media the first day a notice was received.



  • You two are both crazy.

    Not sure how you can defend this.

    Has nothing to do with what I could or could not have done.

    They should have alerted their customers, and to be honest this never should happen in the first place.



  • @BRRABill said in Crashplan Pro Issue:

    You two are both crazy.

    Not sure how you can defend this.

    Has nothing to do with what I could or could not have done.

    They should have alerted their customers, and to be honest this never should happen in the first place.

    I'll give you that once they made the decision to move customers to new servers, YES, they should have contacted you - but contact as soon as the failure happened, nope, can't give that to you. Because things happen, they just need to be fixed. And as JB said, this is backup, not production, but after a few day of downtime, considering the default is no notice until 9 days of failed backup - OK they should have notified you on day 3 if not day two.



  • It's not 9 days.

    I got alerts after 3 days. This is a remote user who doesn't always have his computer on. Wasn't anything way out of the norm until I noticed it a few days in a row, and decided to check in on it.

    And to be honest, it would be more an issue for restores.

    Which to be honest I am not even sure is related. But it sure makes sense.



  • @BRRABill said in Crashplan Pro Issue:

    You two are both crazy.

    Not sure how you can defend this.

    Has nothing to do with what I could or could not have done.

    They should have alerted their customers, and to be honest this never should happen in the first place.

    Whether or not they should have alerted their customers is honestly a completely separate issue. Your issue is completely dumping on them when the mitigation is still on all you for not getting handled.

    Even had it been announced, most customers would have just bitched and waited it out because they sure as fuck were not going to reseed (i suspect) terabytes of data or more, if they could even figure out how to force their data to a new server themselves in the first place.

    Should they have made some kind of notice? Yes. Does not change the prior assumption from almost certainly being a fact.

    If it was my application, I would have designed a pop up notice into it that I can trigger for such events.

    From the outside, I also wonder why data is down for such a long time, this is true. To my understanding my data is stored in some encrypted form. So, to me, that means the worst thing that should happen is that the server is dead and users are offline while their data is moved and will come back online once their blob has moved.
    Maybe they just executed an rsync and there is no prioritization. I would have done some kind of little guy to largest guy scenario in order to keep the longer impact to the smallest number of users.

    But again, all of that said, you still are bitching about not performing your own job of handling a backup failure.



  • @BRRABill said in Crashplan Pro Issue:

    It's not 9 days.

    I got alerts after 3 days. This is a remote user who doesn't always have his computer on. Wasn't anything way out of the norm until I noticed it a few days in a row, and decided to check in on it.

    And to be honest, it would be more an issue for restores.

    Which to be honest I am not even sure is related. But it sure makes sense.

    OMFG how can you even say that you are not sure a restore is related? Seriously?



  • @JaredBusch said

    But again, all of that said, you still are bitching about not performing your own job of handling a backup failure.

    It's a free world. Thanks for your opinion.



  • @JaredBusch said

    OMFG how can you even say that you are not sure a restore is related? Seriously?

    Do you know files can't be restored? Maybe there is a way to do it outside the normal ways. Who knows? I have not officially asked about that.



  • @BRRABill said in Crashplan Pro Issue:

    I got alerts after 3 days. This is a remote user who doesn't always have his computer on. Wasn't anything way out of the norm until I noticed it a few days in a row, and decided to check in on it.

    Right here you say that these backups re not important enough to care about until you got 3 failure notices.



  • @BRRABill said in Crashplan Pro Issue:

    @JaredBusch said

    OMFG how can you even say that you are not sure a restore is related? Seriously?

    Do you know files can't be restored? Maybe there is a way to do it outside the normal ways. Who knows? I have not officially asked about that.

    /blink

    Umm, if the backup repository is unavailable for backup, how in the hell would it be available for a restore?