Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Message from discussion Happy with image backup :)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Mark Conrad  
View profile  
 More options Aug 9 2003, 11:57 am
Newsgroups: comp.sys.mac.apps
From: Mark Conrad <nos...@iam.invalid>
Date: Sat, 09 Aug 2003 15:57:02 GMT
Local: Sat, Aug 9 2003 11:57 am
Subject: Happy with image backup :)
For those like myself who can't afford a raid backup system, the next
best seems to be working very well.

I have 105 backups to my credit so far, and near as I can determine the
105th backup is just as good as the 1st one.

All my applications work as well, all the configurations of my
applications are intact.

The  _good_  version 2.1.1 of DiskWarrior never complains when I use it
to check out the directory of my OS 10.2.6 after a restore operation.

I am getting so lately I don't even bother checking OS ten after a
restore, because by now I have a lot of faith in the restore operation.

All my files are packed in butt-tight after any five minute restore of
the 3.06 GBs of files in my present smallish OSX implementation.  No
fragmentation whatever of my files in the 12.00 GB partition I set
aside for OS-X.   That means the "heads" of my disk drive do not have
to whip themselves to death picking up ump-teen pieces of a scattered
file.

Less wear and tear on my disk drive.

On the down side, OS X seems to get "confused" by my restore
instruction, so temporarily (for the last 105 backups) I am ignoring
the onscreen warning that appears immediately after the five minute
restore operation:

"Your disk was not put away properly, there may be damage to your files"

I have tried everything to try to get rid of that warning, but nothing
works, so I will pass it off as a false warning.

After all, nothing dire has happened after 105 restores.

Below are the two one-line commands I use for backup and restore, the
individual pieces of these one-line commands are seperated by
semicolons, which tells the computer to execute all the pieces one
immediately after the other.

To Backup-

dd if=/dev/rdisk0 of=/Volumes/Util-4/OSX-Backup-8-2/Bak bs=524288
count=1000;dd if=/dev/rdisk0 of=/Volumes/Util-4/OSX-Backup-8-2/Bak2
bs=524288 iseek=1000 count=1000;dd if=/dev/rdisk0
of=/Volumes/Util-4/OSX-Backup-8-2/Bak3 bs=524288 iseek=2000
count=1000;dd if=/dev/rdisk0 of=/Volumes/Util-4/OSX-Backup-8-2/Bak4
bs=524288 iseek=3000 count=1000;dd if=/dev/rdisk0
of=/Volumes/Util-4/OSX-Backup-8-2/Bak5 bs=524288 iseek=4000
count=1000;dd if=/dev/rdisk0 of=/Volumes/Util-4/OSX-Backup-8-2/Bak6
bs=524288 iseek=5000 count=1000;dd if=/dev/rdisk0
of=/Volumes/Util-4/OSX-Backup-8-2/Bak7 bs=524288 iseek=6000
count=1000;dd if=/dev/rdisk0 of=/Volumes/Util-4/OSX-Backup-8-2/Bak8
bs=524288 iseek=24574 count=5

To Restore-

dd if=/Volumes/Util-4/OSX-Backup-8-2/Bak of=/dev/rdisk0 bs=524288
count=1000;dd if=/Volumes/Util-4/OSX-Backup-8-2/Bak2 of=/dev/rdisk0
bs=524288 oseek=1000 count=1000;dd
if=/Volumes/Util-4/OSX-Backup-8-2/Bak3 of=/dev/rdisk0 bs=524288
oseek=2000 count=1000;dd if=/Volumes/Util-4/OSX-Backup-8-2/Bak4
of=/dev/rdisk0 bs=524288 oseek=3000 count=1000;dd
if=/Volumes/Util-4/OSX-Backup-8-2/Bak5 of=/dev/rdisk0 bs=524288
oseek=4000 count=1000;dd if=/Volumes/Util-4/OSX-Backup-8-2/Bak6
of=/dev/rdisk0 bs=524288 oseek=5000 count=1000;dd
if=/Volumes/Util-4/OSX-Backup-8-2/Bak7 of=/dev/rdisk0 bs=524288
oseek=6000 count=1000;dd if=/Volumes/Util-4/OSX-Backup-8-2/Bak8
of=/dev/rdisk0 bs=524288 oseek=24574 count=5

The one-line  _backup_  command has never given me any problems, i.e.
the partitions of my internal drive never try to remount themselves.

The restore command is another story, all the partitions of my internal
drive remount themselves immediately after the five-minute command
finishes executing itself.

I temporarily tried the variation below to try to get rid of any
tendency of the partitions to remount themselves  _during_  execution
of the restore command:

dd if=/Volumes/Util-4/OSX-Backup-8-2/Bak of=/dev/rdisk0 bs=524288
count=1000;umount -f /Volumes/OSX;umount -f /Volumes/Tiny;umount -f
/Volumes/OS9;umount -f /Volumes/Spare;umount -f /Volumes/Storage;dd
if=/Volumes/Util-4/OSX-Backup-8-2/Bak2 of=/dev/rdisk0 bs=524288
oseek=1000 count=1000;umount -f /Volumes/OSX;umount -f
/Volumes/Tiny;umount -f /Volumes/OS9;umount -f /Volumes/Spare;umount -f
/Volumes/Storage;dd if=/Volumes/Util-4/OSX-Backup-8-2/Bak3
of=/dev/rdisk0 bs=524288 oseek=2000 count=1000;umount -f
/Volumes/OSX;umount -f /Volumes/Tiny;umount -f /Volumes/OS9;umount -f
/Volumes/Spare;umount -f /Volumes/Storage;dd
if=/Volumes/Util-4/OSX-Backup-8-2/Bak4 of=/dev/rdisk0 bs=524288
oseek=3000 count=1000;umount -f /Volumes/OSX;umount -f
/Volumes/Tiny;umount -f /Volumes/OS9;umount -f /Volumes/Spare;umount -f
/Volumes/Storage;dd if=/Volumes/Util-4/OSX-Backup-8-2/Bak5
of=/dev/rdisk0 bs=524288 oseek=4000 count=1000;umount -f
/Volumes/OSX;umount -f /Volumes/Tiny;umount -f /Volumes/OS9;umount -f
/Volumes/Spare;umount -f /Volumes/Storage;dd
if=/Volumes/Util-4/OSX-Backup-8-2/Bak6 of=/dev/rdisk0 bs=524288
oseek=5000 count=1000;umount -f /Volumes/OSX;umount -f
/Volumes/Tiny;umount -f /Volumes/OS9;umount -f /Volumes/Spare;umount -f
/Volumes/Storage;dd if=/Volumes/Util-4/OSX-Backup-8-2/Bak7
of=/dev/rdisk0 bs=524288 oseek=6000 count=1000;umount -f
/Volumes/OSX;umount -f /Volumes/Tiny;umount -f /Volumes/OS9;umount -f
/Volumes/Spare;umount -f /Volumes/Storage;dd
if=/Volumes/Util-4/OSX-Backup-8-2/Bak8 of=/dev/rdisk0 bs=524288
oseek=24574 count=5

I got onscreen update messages that the partitions were  _already_
unmounted, during execution of this temporary restore command.

The warning message about improper "put-away" still occured at the end,
so I gave up on the variation directly above.

I will just ignore the warning message.

Mark-


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.