Schlepping back to the data center, and I want to hear war stories! What's the biggest amount of data you ever had to move, and how did you move it? I physically drive a 37TB backup drive to datacenters but I am a minnow in this particular ocean of suffering. Tell me things!
-
Show this thread
-
Replying to @Pinboard
It wasn't much data but it was ~1985: a client had a custom-built miniframe (It was wire-wrapped, had "Custom built for $COMPANY by My Lee(?)" engraved on the front) with their inventory, and of course nothing about its hardware was standard... except the parallel port. I...
1 reply 1 retweet 6 likes -
Replying to @CakeRavens @Pinboard
worked for an MAI Basic/Four dealer (don't judge!) and we'd sold them a machine which had serial WYSE terminals. I figured out how to get my Tandy M100 to talk to it as a terminal, and to listen to the old computer's parallel port, and dumped a full inventory report to it.
1 reply 0 retweets 0 likes -
Replying to @CakeRavens @Pinboard
I don't remember how many hours it took, but the two machines were on opposite sides of a pass-through computer room (retrofit) in the middle of the office building, and the M100 was basically suspended in between. People had to duck under the cables all day.
1 reply 1 retweet 1 like -
Replying to @CakeRavens @Pinboard
Couldn't have been too much data, because we later upgraded that machine with a 5MB (IIRC) disk pack. Bought a "refurbished" drive that something had clearly died in. On the advice of our Sorbus guy, I bought a box of dryer sheets, opened the lid and tossed one in (sans pack).
1 reply 1 retweet 1 like -
Replying to @CakeRavens @Pinboard
One of the office people saw it, and I cheerfully said "I'm doing a load of whites, if you have anything that needs to go in" because I wasn't gonna let that opportunity pass me up.
1 reply 1 retweet 10 likes -
-
Replying to @Pinboard
Pretty much the highlight of my entire IT career (I peaked early).
1 reply 0 retweets 0 likes
Hey, not all of us get a highlight!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.