Re: "bursty traffic"
Ah, yes the Slashdot effect, when a story links to a resource not equipped to handle incoming tsunami of clicks. Kind of a poor man’s DoS…
6665 publicly visible posts • joined 10 May 2010
Why can’t you be the guy that interviews me? :-)
I’ve been interviewing for some time, had many phone interviews by non technical hiring staff who had no idea what the questions they asked meant. No I don’t know O365, but I’ve used enough directory/account applications like AD,OD, GSuite etc. that it won’t take very long to pick it up…
I once supported* POS devices that did exactly that, when connection to the mothership was lost, it began buffering, but there was a limit as I recall. I'm so glad those days are behind me.
*Went as far as unplugging the offending USB peripheral and plugging it back in again. Rebooting the underlying Windows, or reading the error code over the phone to the helpdesk.
Back when I was an MCSA candidate(easy route) I was entrusted with a cluster of windows servers running Exchange and File services, one day the cluster had lost some luster, and my boss said move file service to the other node and we'll reboot it... I failed over (love that term! Failover) the files to the other node (I'd done it dozens of times, a no brainer really), and it didn't do much of anything except render any file services limper than a whisky dick... The phone rang, it was the finance director, I looked at my boss and said it's for you!
Long ago when only desktops roamed the earth, I worked at a place where My Documents was redirected to be the p:\ on the server.... No one was supposed to save anything locally, it was NOT backed up! Our thinking was: we're not backing up 300 desktops, when we can back up a couple of servers. Any issues on the desktop was a nuke a pave, pull your profile down from the server and move on. We had one new employee, stored all his work in a folder on his desktop. We saw this and pointed out our set up, and told him any local data was not backed up, and we're not responsible for it... You guessed it boys and girls, his pc needed a nuke and pave, and all his work was on that desktop... I was in a meeting about his disaster, long enough to confirm that I had done my part telling him NOT to save locally. I was excused and never heard another peep about it.