OMV7 backup problem - Backup Job never completes

  • Hello,


    I am using OMV7 for many months to backup a windows server. Everything was working fine until some major power outages a few days ago caused reboot of the windows server and network disconnection between the server and OMV7. After this problem it seems that OMV can not complete any backup job.


    The hardware that OMV is installed is an old Acer Veriton PC with Intel Core2 Quad (Q9400) CPU @ 2.66GHz, 6 GB RAM, a Kingston SSD for the operating system and 2 Seagate IronWolf Pro 4TB disks (BTRFS/RAID) for storage.


    I use remote mount plugin to mount the shared folder of the windows server on OMV and then rsnapshot plugin to create hourly, weekly, monthly and yearly backups to the local BTRFS system.


    I have rebooted and updated OMV but still the problem persists.


    Just to be sure I disabled the old backup jobs and created a new one, to back up a 13GB folder from the windows server to a new shared folder on OMV. The job started normally but after 1 hour it was not completed and Ι got an error that the next hourly job can not start. During this hour the network statistics was showing a steady network traffic of almost 10Mbps. I was also watching the backup folder through an sftp client and noticed that after about 10-15 minutes from the job start the number of files in the backup folder remained steady and no new files were backed up but the network traffic did not decrease. I also noticed that even when I disabled the backup job the network traffic was at 10Mbps and it stopped only after rebooting OMV.


    Attached you will find some screenshots of my system to help you understand the problem


    I am about to reinstall OMV, so any suggestion would be really appreciated.


    If I finally reinstall OMV, should I use the old backup folders? Will OMV recognize the old backup data? or is it better to create new?


    I searched around the forum and the internet before posting and I could not find anything related to my problem.

    If the thread is in the wrong topic please move it.

    Thank you for your help





  • crashtest

    Approved the thread.
    • Official Post

    For debugging I would just run the rsnapshot job once. I think you can increase the verbosity of the output by adding an option in the "rsync long arguments" field (e.g. -vvv).

    You can see the logs in /var/log/rsnapshot.log or in the GUI

  • Thank you very much for your reply macom.


    I did exactly what you suggested. I put -vvv on the rsync long arguments field and I run the job manually. I also disabled the hourly backups in the job configuration to avoid errors every hour.


    This is what I got in rsnapshot log:

    It seems that after 3 hours and 40 minutes the job was completed but with some warnings. Unfortunately there was no evidence in the log what the warnings was about.


    I think now that the errors I was having after the power outage was because OMV was probably trying to copy all the data again or at least verify them.


    Is it normal to take so much time to copy 13GB over the network?

    Note that the real data I want to backup are 555GB and it didn’t take that log (respectively to the data) to back them up the first time.


    Is there any way to see what these warnings are?


    Do you thing that the speed problem is due to OMV problem or network issues?

    • Official Post

    Unfortunately there was no evidence in the log what the warnings was about.

    At least there are two warnings mentioned starting in line 6 and line 10. The first one mentions that some files were transferred only partially. Second one does not give any additional information.


    Not sure if the logging was more verbose.

    If you look in this file

    /var/lib/openmediavault/rsnapshot.d/rsnapshot-1f4c5481-a400-47a3-a051-2b71a56d63d6.conf

    you can change "verbose" e.g. to 5. Might be worth a try to get some more information.

    The verbose levels are defined in the man page: https://manpages.debian.org/tr…pshot/rsnapshot.1.en.html

  • Thank you for your answer.


    I have seen these warnings in the past even without the -vvv option. Maybe it has something to do with files in use.


    I will try changing the verbose level on the config file and come back with the results.


    Any suggestions about the slow file copy would be really appreciated.


    What file copy speed would be considered normal in a local network for OMV? (our main switch is a relatively old CIsco with 100Mbps ports)

  • Then you should see max 100Mbps which is around 12 MB/sec

    :) I mean the real speed that you have seen with your experience not the theoretical one.


    Anyway the "verbose" and "loglevel" settings in the config file helped me.


    I did many tests while monitoring the network speed of the server and came to the conclusion that the problem is with the network speed and not with OMV functions. It was taking too long for a backup job to complete and I thought It was freezing or something.


    The problem now is that when OMV is backing up a folder the speed is about 10Mbits per second, if I copy the same folder from the server to my Linux Mint pc the speed is 30Mbits per second or more.


    Is there anything I can do to improve OMV copy speed?


    And one more question. Are there any cases that OMV might have to copy all the data again? (maybe if a backup job is abnormally interrupted?)

    • Official Post

    Is there anything I can do to improve OMV copy speed?

    If you are using smb, you can check the smb/cifs subforum for tweaks. Or use nfs instead, which has less overhead.



    Are there any cases that OMV might have to copy all the data again? (maybe if a backup job is abnormally interrupted?)

    No idea, but OMV is not doing any magic. It is just using rsnapshot and rsync. So you could search for those.

  • I want to thank you for your help macom, the settings about the log details helped me to see the real nature of my problem.


    Since it is a network speed issue I will search the forums, do some tests and come back with a new thread if needed.


    You can close this thread now, I am not sure if I can close it.

  • macom

    Added the Label resolved

Participate now!

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