zip.*** files remain after backup fails

  • Resolved trustring

    (@trustring)


    1 year, 2 months ago

    Hi.
    I’m using BackWPup 4.0.0.
    The other day I got alerted by my rental server host that my file capacity is terribly expanding.

    Checking with FTP I noticed there’re plenty of strange named files in BackWPup’s backup directory.
    The files are named like:
    2023-08-27_03-01-38_ATPOV4GS02.zip.ERl2Jb
    2023-09-10_03-03-21_TTPOV4AK02.zip.hHjyQ8
    Their permissions are 600, not 644.

    BackWPup’s log tells there’re so many failures with like “restarting the job because of 5 minutes no action” message (translation from Japanese message).
    The strange named files seem the traces of the failures while the reason why the strange named files are not deleted after fail is mystery…

    Could you tell me how I can stop such file expansion?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter trustring

    (@trustring)

    I’ll add some info.
    Today’s new backup files generated be BackWPup are:

    /*-----------------------------------------
    [file num]
    filename
    size
    update time
    permission

[1]
    2023-09-17_03-05-11_VHPOV4GO02.zip.BkH9mH
    1,040,588,800
    3:08:03
    600

[2]
    2023-09-17_03-05-11_VHPOV4GO02.zip.3CgDne
    1,222,594,560
    3:14:03
    600

[3]
    2023-09-17_03-05-11_VHPOV4GO02.zip
    1,580,331,348
    3:21:02
    644

[4]
    2023-09-17_03-05-11_VHPOV4GO02.zip.Z40cVg
    558,714,880
    3:21:04
    600
    -----------------------------------------*/

    Only 3rd one was success, I think.
    Other 3 files are trails of failures and should be removed.

    The reason why they failed is also what I want to know, but first I eager to remove such failed filed automatically.

    • This reply was modified 1 year, 2 months ago by trustring.
    Plugin Support happyAnt

    (@duongcuong96)

    Hi @trustring

    I think the reason is during the process, backup job got terminated by the web server, maybe because of the process using too much server resource.

    That is the reason you see many strange zip files, please just manually remove all of these, also reduce the server load by going to BackWpUp -> Settings -> Reduce server load -> choose medium.

    In case it doesn’t help, please try switching to Tar instead of Zip, Tar uses much fewer server resource than Zip ^^

    Thread Starter trustring

    (@trustring)

    Thank you for the precise suggestions.
    It looks that the two settings made the trouble to solve!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘zip.*** files remain after backup fails’ is closed to new replies.