Sync Migrating Catalog to new Win 11 PC

[Minguy]

Lightroom Version Number

13.4

Operating System

1. Windows 10
2. Windows 11

My LrC catalog lives on a Win 10 laptop which is many years old and has partitioned drives C:\ and D:\. The catalog lives in the User directory on C:\ and the backups are written to D:\, which is also where my photo archive lives. Everything is backed up to external drives.

My new desktop PC has a 2TB SSD which has (out of the box) only a C:\ drive. I'm not used to that, being an old Win10 user. I expected a partitioned drive. I have not yet found (via Adobe help and here) the recommended way to migrate my catalog and files to a new directory structure that doesn't match the old, partitioned one. I do know how to "find missing files", and it works, so I have an intact catalog. but I get an error telling me that sync doesn't recognize my new directory structure. I understand why that's happening, but I don't know the best way to complete the process of letting the ecosystem know where everything is. Thank you!

 

[Minguy]

I think I figured it out....Edit>Preferences>Lightroom Sync> Set location to newly created C:\"Lightroom Synced Photos" folder.

 

[Gnits]

Have you moved your images from the old D drive on the old computer to the C drive on the new computer. If so.... what is the top folder of your images. How many images do you have.

 

[Minguy]

Caveat: All of this can be undone by way of backups. What I did was copy the "photos" folder from D:\Photos of my old PC into a folder I created on the new PC also called "Photos", therefore C:\Photos. Then I copied the proper LRCAT file from the old C:\user\Lightroom directory into a newly created C:\user\Lightroom directory on the new PC. Upon opening this catalog file on LrC on the new PC, the database reflected the correct amount of files, but all of my folder structure in that database reflected "missing" (with question marks: ?") images . This makes sense because the path is mismatched. Therefore I used "Locate Missing Files" to build a new association between the catalog database and my new C:\Pictures file path. This worked. However, when attempting to sync with the cloud I got a message saying it couldn't find the sync folder. So, as I posted afterwards, I established a fresh sync path using Edit>Preferences>Lightroom Sync, and this appears to be working. Although I'm still mystified about how the ecosystem syncs everything. I guess that's for me to figure out on my own.

 

[Gnits]

Ok that makes sense. Sounds like you are back on track.

For Win machines I typically have one solid state drive dedicated to the o/s and apps and have a second drive dedicated to data. This simplifies my backup routines with different strategies for my c drive and my data drive. Lots of people argue that it is easy to rebuild and reinstall apps so no point in backing up the system drive. I disagree with that point of view for lots of reasons… but that is a different topic.

You could still partition your drive, without losing any data and do something similar. You would have to copy the photos to the second partition and re set the sync folder setting.

You know best what will work for you.

 

[Minguy]

It makes perfect sense to use partitions in the way you state, which is what I was accustomed to, having used Windows forever. How is a user supposed to protect themself from a root drive failure that takes out your OS and your working files in one go? I was surprised to find this is apparently how it works since I last bought a PC several years ago.

 

[Gnits]

The optimum solution is to have a small ssd for the O/S and a larger SSD for data. If buying a PC from a store that is not always possible.

OS failures are not always due to a disk failure (especially with solid state)... eg failed update, power failure , virus attack, etc, ... but that is why backups are always needed.
I had a c drive failure about 15 years ago and it still pains me to remember the pain inflicted. While I was able to get a new disk and rebuild the o/s and reinstall all the apps ...I never got back the machine that I lost, as I had to re configure all my apps, reinstall all the plugins and one forgets that every app keeps loads of default settings in hidden places (such as the registry). I vowed never to let it happen again.

Here are two emails I received this morning. The lower one (at 5.32) tells me that my 'System Backup completed successfully. The upper email confirms my internal M2 drive was backed up successfully at 06:01. In running these backups every day for 15 years I have only had 4 incidents where the backups were not completed and I had good error messages to tell me why (probably lack of space). These are totally automated, so no effort to run.

I have a C drive for o/s and apps, an internal M2 drive for all my data (eg word docs, etc) and all my images for the last 2 years. I have an internal spinning drive which holds my repository of images older than 2 years (ie back 20 years or more) and back these up to a NAS drive.

 

[karl.nyhus]

It makes perfect sense to use partitions in the way you state, which is what I was accustomed to, having used Windows forever. How is a user supposed to protect themself from a root drive failure that takes out your OS and your working files in one go? I was surprised to find this is apparently how it works since I last bought a PC several years ago.

I thought partitioning a disk drive like this was a holdover from the days when disk drives first became physically larger than what operating systems could handle?

But in modern times, this is a poor practice if it leads you to think that you actually have two physical disk drives.

If the partition masquerading as a C:\ drive fails, it can take out the other partition, too. That doesn't happen if C:\ and D:\ drives are in reality separate physical disk drives.

 

[Minguy]

karl, you may be exactly right. I know that a partitioned drive is still just a single physical drive and therefore it can fail and take all partitions with it. That's why I've always tried to keep an independent backup of each . That said, If newer store-bought Windows PCs are shipping with a single SSD, which is something I wasn't used to, maybe it makes sense to back up that single drive with an adequately-sized external drive?

 

[karl.nyhus]

I know that a partitioned drive is still just a single physical drive and therefore it can fail and take all partitions with it. That's why I've always tried to keep an independent backup of each .

As long as you know that, you'll do fine.

 

[clee01l]

I thought partitioning a disk drive like this was a holdover from the days when disk drives first became physically larger than what operating systems could handle?

I agree. But you will see Partitions used in other ways like recovery partitions. I believer both Microsoft and Apple partition the primary disk in this way. The problem with partitions is when the hardware disk fails, you lose all of the partitions.

If you want a Primary Disk for OS and apps, I think you are better off thinking smaller and getting a second disk for data.

 

[PhilBurton]

I think that all Windows PCs are delivered with a C: drive that uses all the space on the internal drive, which is an SSD or preferably an NVMe drive,, which has faster read/write speeds.

IF you are comfortable with third-party utilities that can create, delete, resize, etc partitions, try https://www.partitionwizard.com/free-partition-manager.html. It's free and has a very nice user interface so you can see changes before you commit to making them. Highly recommended. You don't need to pay for a professional edition. If you need a professional version, this forum is not the right place to discuss how to use those versions.)

Just be sure to do a full backup before making any such changes. And yes, your catalog backups should be on a physically separate drive, no matter if it is an SSD or mechanical HDD.

 

[clee01l]

I think that all Windows PCs are delivered with a C: drive that uses all the space on the internal drive, which is an SSD or preferably an NVMe drive,, which has faster read/write speeds.

You might want to check again. It won't be large, may be a few MBs.
https://superuser.com/questions/1824542/move-windows-recovery-from-c-onto-its-own-recovery-partition

 

[Gnits]

One option is to create a recovery drive on a usb Thumbnail drive.

https://support.microsoft.com/en-us...a-8766-73fab304c246#WindowsVersion=Windows_10

I have one in an enveloped taped to the side of a bookshelf in my office. It becomes a last line of defence,

If I do have a crash of my C drive, my preference is that I will recover from my backed up c drive, which will always be less than 24 hours old. Recovering this drive will also bring back all my installed apps, but more importantly their configuration status, word templates and all detailed settings for each app. A

 

[karl.nyhus]

But you will see Partitions used in other ways like recovery partitions.

Of course. My only objection to partitioning a disk is when the partitions are made to look like disk drives.

 

[Minguy]

Just ran the Win 11 disk management utility and it shows that my 2TB "C:\drive is actually partitioned out of the box as pictured. This is familiar to me from past Windows OS's, it's just that the default directory used to show a C:\ drive for the OS, and a D:\ drive for storage.
I guess I will just use a third party backup utility to keep running backups of the entire drive, (plus independent backups of LRc synced files and my photo archive)unless someone here has a better suggestion. If anyone can suggest a practical backup utility that is good for personal (as opposed to enterprise) use, please let me know.

 

[Gnits]

For genuine backup software, I am a big fan of Macrium Reflect.

There are a lot of versions from free (I think) to home owner, server, small business, large business, etc.. It is a long time since I looked at pricing, so not familiar with their recent offerings. I set mine up 15 years ago and working ever since, but running with the latest version.

My background is large scale enterprise computing and used to spending millions on backup systems, this is ideal for personal use.

I have it configured it to treat my C drive as a system drive , so it does backups that the backup can be used to restore a working Windows system.

I have my data drive backed up in folder mode. Individual files can be recovered, but I have never had to.

It automatically keeps generations of backups, which you can set how many. I have mine set to do a full backup on Sunday Mornings and do incremental backups every morning at 5.30 / 6:00. The daily backups only takes a min or two.

It has full logs, recovery options, etc..

I back up to an Internal spinning disk, as they are so cost effective now and easiest to deal with if I need to recover.


These backup tools are completely different from File Copy or File Synch apps (think Beyond Compare or Good Synch), which also have their uses.

 

[Gnits]

The C drive above consumes 99% of your drive. Ignore the other partitions. I would not touch them. They may contain engineering type utilities installed by the PC maker or disk maker.

 

[Minguy]

Great information. Thanks very much!

 

[PhilBurton]

You might want to check again. It won't be large, may be a few MBs.
https://superuser.com/questions/1824542/move-windows-recovery-from-c-onto-its-own-recovery-partition

Cletus,

Technically you are correct. Going further, a modern GPT-formatted drive has two other partitions also hidden to the user (who does not turn on the option to view hidden partitions.) But as a practical matter, the average user is concerned only with the C: partition.

 

[PhilBurton]

Of course. My only objection to partitioning a disk is when the partitions are made to look like disk drives.

Well, technically speaking a Windows drive IS a partition, but that distinction isn't important to most users, and I would wager, even a majority of members of this forum. (I could be wrong, of course. Would not be the first time. )

What is important is that without specialized utilities or some RAID configurations, two or more physical drives can't appear as just one Windows partition.

I'm afraid that this thread has veered off into Windows-geek-land. For members of this forum, the key point is that catalog backups should be on a separate physical drive from the catalog itself. Same for the photo image files and their backup. If you find that any more detail is Too Much Information, best to consult a specialist.

 

[Gnits]

Great information. Thanks very much!

When you have a new PC is the opportune time to decide how you want to structure your storage, before the C drive begins to fill organically.

For some people, they prefer to keep as much as the o/s and apps contained on a C drive and use a separate partition to keep data separate and make it easier to manage data and backup routines.

Naturally, it is better to have separate drives than multiple partitions, as a faulty drive will bring down all partitions. That is no different than keeping everything on the C drive... but you have better ability to manage the data partitions from the o/s partitions.

Standard windows features allow you to shrink the space occupied by your existing C drive and then create a new partition, but for many this is stepping into uncomfortable territory and it makes sense to have a backup regime in place to back up your system drive before making such changes.

At least with a desktop, you have the option to add, over time, internal and external drives to provide you with further flexibility. There is no perfect solution.