NightlyCleanThreshhold behavior with multiple mags

Hi,

it will check the largest free space, but it will delete over both MAG, unless you add:

LRUSort = StudyDate

to DICOM.INI in which is will delete oldest studies, but then on MAG0 only...

Not pretty, but you can script more advanced delete mechanisms

Marcel

Hi,

if LRUSort is not set it will delete sorted on the oldest stored date.

If LRUSort is set deleting only occurs on MAG0.

I am adding methods to script the process, where delete is already possible but not the intricate query of finding the oldest patients.

Of course you can run e.g:

dgate(64) --deletestudies:20100101-20100131

this will delete a month of studies from Jan 2010

Marcel

Hi,

the behavior oh NightlyClean is still the same?
I have 2 Mag devices on 2 disks

# Configuration of compression for incoming images and archival

DroppedFileCompression = un

IncomingCompression = un

ArchiveCompression = j2

# Configuration of disk(s) to store images

MAGDeviceFullThreshHold = 30

MAGDevices = 2

MAGDevice0 = d:\dcm_prod\

MAGDevice1 = e:\dcm_arch\

NightlyCleanThreshhold = 70000

NightlyMoveThreshhold = 100000

NightlyMoveTarget = MAG1

I tested the move from MAG0 to MAG1 at 2:00 and the "archived" patient went compressed. It works like a charm!
But I want to be the images stored on MAG1 to be cleaned at night... The MAG0 has "always" enough free space for the production day, but, if I read correctly, I must set the free space on
NightlyCleanThreshhold to 170000?

Nightly Clean start at 1:00 (rigth if I need space on MAG1) but can I be sure the space was "cleaned" from MAG1 and not from MAG0 to reach 170000 MB?

Example if I understand correctly.

After xxxx days
NightlyCleanThreshhold = 70000

NightlyMoveThreshhold = 100000

Day 1

MAG0 free space 101.000
MAG1 free space 80.000

1:00 --> Clean --> No clean (MAG0 > MAG1 > NightlyCleanThreshhold)
2:00 --> Move --> No Move (MAG0 > NightlyMoveThreshhold)

... exams...

Day 2

MAG0 free space 50.000

MAG1 free space 80.000

1:00 --> Clean --> No clean (MAG1 > MAG0 > NightlyCleanThreshhold)

2:00 --> Move --> Move + Compression (compression 50.000 >>> 30.000)

MAG0 --> 100.000

MAG1 --> 50.000

... exams ...

Day 3

MAG0 free space 60.000

MAG1 free space 50.000

1:00 --> Clean --> Clean from MAG1 or MAG0? LRUSort is not set.

Thanks

Hi,

I deletes entire patients that are present on MAG0. However, of studies of the same patient are on other MAG's these are deleted as well. Use with care.

For more advanced deletion algorithms you would have to script it.

Marcel

Hi,

I'm a little confusing.

For me the best option to free space (moving on archive and/or free space) was on studydate, but you said on previous answer that this behaviors work only on MAG0.

If set on LRUSort the older study at 2.00 will be moved on MAG1

Query and Retrieve on the server still work also in this study.

But the clean space beahvior works only on MAG0 and, if I assume the nigtlyMove was well set to free the space needed on a production day, the MAG0 always have enough space and MAG1 will never clean.

I need to delete only on MAG1 to have space for the Nighlymove.

I think I need to clean space on MAG1 using the

--deletestudies:date(range) Delete studies from server on date

in this scenario with a external script looping check of space and the last studydate on server.

I can use Conquest integrated features to "free" MAG0 and move to MAG1, but clean space on MAG1 was my duty. Correctly?

Thanks

Correct!

So the built-in delete option is really only optimised for s single MAG option.

Marcel