Sycronize After RAID Failure

[MontanaHospital]

Hello,
I have restored my PacsOne from a RAID failure from a full system backup on
September 25th and a /home mirror backup from October 9th. How do I get the
system to recognize the DICOM studies on the /home from between these dates?

One Idea I had was to move them off the /home and then do an import. Is there a
better, easier way?

thanks much for a great system. Had been running flawlessly since 7/2008 and
would not have failed except for accident that pushed the RAID reset button!


-DL

[pacsone]

If you have restored from backup all the raw Dicom image files under "/home", then you don't need to do anything because the raw Dicom image files are exactly where they were before, i.e., nothing has changed as far as PacsOne Server is concerned, so you should be able to access the existing studies exactly the same way as before.

[MontanaHospital]

HI, thanks for your reply.
Let me try to explain my situtation more clearly:

PacsOne RAID crash one week ago.
PacsOne /home archive restore from one week old backup.
PacsOne OS/SQL restore from three week old backup.

The restored Pacs One works fine but only shows studies up to the date of
the OS/SQL backup from three weeks ago ( as I would expect ).

So there are two weeks of DICOM studies on the /home that are not recognized
by the restored Pacs One.

Is there a way for me to get Pacs One to scan /home and re-link to these
two weeks of DICOM files that are now "orphaned" from the SQL database?

thanks for your time.
-DL

[pacsone]

Can you restore the MySQL database from one week ago (instead of 3 weeks back) which is more consistent with the archive restore from the same one week ago?

In any case, you can always submit an Import job from the Tools->Import menu, and enter the restored archive directory "/home" as the Import Source Directory. This Import job will force PacsOne Server to update its database meta-records to re-link to the "new" raw Dicom image files under the Import Source Directory.

If you want to import only the specific days from the 2-week difference between the restored archive directory and MySQL database backups, then you can submit one Import job for each dated sub-folder under the "/home" root directory, e.g., "/home/2012-10-01-MON/", "/home/2012-10-02-TUE/", etc.

[MontanaHospital]

Hi,
I'm sorry but I don't have a more current backup for this situtation
I'll either have to resend from the original modality or import.

But when I try the:
Tools -> Import ->Import Studies from a DICOM Part 10 formatted local directory:
with the directory: "/home/gcmc_us01/2012/10/"

I get the mesage:
"WARNING: DICOM Directory Record File: /home/gcmc_us01/2012/10/DICOMDIR does not exist"

Then:
Job: [1889] has been scheduled to scan studies from: /home/gcmc_us01/2012/10/.

The job gets run but nothing is imported.
If I try creating a directory named "DICOMDIR" and specify that I get a message
that the directory is not Part 10 formatted. (but this should be an exact replica from
the original archive...)

What to do ??

[pacsone]

Did you choose the Native format instead of the default Dicom Part-10 format when configuring the storage format for PacsOne Server to store received images? If so, then those images restored from backup won't have the Dicom Part-10 File Meta Information header and therefore, PacsOne Server would not be able to import them due to the missing Part-10 header.

If this is the case, you'd have to have the modalities re-send the studies over from those 2 weeks' difference between the restored backups. But we'd recommend switching the storage format to the default Dicom Part-10 format for PacsOne Server to store received images, since the few hundreds of bytes saved from the Part-10 header is not worthwhile if compared with the loss of compatibility without the Part-10 header.

[MontanaHospital]

I don't think the choice of Native / Dicom Part-10 format was available on our version.
We are still running v6.1.1 from when we installed the system back in 2008.

I was able to restore, by resending from our modalities, all the studies that were missing from the backup except for one from one modality that I don't have access to.

So I have the DICOM files, presumably in "native mode", from one study that I would like to manually introduce back into the Pacs One database. Can you suggest a way to go about doing this?

Thanks For Your Help !!

PS:
I will include a "mysqldump" operation in my backup routine for this system!!
I will look into upgrading our installation to the current, premium edition, soon!!

[pacsone]

I don't think the choice of Native / Dicom Part-10 format was available on our version.

The storage format selection has always been available since Day 1 when PacsOne Server was first introduced, and it's set to be the Dicom Part-10 format by default.

So I have the DICOM files, presumably in "native mode", from one study that I would like to manually introduce back into the Pacs One database. Can you suggest a way to go about doing this?

You can simply copy/move all the raw Dicom image files of this study (assuming they are in Dicom Part-10 format) into a local/accessible folder on the server where PacsOne Server is running, then submit an Import job from the Tools->Import menu to have PacsOne Server import all the raw Dicom image files from that source folder. Otherwise if the raw Dicom image files are NOT stored in the Dicom Part-10 format, you'd need to re-send that study from the source modality to PacsOne Server, via the Dicom networking transfer protocol.

[MontanaHospital]

I'm going to presume that this choice is made during the installation process and that we probaby, naively, choose "Native" format.

When I upgrade PacsOne perhaps would it make sense to just build another server with PacsOne configured for Dicom Part-10 format and then do a DICOM transfer
between the servers to get everything into Part-10 format ?

Thanks again for your help.