Shirt Pocket Discussions  
    Home netTunes launchTunes SuperDuper! Buy Now Support Discussions About Shirt Pocket    

Go Back   Shirt Pocket Discussions > SuperDuper! > General

Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
Old 02-06-2008, 10:18 AM
guybeckett guybeckett is offline
Registered User
Join Date: Feb 2008
Posts: 2
Making two Macs identical

I work in two locations several hundred miles apart. In each I have a g5 mac running leopard (slightly different vintages but handily both non-intel). Both do time-machine backups to internal drives.

I want the two machines to be clones of one another - so I can just work in either place with the same system set-up. I have a hard drive to transport files between the two locations.

So.. should I just clone the main drive onto the portable hard drive with superduper and then do smart backups at either end each time I move? Are there any issues with doing this? Will adobe cs3 cope with this? What about the time-machine backup disks. Do they need to be cloned as well?

Is anyone else working this way and what are their experiences of problems/solutions?
Reply With Quote

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
One license, several Macs? jpgoldberg General 7 01-18-2008 12:46 PM
Error making Image bives General 5 08-29-2007 08:25 PM
Help? Qs: Backup over 2 FireWire Netw'd Macs SuperDuperUser General 2 12-29-2006 05:11 PM
making external hard drive bootable with SuperDuper mustangpcc General 3 12-27-2005 12:23 PM
Backup und Original not identical? jfahrner General 6 08-02-2005 01:40 PM

All times are GMT -4. The time now is 05:28 AM.

Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2022, vBulletin Solutions, Inc.