So yesterday at 17:00 I noticed the DVR guy was examining the cameras we set up for testing purposes outside.
So I stopped and chatted to him. Apparently he was removing one of the cameras as he was going to site the next day and needed it to install on site.
Then he asked me for a network cable. I tole him my PFY is most probably inside and may or may not help him. Then I left for sweet $home (and got caught up in a charlie foxtrot of a traffic jam).
Next day I heard he asked for a network cable but nobody was able to help him. Boo hoo.
Bad planning on his part. Had he informed us that he need to do an install early enough, we would’ve made a plan.
I think I’ve finally realised that my boss doesn’t seem to know what is going on. There is another developer in our team. His installation of visual studio is fried. So instead of fixing it he’s rdp’ed onto the dev SQL box and installed Vs there. Whatever he’s working on sent the server into meltdown and it needed to be stopped before we could do any work. The last time was the debug process from his program.
Enter bossman.
Me: Server went down Dev processes went haywire.
Boss: maybe we need to look at alternative environments for developing.
Me: told boss that the correct environments for developing code are our own PCs!!! Otherwise this stuff happens!
‘The time has come,’ the Walrus said,
To talk of many things:
Of shoes — and ships — and sealing-wax —
Of cabbages — and kings —
And why the sea is boiling hot —
And whether pigs have wings.’
And to resuscitate this thread.
Why do companies love to assign exiting (either resigning or getting fired) personnel’s tasks onto an existing employee, and never employ a new employee? Do they do this just to “save money”?
Want me to clone a server’s boot drive over to a bigger volume?
Sure can do… hollow laugh
Going to see if we can get an experienced company to do this rather, cloning and upgrading an old server is a very iffy affair, given that it runs windows 7…
In my job anything that is out of Microsoft support is best effort only - and in that case, it’d be "ok we’ll take a backup before doing this but if it goes pear-shaped you’re on your own (after restoring from said backup).
Somebody else will do it - seeing that the primary partition is RAID0 over two HDD’s…
If it was a RAID1/RAID5 setup, no sweat.
Had a RAID0 shit the bed with me once. Luckily I could get the middle HDD (there were three) up and running so that I could copy the most critical data off.
Long ago, we had a server with a RAID5 array in it. We had a second disk fail whilst rebuilding after replacing the first failed disk.
Idiot mangler kept saying “That can’t happen…” as he didn’t understand probability and disks from the same batch (we checked) were more likely to fail at the same time.
I won’t go into how the Solstice DiskSuite had been setup - let’s just say that it should not have worked. At all. Yet it did, and had been running for several years..
