Problems after trying new version of Silverkeeper

2006-11-06 Thread Kaye and Geoff

Hi,

eMac OS10.2.8 backing up to partition on external firewire disk

We use Silverkeeper to do our routine backups. and recently upgraded. 
The new version(1.1.4) was incompatible with the old version, and 
offered features we wanted, including the ability to make the backup 
disk bootable. We archived our old backup (thank heavens), erased the 
backup disk, and tried out the new version with somewhat disastrous 
results.


Although the backup appeared to work ( it took a couple of hours and 
files appeared on the backup disk), the only entry written to the log 
was an error (code 50 - indicates timeout). After finishing the 
backup and rebooting we found that about half our applications had 
disappeared from the Applications folder (and weren't on the backup 
disk). That was solvable, since we had the archive. but we are left 
with a rather strange problem. Our internal drive now shows the unix 
directories (/var, /etc, /usr and so on) in the finder window.


Initially we thought it might be a permissions/ownership problem, but 
fixing permissions didn't sort it out (although there were thousands 
of file permissions that changed). Further investigation shows that 
our internal disk has / as its mount point. I would normally expect 
all disks to have /Volumes as the mount point.


Can we change the boot disk mount point without causing problems? If 
so, can someone remind us where the appropriate unix config file can 
be found? We're familiar enough with unix to be able to edit the file 
directly, but can't find the right file!


A secondary problem is the existence of an alias visible from the 
finder called dev that points to nothing (and gives an error), with 
root/wheel as owner/group having no access as the permissions, 
which are grayed out and unchangeable. Attempting to change the 
ownership from the finder asks for admin password, then gives a no 
permission error. It doesn't show up at all in Terminal, and /dev 
itself is fine. Any ideas?


Needless to say, we've gone back to the old version of Silverkeeper.

Cheers, Kaye  Geoff


--
Kaye Stott and Geoff Prince
Email: [EMAIL PROTECTED]
Web: http://www.omninet.net.au/~kg/


Re: Problems after trying new version of Silverkeeper

2006-11-06 Thread Robert Howells

Howdy Kaye  Geoff ,

In my experience with something like this the end result of trying to  
patch

 the existing system has never been totally satisfactory .

It has been quicker , easier , and more reliable to bite the bullet ,
Reformat the hard drive and copy back an archive  ..
but how effetctive that is for you depends on whether you
have actually archived a total copy of Applications and System ,
as well as your User files .

I use Superduper running from another source to copy the contents of  
a Disk Image

of my Hard Drive , back to the working Hard Drive.

The copy usually takes 1 to 2 hours and everything is sweet after.

Cheers

Bob



On 06/11/2006, at 11:40 AM, Kaye and Geoff wrote:


Hi,

eMac OS10.2.8 backing up to partition on external firewire disk

We use Silverkeeper to do our routine backups. and recently  
upgraded. The new version(1.1.4) was incompatible with the old  
version, and offered features we wanted, including the ability to  
make the backup disk bootable. We archived our old backup (thank  
heavens), erased the backup disk, and tried out the new version  
with somewhat disastrous results.


Although the backup appeared to work ( it took a couple of hours  
and files appeared on the backup disk), the only entry written to  
the log was an error (code 50 - indicates timeout). After finishing  
the backup and rebooting we found that about half our applications  
had disappeared from the Applications folder (and weren't on the  
backup disk). That was solvable, since we had the archive. but we  
are left with a rather strange problem. Our internal drive now  
shows the unix directories (/var, /etc, /usr and so on) in the  
finder window.


Initially we thought it might be a permissions/ownership problem,  
but fixing permissions didn't sort it out (although there were  
thousands of file permissions that changed). Further investigation  
shows that our internal disk has / as its mount point. I would  
normally expect all disks to have /Volumes as the mount point.


Can we change the boot disk mount point without causing problems?  
If so, can someone remind us where the appropriate unix config file  
can be found? We're familiar enough with unix to be able to edit  
the file directly, but can't find the right file!


A secondary problem is the existence of an alias visible from the  
finder called dev that points to nothing (and gives an error),  
with root/wheel as owner/group having no access as the  
permissions, which are grayed out and unchangeable. Attempting to  
change the ownership from the finder asks for admin password, then  
gives a no permission error. It doesn't show up at all in  
Terminal, and /dev itself is fine. Any ideas?


Needless to say, we've gone back to the old version of Silverkeeper.

Cheers, Kaye  Geoff


--
Kaye Stott and Geoff Prince
Email: [EMAIL PROTECTED]
Web: http://www.omninet.net.au/~kg/

-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Unsubscribe - mailto:[EMAIL PROTECTED]