Updating Photos Library?

[hempomatic]

I have 2 Photo libraries, one on the computer drive, the other on a remote drive. When I click on the remote drive, it starts to update. Does this mean it's updating the program from version 8 to version 9, or is it trying to consolidate the 2 libraries. I have them both backed up, but if the unexpected happens, which it tends to because I rarely know what I'm doing. Restoring over 1/2 TB of data from a spinner BU drive to a remote SS drive drive can be a tedious process.

 

[MacInWin]

or is it trying to consolidate the 2 libraries.

It is not that. I don't know what it is, but it won't merge two libraries like that.

What it could be is that if the library was created with one version of Photos and then you changed to the internal library and then updated Photos to a newer version that required the library to be updated, that the one on the external also needs that same updating. You haven't given much detail, so it's hard to tell.

 

[hempomatic]

The Version of Photos on the computer is Photos 9. I've been using this version for a month or so, but until recently had no need to open the older Library on the remote drive. The computer is updated to 14.1.1

The version of Photos on the remote drive was from Photos version 8, running Ventura. (Do you need any other information?)

I added nothing to the remote library since updating the computer from Ventura. All I did was try to open it because I was looking for some archived pictures. That's when I panicked and killed the update.

 

[MacInWin]

Ok, that explains it. It was updating the version 8 library on the external to be compatible with Version 9. Nothing should be lost or merged, just updating some internals in the library. Depending how you "killed" the update, all should be good. Next time, let it finish.

 

[hempomatic]

Depending how you "killed" the update, all should be good. Next time, let it finish.

Yeah ...... I tend to panic when something happens that I don't understand. Thanks.

 

[MacInWin]

One has to be careful when "killing" a process in the middle of a run. It can leave the thing it was working on in a damaged state. That is why the recommendation before doing things like that is to make a backup, just in case the process goes sideways.

 

[hempomatic]

One has to be careful when "killing" a process in the middle of a run. It can leave the thing it was working on in a damaged state. That is why the recommendation before doing things like that is to make a backup, just in case the process goes sideways.

Thanks Jake,

I let it update. It only took a moment. It was as you expected, just making the two libraries compatible with the current version. Nothing went sideways, but I get your point, I shouldn't have killed it after the update began. I panicked.

I may not know s#*t from shinola, but I do always have a back-up.

 

[MacInWin]

You know more thatn you think, my friend. You know to have backups, and that right there is computer gold!