disk name change

[SAMouzon]

I had a hardware disaster that lasted for almost the first two months of the year. I won't bore you with details, but I fixed it by buying a new server disk and a couple new Time Machine disks which I swap out monthly between studio and storage unit. The previous disk was named MouzonCloud 20; the new disk is MouzonCloud 24. The folder structure inside the new disk is identical to the old disk.

I'm finally doing a catalog sync for the first time this year, and if I'm reading the Catalog Sync window's Sync Status correctly, PM is looking for files on the old MouzonCloud 20 instead of the new MouzonCloud 24. I guess I could completely rebuild the catalogs, but is there an easy and clean way to change the disk name so PM will look in the new disk instead of the old one that's no longer connected?

FWIW, every search I do has a yellow circle to the right of the file name on every image I've seen so far, so PM is obviously looking for images on the old MouzonCloud 20 disk. Kirk's response on my previous post clued me in to that. And "24" is the disk size: 24 terabytes, so if there's a clean way to make the transition that would likely save a ton of time.

[Kirk Baker]

If the disk structure is identical, then performing a "Reintegrate Forgotten Catalog" maintenance operation will likely correct the issue.

https://docs.camerabits.com/support/solutions/articles/48001179060-catalog-management

-Kirk

[SAMouzon]

Fabulous... thanks, Kirk! I'll do that.

[SAMouzon]

Kirk, I've followed the link. I forgot the catalog, then located the existing catalog, then reintegrated under maintenance. The operation completed successfully, with the correct number of records, but local files found were 0, local files missing were 0, and files offline were the correct number that's on the old disk.

When I transferred everything to the new disk, I copied both the entire image folder structure and also copied the PM Catalogs. So what's apparently happening is that the catalogs are still looking for the files on the old disk, even though the image files themselves are on the new disk in the same folder structure.

Is there a way to tell the catalogs to look on the new disk instead of the old one? If that or something else doesn't work, am I back to deleting all the catalogs and rebuilding them from scratch as if this were a new PM install? I hope not, because that could take days since I've got over 14T of images. Surely others have had this new-disk problem, right?

[SAMouzon]

It occurred to me that I've done a ton of work with my images so far this year, especially with the metadata. So rather than trying to find a hack for updating the catalogs, it seems like it may be cleaner to just rebuild them from scratch. So I'm deleting each catalog one at a time. I'm on one right now with just over 100,000 images and it started 1:20 ago and is about 55% done. I'm gonna put the big one on to cook before going to bed; it has about 272,000 images so it'll hopefully be done early tomorrow. After that, there's only four more with a couple thousand images each. Even if I'd found a way to redirect to the new disk, this might not take much longer, and is definitely a much cleaner start so I'm OK with it now.

[Kirk Baker]

Kirk, I've followed the link. I forgot the catalog, then located the existing catalog, then reintegrated under maintenance. The operation completed successfully, with the correct number of records, but local files found were 0, local files missing were 0, and files offline were the correct number that's on the old disk.

When I transferred everything to the new disk, I copied both the entire image folder structure and also copied the PM Catalogs. So what's apparently happening is that the catalogs are still looking for the files on the old disk, even though the image files themselves are on the new disk in the same folder structure.

Is there a way to tell the catalogs to look on the new disk instead of the old one? If that or something else doesn't work, am I back to deleting all the catalogs and rebuilding them from scratch as if this were a new PM install? I hope not, because that could take days since I've got over 14T of images. Surely others have had this new-disk problem, right?

There is a file called ".pmshare" that PM uses to track your disks.  It sounds like your backup/restore did not restore that file, or I would have expected a Reintegrate Forgotten Catalog to have found and corrected all paths to your files.

-Kirk