I wish I wouldn't have clicked that button...
-
I was attempting to get familiar with our file restoration software when I initiated a complete restoration of the department wide share drive. :omg: My intent was to restore a test directory that I'd deleted - instead of that I kicked off a restore of everything. The first hint that something was wrong was when after 1 minute the process was at 5%. I figured a single small directory should take seconds - I killed the job. I then had to send out the department wide email confession my goof encouraging people to check and make sure they didn't loose data. No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again. The good news is that a review of the logs this morning shows that no files were actually impacted - the job was still initializing when it was canceled. Whew.
-
I was attempting to get familiar with our file restoration software when I initiated a complete restoration of the department wide share drive. :omg: My intent was to restore a test directory that I'd deleted - instead of that I kicked off a restore of everything. The first hint that something was wrong was when after 1 minute the process was at 5%. I figured a single small directory should take seconds - I killed the job. I then had to send out the department wide email confession my goof encouraging people to check and make sure they didn't loose data. No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again. The good news is that a review of the logs this morning shows that no files were actually impacted - the job was still initializing when it was canceled. Whew.
For the full effect, start the test restore on a Friday lunchtime, and then knock off for a long weekend! :laugh: Remember to remove the battery from your cellphone... [edit] typos - tablet autocorrect... :sigh: [/edit]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
I was attempting to get familiar with our file restoration software when I initiated a complete restoration of the department wide share drive. :omg: My intent was to restore a test directory that I'd deleted - instead of that I kicked off a restore of everything. The first hint that something was wrong was when after 1 minute the process was at 5%. I figured a single small directory should take seconds - I killed the job. I then had to send out the department wide email confession my goof encouraging people to check and make sure they didn't loose data. No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again. The good news is that a review of the logs this morning shows that no files were actually impacted - the job was still initializing when it was canceled. Whew.
Be glad it did not delete all files before the restore. :)
-
For the full effect, start the test restore on a Friday lunchtime, and then knock off for a long weekend! :laugh: Remember to remove the battery from your cellphone... [edit] typos - tablet autocorrect... :sigh: [/edit]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
I was attempting to get familiar with our file restoration software when I initiated a complete restoration of the department wide share drive. :omg: My intent was to restore a test directory that I'd deleted - instead of that I kicked off a restore of everything. The first hint that something was wrong was when after 1 minute the process was at 5%. I figured a single small directory should take seconds - I killed the job. I then had to send out the department wide email confession my goof encouraging people to check and make sure they didn't loose data. No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again. The good news is that a review of the logs this morning shows that no files were actually impacted - the job was still initializing when it was canceled. Whew.
Quote:
The good news is that a review of the logs this morning shows that no files were actually impacted - the job was still initializing when it was canceled.
If only you had noticed that BEFORE sending out the company wide email announcing the oops... :sigh:
"Religion is the most malevolent of all mind viruses." - Arthur C. Clarke
-
Be glad it did not delete all files before the restore. :)
-
Quote:
The good news is that a review of the logs this morning shows that no files were actually impacted - the job was still initializing when it was canceled.
If only you had noticed that BEFORE sending out the company wide email announcing the oops... :sigh:
"Religion is the most malevolent of all mind viruses." - Arthur C. Clarke
-
I was attempting to get familiar with our file restoration software when I initiated a complete restoration of the department wide share drive. :omg: My intent was to restore a test directory that I'd deleted - instead of that I kicked off a restore of everything. The first hint that something was wrong was when after 1 minute the process was at 5%. I figured a single small directory should take seconds - I killed the job. I then had to send out the department wide email confession my goof encouraging people to check and make sure they didn't loose data. No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again. The good news is that a review of the logs this morning shows that no files were actually impacted - the job was still initializing when it was canceled. Whew.
-
Every once and awhile I get the impression, indistinct and faint as it may be, that you don't have my best interests at heart.
No, no - it's a learning experience. You'd even look back on it and laugh, a few years later. :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
I was attempting to get familiar with our file restoration software when I initiated a complete restoration of the department wide share drive. :omg: My intent was to restore a test directory that I'd deleted - instead of that I kicked off a restore of everything. The first hint that something was wrong was when after 1 minute the process was at 5%. I figured a single small directory should take seconds - I killed the job. I then had to send out the department wide email confession my goof encouraging people to check and make sure they didn't loose data. No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again. The good news is that a review of the logs this morning shows that no files were actually impacted - the job was still initializing when it was canceled. Whew.
-
I was attempting to get familiar with our file restoration software when I initiated a complete restoration of the department wide share drive. :omg: My intent was to restore a test directory that I'd deleted - instead of that I kicked off a restore of everything. The first hint that something was wrong was when after 1 minute the process was at 5%. I figured a single small directory should take seconds - I killed the job. I then had to send out the department wide email confession my goof encouraging people to check and make sure they didn't loose data. No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again. The good news is that a review of the logs this morning shows that no files were actually impacted - the job was still initializing when it was canceled. Whew.
:) From it I learned to check this:
MehGerbil wrote:
The good news is that a review of the logs this morning shows that no files were actually impacted
Before to do:
MehGerbil wrote:
I then had to send out the department wide email confession
The Jurassic period produced such an abundance of lethal predators, that the oceans were a virtual STEW OF ASSASSINS - The history channel
-
For the full effect, start the test restore on a Friday lunchtime, and then knock off for a long weekend! :laugh: Remember to remove the battery from your cellphone... [edit] typos - tablet autocorrect... :sigh: [/edit]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
OriginalGriff wrote:
remove the battery from your cellphone.
Two of the best pieces of advice -- especially the latter -- of the whole year. :D Way to think outside the box. This little button he clicked is like an extra day off every week. :)
-
I was attempting to get familiar with our file restoration software when I initiated a complete restoration of the department wide share drive. :omg: My intent was to restore a test directory that I'd deleted - instead of that I kicked off a restore of everything. The first hint that something was wrong was when after 1 minute the process was at 5%. I figured a single small directory should take seconds - I killed the job. I then had to send out the department wide email confession my goof encouraging people to check and make sure they didn't loose data. No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again. The good news is that a review of the logs this morning shows that no files were actually impacted - the job was still initializing when it was canceled. Whew.
MehGerbil wrote:
No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again
Response: I was unable to test the file restoration software because we lack a test system. We should have, as a minimum, a test system that mirrors production. That way, we can test in a sterile environment and ensure we don't have this happen again.
-
MehGerbil wrote:
No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again
Response: I was unable to test the file restoration software because we lack a test system. We should have, as a minimum, a test system that mirrors production. That way, we can test in a sterile environment and ensure we don't have this happen again.
-
Basically, you just asked for more funding without mentioning money. *blink* May I come and work for you?
If management neglected to PROVIDE a test environment, then it reflects poorly on their PLANNING. So, as much as you were the land on the lever, so to speak, it was their responsibility to ensure what happened couldn't happen.
-
I was attempting to get familiar with our file restoration software when I initiated a complete restoration of the department wide share drive. :omg: My intent was to restore a test directory that I'd deleted - instead of that I kicked off a restore of everything. The first hint that something was wrong was when after 1 minute the process was at 5%. I figured a single small directory should take seconds - I killed the job. I then had to send out the department wide email confession my goof encouraging people to check and make sure they didn't loose data. No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again. The good news is that a review of the logs this morning shows that no files were actually impacted - the job was still initializing when it was canceled. Whew.
buttons and "getting to know you", don't mix.
-
If management neglected to PROVIDE a test environment, then it reflects poorly on their PLANNING. So, as much as you were the land on the lever, so to speak, it was their responsibility to ensure what happened couldn't happen.
-
MehGerbil wrote:
No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again
Response: I was unable to test the file restoration software because we lack a test system. We should have, as a minimum, a test system that mirrors production. That way, we can test in a sterile environment and ensure we don't have this happen again.
-
Married... happily. Just been in the trenches for almost 3 decades; learn a few things along the way.
-
I was attempting to get familiar with our file restoration software when I initiated a complete restoration of the department wide share drive. :omg: My intent was to restore a test directory that I'd deleted - instead of that I kicked off a restore of everything. The first hint that something was wrong was when after 1 minute the process was at 5%. I figured a single small directory should take seconds - I killed the job. I then had to send out the department wide email confession my goof encouraging people to check and make sure they didn't loose data. No better way to start a Tuesday morning than a note from the director asking for ideas on how to make sure this never happens again. The good news is that a review of the logs this morning shows that no files were actually impacted - the job was still initializing when it was canceled. Whew.
Very similar thing happened in my previous company. We had RAD-5 ( or whatever that's called) set, but nobody tested whether backup is really happening. So, one fine morning, the main hard disk gone and in haste, network admin fired restore ! No prize for guessing the all files / mails were now 6 months older. Time-Travel you know !! And the best thing, later we learnt the disk wasn't gone, it was just playing up and the restore overwritten it..! :doh: Luckily that I was on leave, so my files/outlook mails survived !
Thanks, Milind
