Speaking of power related file write and failing hardware issues, I am curious about something. How many folks have clients that refuse to use decent UPS units (with the data cable to allow for a clean shutdown with a power loss event)? And of those clients that do get UPS units, how many of them bother to replace their UPS batteries every 2 years or so?
I have been strongly suggesting UPS units to my clients for several years, and try to get them to replace their UPS batteries about every 2 years. Those that have listened have the very fewest issues. Those that don't listen do not seem to have a lot of ongoing power related computer problems with programs being run. But with the storms we get, and errant power at times, they do get PCs zapped every once in a while. Recently one client lost 6 PCs in 2 days with an overnight thunderstorm! Now he is putting in UPS units, but only for the Mission Critical PCs. Better than nothing I guess. It also seems those clients that do listen about UPS units also listen about putting a good file/disk backup plan in place. It is almost as though one has to experience a loss of equipment or data before they believe they need to be protected. Years ago I recall Ed quipping at me, "There are two kinds of computer users. Those that have lost data, and those that will." Truer words are rarely spoken... I "forced" an associate in Seattle to let me install a UPS and external HDD for file imaging and backup purposes on his Server 2000 last August. He whined and bitched about the cost, but I told him he either takes measures to protect himself, or he could find someone else to provide him the commercial services I was about to set up for him (fully automated Data Extractions, Data Translations and uploading updated data to targeted ftp Servers for SQL Server import). He wondered why I was being so harsh, and I told him that not if, but when, he had a problem I knew he would end up calling me. And I do not have the spare time to try to get a machine in Seattle back up from scratch, or to waste my time with anyone not willing to prevent problems when it is so inexpensive to do so. I also told him if he was real lucky he would never have to thank me for forcing his hand, and if even luckier he would eventually end up thanking me. He rolled over, and I installed the equipment and software, blew an initial Drive Image (www.R-TT.com, they have R_DriveImage for $45, works on Windows Server platforms), and set up the nightly file backups (SyncBack). Two days ago their 2000 Server hard drive crashed mid-day. Who do you think they called? Me, the one who forced the backups and UPS on them <g>... Within 2 hours, remotely guiding their non-IT office clerk, I have them up and running with a new hard drive. And over the next few hours I had restored all their data files (about 10Gb, it took a while) current through the previous night's backup. I could not help myself, so I got transferred to my associate and asked, "Aren't you glad you listened to me last year?" He confessed he recognized the value of the investment, and said he never did dwell on the cost after I had installed the equipment and software - he had gotten over it. Had he not been protected he would have had to send the old drive out to a data recovery lab, maybe pay a few thousand $ IF they could recover data, rebuild the Server O/S, etc. Had no data been recoverable he would to have shut his doors, as all of his client info, billing, active projects data, etc., was on that Server. Less than $500 invested last year saved their business. I have no idea how much grief the UPS saved them over the past year with power related issues, but I bet they had no power related problems on the Server... Gil > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Ed Leafe > Sent: Friday, July 28, 2006 8:04 AM > To: [EMAIL PROTECTED] > Subject: Re: Top 10 reasons for FPT corruption > > > On Jul 28, 2006, at 6:13 AM, Tristan Leask wrote: > > > What are then main reasons for doing this? > > > > Eg, Power cuts / Dodgy disk? > > There are lots of reasons, but keep in mind that corruption > can only > happen when the disk is being written to. Some cases are > unintentional, such as head crashes or cosmic rays flipping bits, but > most are the result of programmatic writes. Minimizing those, through > the use of views and TABLEUPDATing only when necessary, can help > lessen the impact of bad network/ power/ disk situations. > > -- Ed Leafe > -- http://leafe.com > -- http://dabodev.com > > > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
