nightly move with 1.5.0 not usable

  • hi marcel

    for years I used nightly move to keep enough free space on mag0.

    In previous versions that could be organized by keeping the GUI running.

    But since Version 1.5.0 this results in a suprisingly reaktion:

    My settings are "below 200GB move to mag1"

    but with 190GB free space the GUI moves 190GB and not only 10GB!

    HS

  • Hi,


    the configuration screen: Free disk Space 186 gigabyte


    maintenance.log:

    24.09.2020 12:15:33 ------------------- Show free space on devices --------------------

    24.09.2020 12:15:33 [XXX] ** MAG DEVICE CHECK

    24.09.2020 12:15:33 [XXX]

    24.09.2020 12:15:33 [XXX] Free space on MAG Device 0 := 194594 MByte

    24.09.2020 12:15:33 [XXX] Free space on MAG Device 1 := 766802 MByte

    25.09.2020 02:00:00 Making space at night by moving LRU patients to: MAG1

    25.09.2020 02:00:00 Amount of MB to move: 200000

    25.09.2020 02:00:00 [XXX] ---------- Start archival operation -----------

    25.09.2020 02:12:19 [XXX] Archival: set archive flag for patient: xxxxxxxx

    ......

    25.09.2020 04:59:44 [XXX] MoveDataToDevice: copied image data for patient: xxxxxxx


    and maintenance.log after nightly zip:

    25.09.2020 05:00:12 [XXX] MoveDataToDevice: copied image data for patient: xxxxxxx

    ........

    25.09.2020 08:01:24 [XXX] MoveDataToDevice: compared image data for patient: xxxxxxx

    25.09.2020 08:02:47

    25.09.2020 08:02:47 ------------------- Show free space on devices --------------------

    25.09.2020 08:03:24 failed nightly moving

    25.09.2020 14:03:33

    25.09.2020 14:03:33 ------------------- Show free space on devices --------------------

    25.09.2020 14:03:33 [XXX] ** MAG DEVICE CHECK

    25.09.2020 14:03:33 [XXX]

    25.09.2020 14:03:33 [XXX] Free space on MAG Device 0 := 191764 MByte

    25.09.2020 14:03:33 [XXX] Free space on MAG Device 1 := 566492 MByte


    The reason for "failed nightly moving" was the exit from GUI at 8:03.

    So the GUI could not delete the successfully compared data on mag0. This data is now duplicated from Mag0 to mag1.

  • Hm,


    this is the code:


    Code
    mb := StrToIntDef(trim(EditNightlyMoveTreshold.text), 0) - DiskFreeGB(Label10.Caption[1]) div 1024;
    WriteMemo(MaintenanceMemo, 'Amount of MB to move: ' + IntToStr(mb), 100, 200, 'maintenance');


    I think it mixes up MB and GB...


    To clean MAG0 run:


    dgate64 -amMAG0.Archiving,MAG1


    Which will copy again and then delete.


    Marcel

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!