Jump to content
UNIVAC

Cloning a backup set to a larger drive

Recommended Posts

I am running Retrospect Desktop v12.6.1.101 on a Windows 7 Pro system.


Earlier this year, I cloned a complete backup set from a 1TB external drive to a 3TB external drive using a partition manager called MiniTools.  My Retrospect scripts continued working with the new cloned drive without a hiccup.  Not only have the backups continued working, but I have done restores from the new drive, too.  All was good!


Last weekend, I cloned another complete - but different - backup set from a 2TB external drive to a 4TB external drive.  I followed the exact same procedure I used earlier in the year (I took screenshots the first time).  However, Retrospect is not finding the new backup set when I run my backup script, it appears:

image.png.71c15ed3dd47319079c7248fd46ee049.png

The volume label, file system type (NTFS), allocation unit size and the number of files and folders are all identical as one would expect after a disk clone.  Of course, I extended the partition on the new drive during the clone to take advantage of the entire 4TB. The only odd thing is that, if you look at the member properties for the new 4TB drive, it says it’s 2TB in size.  

What am I missing?  My research in this forum hasn’t turned up anything except that Retrospect uses UUID for identifying disks.  I’m not sure if this a new feature in Retrospect v12.  Besides, if it DOES use UUID then why did my earlier clone this year work? (I think I was on v12 of Retrospect when I did the earlier clone this year).  Ideas anyone?

 

bryan

 

 

Share this post


Link to post
Share on other sites

Retrospect has always used UUID to identify a disk. 

When doing your first cloning, you probably opened the backup set properties to check your new disk could be found and at the same time pointed out the backup set member's "new" location to Retrospect. That is the only explanation I can think of.

Share this post


Link to post
Share on other sites

Hi Lennart_T,  Yes, I believe you are correct and I must've opened the backup set and reselected the backup folder on the drive to reset the values of the drive (capacity, UUID (?), etc.).

Thanks for refreshing my memory and I've added that extra step to my clone doc!

bryan

Share this post


Link to post
Share on other sites

I had exactly the same problem about a week ago, and I solved it by doing what UNIVAC did. Love the name.  😃

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×