J
Jeff Liebermann
[email protected] hath wroth:
It's bad. Just research the number of class action suits on behalf of
irate owners of failed hard disks.
Well, if you want to stay after work, on your time, and clean up the
mess you made on your own computer, or everyone's computer if you
installed a security problem, I'm sure that IT would agree.
Nope. That's an attempt to fix flaky NWAY negotiation in your
ethernet card and ethernet switch. That is a known problem with
various junk cards and switches. However, when I've seen an ethernet
protocol mismatch, the speed is really slow (like 5% of normal), with
lots of data errors. Run:
netstat -e
and see if there are any ethernet errors.
Much more useful are benchmark tests measuring copy, backup, and
restore speeds to and from the network drive. It's not easy to find
the exact location of network inefficiencies, but the numbers should
give you a clue. For example, if you can copy at reasonable rate, but
cannot do a backup to the same drive, then there's something probably
broken in the backup program. Probably the compression routine. I
use IPerf for my various speed tests.
Fine, but you're missing my point. How long would it take for you to
put your machine back together if the HD failed? Would IT do it for
you? If so, you're done, and it's they're problem. However, if you
are expected to return to productivity after IT only restores the
operating system, you've got a major project on your hands. Think
image backups to DVD instead.
Yech. tar only backs up files. If this is a Linux or Unix system, at
the very minimum, you should be using some cpio variant so that you
also backup the device nodes and named pipes. If you think it's
easier to restore the system with an OS reinstall, update, and tar
extraction, fine. If you want it all in one shot, think about a
better (image) backup system.
You won't know if you're in trouble until after you've gone through a
full recovery. If you can find a blank hard disk, try removing the
exiting working drive, cramming the blank drive in its place, and
actually doing a full restore. You'll be amazed at all the things you
forgot to backup.
Good luck.
I've heard it was bad but I had no idea it was that bad.
It's bad. Just research the number of class action suits on behalf of
irate owners of failed hard disks.
Ah. We're kind of limited in what we can do at work - we're not free
to install backup software for instance.
Well, if you want to stay after work, on your time, and clean up the
mess you made on your own computer, or everyone's computer if you
installed a security problem, I'm sure that IT would agree.
The IT folks don't do any
backups for us besides backing up the network drive, and working
directly from the network drive is SLOW. (There was some sort of bug
in Windows XP that made network access super-slow... I discovered the
bug through some web research, and told the IT folks the fix [THAT in
and of itself should raise a few eyebrows] - it involves going to
Device Manager and setting the network card Speed and Duplex to 100Mb
Full instead of Auto) but it's still slow.
Nope. That's an attempt to fix flaky NWAY negotiation in your
ethernet card and ethernet switch. That is a known problem with
various junk cards and switches. However, when I've seen an ethernet
protocol mismatch, the speed is really slow (like 5% of normal), with
lots of data errors. Run:
netstat -e
and see if there are any ethernet errors.
Much more useful are benchmark tests measuring copy, backup, and
restore speeds to and from the network drive. It's not easy to find
the exact location of network inefficiencies, but the numbers should
give you a clue. For example, if you can copy at reasonable rate, but
cannot do a backup to the same drive, then there's something probably
broken in the backup program. Probably the compression routine. I
use IPerf for my various speed tests.
I work off the C: drive
and keep all my files in the C:\Files folder, which makes zipping
really easy. (I close all programs before leaving the office, so open
files aren't a problem.) I create the zip file on my C: drive then
shuffle it over to the file server.
Fine, but you're missing my point. How long would it take for you to
put your machine back together if the HD failed? Would IT do it for
you? If so, you're done, and it's they're problem. However, if you
are expected to return to productivity after IT only restores the
operating system, you've got a major project on your hands. Think
image backups to DVD instead.
At home I take it a step further - run tar backups and run a sha1sum
on that before and after transferring.
Yech. tar only backs up files. If this is a Linux or Unix system, at
the very minimum, you should be using some cpio variant so that you
also backup the device nodes and named pipes. If you think it's
easier to restore the system with an OS reinstall, update, and tar
extraction, fine. If you want it all in one shot, think about a
better (image) backup system.
I ran a few tests and was always able to get what I wanted, so I'm not
worried.
You won't know if you're in trouble until after you've gone through a
full recovery. If you can find a blank hard disk, try removing the
exiting working drive, cramming the blank drive in its place, and
actually doing a full restore. You'll be amazed at all the things you
forgot to backup.
Michael
www.acomputerexpert.com (my side business, after work)
Good luck.