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

Go Back   Shirt Pocket Discussions > SuperDuper! > General

Reply
 
Thread Tools Rate Thread Display Modes
  #1  
Old 02-04-2011, 11:54 AM
webatomic webatomic is offline
Registered User
 
Join Date: Jan 2011
Posts: 18
Verifying a clone

Is there some preferred method for verifying a cloned drive? Some quick way of checking that everything is as it should be?
Reply With Quote
  #2  
Old 02-04-2011, 12:11 PM
dnanian's Avatar
dnanian dnanian is offline
Administrator
 
Join Date: Apr 2001
Location: Weston, MA
Posts: 14,814
Send a message via AIM to dnanian
Starting up from it is often a good check...
__________________
--Dave Nanian
Reply With Quote
  #3  
Old 02-04-2011, 12:15 PM
webatomic webatomic is offline
Registered User
 
Join Date: Jan 2011
Posts: 18
Quote:
Originally Posted by webatomic View Post
Is there some preferred method for verifying a cloned drive? Some quick way of checking that everything is as it should be?
Right. I figured out that much. But from that point, are there any tips on what to check, or ways to quickly compare it against the source drive to make sure it's all good?

I'm figuring on this being a regular thing, so I'd like to have some kind of simple routine to go through, unless you think simply booting to the clone is proof enough that it's an exact duplicate of the original.
Reply With Quote
  #4  
Old 02-04-2011, 12:19 PM
dnanian's Avatar
dnanian dnanian is offline
Administrator
 
Join Date: Apr 2001
Location: Weston, MA
Posts: 14,814
Send a message via AIM to dnanian
There's really no way to verify. And, frankly, with a live system it's changing constantly. By the time you get around to 'checking' it, it's different.
__________________
--Dave Nanian
Reply With Quote
  #5  
Old 02-04-2011, 12:21 PM
webatomic webatomic is offline
Registered User
 
Join Date: Jan 2011
Posts: 18
So you recommend to boot from it and then move on basically, yes?
Reply With Quote
  #6  
Old 02-04-2011, 12:29 PM
dnanian's Avatar
dnanian dnanian is offline
Administrator
 
Join Date: Apr 2001
Location: Weston, MA
Posts: 14,814
Send a message via AIM to dnanian
My general suggestion is to have more than one backup. It's faster to create and maintain two backups then it is to verify one, and it has additional benefits, too.
__________________
--Dave Nanian
Reply With Quote
  #7  
Old 02-10-2013, 01:58 PM
garoomph garoomph is offline
Registered User
 
Join Date: Jun 2006
Posts: 29
Quote:
Originally Posted by dnanian View Post
My general suggestion is to have more than one backup.
When I clone into an image I want to verify that before multiplying it.

I tried rsync --dry-run --checksum, but it only displays results at the very end, which is annoying for tens of gigabytes.
Reply With Quote
  #8  
Old 02-10-2013, 03:45 PM
dnanian's Avatar
dnanian dnanian is offline
Administrator
 
Join Date: Apr 2001
Location: Weston, MA
Posts: 14,814
Send a message via AIM to dnanian
Understood. It's not something we have a solution for at present.
__________________
--Dave Nanian
Reply With Quote
Reply


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
Problem Booting From a Clone on a Firewire HD sgmorr General 8 03-11-2010 11:11 PM
Windows equivalent to SuperDuper!? jreffner General 21 08-13-2009 05:36 PM
Using Disk Utility from Clone gets -9972 error (falsely?) eagseags General 6 09-08-2007 09:50 PM
Persistent failure to copy radicalkat General 1 08-10-2007 08:00 PM
Problem getting apps to run on clone volume ChetA General 3 09-06-2005 02:19 PM


All times are GMT -4. The time now is 12:27 PM.


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