uunix wrote:
Bit of porn.. bit of horror channel.. bit of moving 20 PC's to the new domain at work... APART FROM ONE!! ONE CLUSTER FSCK !! One cluster fsck who after multiple emails attaining to the said domain transfer to NOT turn their computer off on Friday the 13ths May.. TURNED HIS OFF!!! It would be nice that I had set up each PC to wake on lan.. but I never, and I have to go in tomorrow! MY fault for not thinking about people not doing as they are told.
Well, for this, he will at least suffer from remote shut downs at the worst time and I might even delete the occasional important file! (of cause I'd copy it to some location first and claim I saved his life... ) this from a guy that gave me 6.5 out of ten for a perfect cuppa just because the cup wasn't to the brim!.. GRRRRRR!!!
I found a few weeks back that you can never, ever trust people at work when it comes to simple matters like these.
We've been migrating from an ancient file server to a new storage solution recently. As the old server was severely ancient, very slow, and had 9TB on it, we decided to perform the migration in stages. We did a test migration first of everything and ran tests with some of the key users to ensure it worked, then we re-synced several folders and sent out a communication across the business clearly detailing that the migration was happening in stages, and listing a limited number of shares which had been moved.
So far, so good, and no complaints when we turned off the first batch of old shares. The following week, we migrated the second pile of folders across and sent the second communication out. Then, we received a worried e-mail from a user "a load of my files have disappeared". Turns out he ignored the part of out communication saying "this is a phased transition across several weeks", never bothered to check and see which shares had been migrated, and instead had decided to re-map *all* of his shares to the new server (the new server uses a root share with permissions to manage access to sub-folders, and his share had some permissions left over from the earlier testing phase).
Hence, when we'd re-synced the next batch of folders prior to the second stage of migrations, this had nuked all the stuff he'd been working on for the past week and was saving to the wrong place. Cue lots of scrabbling around with backups, lots of wasted time, and stern words from our regional IT leader to the guy about the importance of not making blind assumptions when it comes to company data.