What Are You Doing Right Now
-
@wirestyle22 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@wirestyle22 said in What Are You Doing Right Now:
@scottalanmiller Why is that?
Did you miss our thread of evaluating Zimbra vs. Kopano? Kopano went down in flames. Most clear cut product evaluation I've ever seen. I got to be the number two contributor, of all time in their community just trying to get a single useful answer from them today. We have the busiest thread that they have ever had, ever... and three more in the top ten or fifteen all time threads... all in one day. And ML had more posts about their product in one day than they've had... ever!
Yeah I haven't been able to keep up with a lot this week unfortunately. Mostly talking to people through PM's
Hope that all is well (other than the teeth!)
-
Not that I don't hope that the teeth are well...
-
Well I am happy that the Ubuntu 16.04 to 16.10 upgrade went off without a hitch.
Because I clicked checkpoint on the wrong machine.. I just went in to remove the checkpoint and there was not one there!
-
@scottalanmiller said in What Are You Doing Right Now:
Getting NethServer 7.0 RC3 uploaded so that I can start playing with it.
Scott, I was curious on how your testing with NethServer went. I have previously tested it as well and it was nice. Community was lively as well as helpful. I was curious on your impressions.
-
My Google-Fu is stronger than usual today...
-
@scottalanmiller said in What Are You Doing Right Now:
Our doctor's office just emailed us to tell us that 2+ years of medical records were lost because they weren't testing backups. They kept getting a "your backup was successful" message, but no one looked to see if that was true.
So not only did they totally lose their medical records system (um, really?) but they don't have working backups.
I'll hold my hands up on this too, we are terrible and testing.
But that's about to change as i'm reviewing our entire backup and testing procedures over the next month or two.
-
@hobbit666 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
Our doctor's office just emailed us to tell us that 2+ years of medical records were lost because they weren't testing backups. They kept getting a "your backup was successful" message, but no one looked to see if that was true.
So not only did they totally lose their medical records system (um, really?) but they don't have working backups.
I'll hold my hands up on this too, we are terrible and testing.
But that's about to change as i'm reviewing our entire backup and testing procedures over the next month or two.
We check all customers backups every week, and the majority get a test restore done at least once a month too, just to be on the safe side - so might be worth doing test restores as well - no good making sure the backup works if you're unable to restore the data if it does die!
-
@vhinzsanchez said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
Getting NethServer 7.0 RC3 uploaded so that I can start playing with it.
Scott, I was curious on how your testing with NethServer went. I have previously tested it as well and it was nice. Community was lively as well as helpful. I was curious on your impressions.
Got caught up in other projects, it's still sitting waiting for me
-
Back in the server room cleaning and sorting for a few hours
-
Grocery shopping.
-
Trying to figure out why one of our customers servers just turned itself off.
-
@NattNatt said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
Our doctor's office just emailed us to tell us that 2+ years of medical records were lost because they weren't testing backups. They kept getting a "your backup was successful" message, but no one looked to see if that was true.
So not only did they totally lose their medical records system (um, really?) but they don't have working backups.
I'll hold my hands up on this too, we are terrible and testing.
But that's about to change as i'm reviewing our entire backup and testing procedures over the next month or two.
We check all customers backups every week, and the majority get a test restore done at least once a month too, just to be on the safe side - so might be worth doing test restores as well - no good making sure the backup works if you're unable to restore the data if it does die!
If by checking you mean looking at the logs.... That's not really checking. A restore is the only real check. Of course having logs that day the backups were successful is a good first step.
-
@Dashrender said in What Are You Doing Right Now:
@NattNatt said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
Our doctor's office just emailed us to tell us that 2+ years of medical records were lost because they weren't testing backups. They kept getting a "your backup was successful" message, but no one looked to see if that was true.
So not only did they totally lose their medical records system (um, really?) but they don't have working backups.
I'll hold my hands up on this too, we are terrible and testing.
But that's about to change as i'm reviewing our entire backup and testing procedures over the next month or two.
We check all customers backups every week, and the majority get a test restore done at least once a month too, just to be on the safe side - so might be worth doing test restores as well - no good making sure the backup works if you're unable to restore the data if it does die!
If by checking you mean looking at the logs.... That's not really checking. A restore is the only real check. Of course having logs that day the backups were successful is a good first step.
Full logs checked every week, and any warnings/errors raised to be fixed
-
@NattNatt said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@NattNatt said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
Our doctor's office just emailed us to tell us that 2+ years of medical records were lost because they weren't testing backups. They kept getting a "your backup was successful" message, but no one looked to see if that was true.
So not only did they totally lose their medical records system (um, really?) but they don't have working backups.
I'll hold my hands up on this too, we are terrible and testing.
But that's about to change as i'm reviewing our entire backup and testing procedures over the next month or two.
We check all customers backups every week, and the majority get a test restore done at least once a month too, just to be on the safe side - so might be worth doing test restores as well - no good making sure the backup works if you're unable to restore the data if it does die!
If by checking you mean looking at the logs.... That's not really checking. A restore is the only real check. Of course having logs that day the backups were successful is a good first step.
Full logs checked every week, and any warnings/errors raised to be fixed
Checking means actually doing a restore. The doctors office that just lost everything has clear logs, too.
-
-
Yup. That's the real name of the rice here.
-
@scottalanmiller said in What Are You Doing Right Now:
@NattNatt said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@NattNatt said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
Our doctor's office just emailed us to tell us that 2+ years of medical records were lost because they weren't testing backups. They kept getting a "your backup was successful" message, but no one looked to see if that was true.
So not only did they totally lose their medical records system (um, really?) but they don't have working backups.
I'll hold my hands up on this too, we are terrible and testing.
But that's about to change as i'm reviewing our entire backup and testing procedures over the next month or two.
We check all customers backups every week, and the majority get a test restore done at least once a month too, just to be on the safe side - so might be worth doing test restores as well - no good making sure the backup works if you're unable to restore the data if it does die!
If by checking you mean looking at the logs.... That's not really checking. A restore is the only real check. Of course having logs that day the backups were successful is a good first step.
Full logs checked every week, and any warnings/errors raised to be fixed
Checking means actually doing a restore. The doctors office that just lost everything has clear logs, too.
Fair enough, that's once a month then!
-
@NattNatt said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@NattNatt said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@NattNatt said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
Our doctor's office just emailed us to tell us that 2+ years of medical records were lost because they weren't testing backups. They kept getting a "your backup was successful" message, but no one looked to see if that was true.
So not only did they totally lose their medical records system (um, really?) but they don't have working backups.
I'll hold my hands up on this too, we are terrible and testing.
But that's about to change as i'm reviewing our entire backup and testing procedures over the next month or two.
We check all customers backups every week, and the majority get a test restore done at least once a month too, just to be on the safe side - so might be worth doing test restores as well - no good making sure the backup works if you're unable to restore the data if it does die!
If by checking you mean looking at the logs.... That's not really checking. A restore is the only real check. Of course having logs that day the backups were successful is a good first step.
Full logs checked every week, and any warnings/errors raised to be fixed
Checking means actually doing a restore. The doctors office that just lost everything has clear logs, too.
Fair enough, that's once a month then!
yeah, What Scott said is what I was going for.
The reality is that Scott's doctor's office probably never did a test restore, even one would have shown the issue most likely.
-
@Dashrender said in What Are You Doing Right Now:
@NattNatt said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@NattNatt said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@NattNatt said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
Our doctor's office just emailed us to tell us that 2+ years of medical records were lost because they weren't testing backups. They kept getting a "your backup was successful" message, but no one looked to see if that was true.
So not only did they totally lose their medical records system (um, really?) but they don't have working backups.
I'll hold my hands up on this too, we are terrible and testing.
But that's about to change as i'm reviewing our entire backup and testing procedures over the next month or two.
We check all customers backups every week, and the majority get a test restore done at least once a month too, just to be on the safe side - so might be worth doing test restores as well - no good making sure the backup works if you're unable to restore the data if it does die!
If by checking you mean looking at the logs.... That's not really checking. A restore is the only real check. Of course having logs that day the backups were successful is a good first step.
Full logs checked every week, and any warnings/errors raised to be fixed
Checking means actually doing a restore. The doctors office that just lost everything has clear logs, too.
Fair enough, that's once a month then!
yeah, What Scott said is what I was going for.
The reality is that Scott's doctor's office probably never did a test restore, even one would have shown the issue most likely.
They did not, no one did. They just checked the logs, saw no errors and assumed that it would work.
-
How do yall feel about Veeam B&R's SureBackup? Is that as reliable as checking the backups themselves or do you actually check for VM functionality in an isolated environment?
