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

Go Back   Shirt Pocket Discussions > SuperDuper! > General
FAQ Community Calendar Today's Posts Search

 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #3  
Old 03-16-2008, 08:54 PM
gianfri gianfri is offline
Registered User
 
Join Date: Mar 2008
Posts: 8
I see. So to restore from a NAS drive to, say, Mac #1 I would have to connect to the NAS drive from another computer on the same network (Mac #2), then use Mac #2 to clone the SD! image drive from the NAS to the local drive of Mac#1. Is this correct?

Thanks!

PS I read in some forum posts elsewhere that there are in fact ways to use Time Machine on a network drive, provided that one can initialize the Time Machine drive connecting it directly to the Mac as a local drive. After that the drive can be set up as a network drive and Time Machine should be able to recognize it. I guess I will have to try to see if cloning the existing Time Machine backup from the local drive to the NAS will enable Time Machine to recognize the drive....
Reply With Quote
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 

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
Windows equivalent to SuperDuper!? jreffner General 21 08-13-2009 05:36 PM
Restoring boot drive from a clone and subsequent Time Machine backup Hoosier_1701 General 1 03-06-2008 01:42 PM
Feature request - turn off Time Machine on clone rmf General 7 11-29-2007 05:52 PM
A different angle on SD & Time Machine integration badlydrawnboy General 10 10-26-2007 08:37 PM
A SuperDuper Back Up Strategy Bagelturf General 3 09-09-2007 01:23 PM


All times are GMT -4. The time now is 01:31 AM.


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