backup slow in v24

[dl1clm]

A Happy New Year to all.

Since I run version 24 I am under the impression that 'Backup' is much slower as it was in earlier versions.
The database type I use is SQLite and I have a little over 4000 records in the database.
I made the setting so that a backup is stored on my network using a UNC path like I had in version 22 and 23.
Now in version 24 when I close the logbook it takes about 40 seconds showing 'Backup in Progress' and than finally the application closes.
I checked my server and network but can not find an issue there.

Many thanks for the nice Logbook program, it is doing a great job for me. I use it for 6 months now, previously I used HRD 5.

73 Dick

[DF5WW]

Hi Dick,

i can´t finde an issue like you described and i have more than 21.000 QSO´s stored in my SQlite database. Could it be that some other windows processes slowing down the storage speed of your HDD ???

On my side all is working fine and quick

[G4POP]

Hi
Backup is a little larger than previous versions because we now save all of your configuration files to zipped backup folders.

That said I have just timed the close down and backup with a 37000 QSO database and the overall time was 8 seconds

Therefore I suspect something on your computer is slowing the process down

[dl1clm]

Thanks for your reply.
I don't know what is the difference, but when I use version 1.23 the network backup is made within 4 seconds.
The network and the server is the same. I even created a network drive mapping instead of using the unc path but that did not make a difference.
when I use version 1.23 the backup is working quick.
I wonder what is the difference??
When I do not enter a path in the Backup textbox (default location in Settings 1 tab) the backup is done within 2 seconds.

thanks for your help.
73 DIck

[G4POP]

Did you try uninstalling Log4om, doing a fresh download and then a new install?

[dl1clm]

No, I did not do a clean setup with V 1.23. I did a fresh install a month ago ( v1.23 ) on my clean installed Windows 10 laptop.
At that time I printed all the config settings and copied a few of the xml files back.
What is the best way to do a clean install and keeping all the settings?

I just checked some different backup methods:
Backup to HD takes a few seconds
Backup to external USB HD takes also a few seconds
Backup to USB memory stick takes also a few seconds
Backup to network based on both UNC ( \\server\backup\ ) and drive mapping takes over 40 seconds.

Now since my backup performance is very slow I am triggered to have a closer look at the backup and see that a backup is made everytime I close Log4OM. That is because I checked the box 'Auto backup on closing' and is OK, except I was not a ware that the backup is also made when I did not change anything in the database. My backup depth setting is 6 and so after 6 times closing Log4OM without entering any data I do have a set of backups, all the same and no history backups anymore. I was under the assumption that only backups ware made if there was a change in the database. Maybe this can be suggestion for future development.

I can not find any problems in my network, other application communicate at normal speed with the server. Maybe I can do a test this afternoon to setup a different server in the network and see what that will do.

73 Dick

[DF5WW]

Hi Dick,

i don´t know b4 what a UNC server is but could it be that it´s the thing which is described in this (sorry to other users, german wiki) wiki ???

Could it be that there are some handshakes needed between L4O backup routine and the server adress which slowing down the backup process ??? Only an idea, i´m not a specialist

[dl1clm]

Hi Terry and Juergen,

Thanks for your reply.
@ Juergen The UNC path method is only a way to connect to a folder or share on a server. You can make a share like G:\server\backup and on your workstation create a mapping like G: = folder backup on the server. If you send the backup to G: the backup will be made on the server in the folder 'backup'. The other method is using the UNC (Universal Naming Convention) path without creating a drive mapping on the workstation the UNC path in this example will be \\server\backup.

@ Terry and Juergen
I had an eye opener after I setup a second server in the netwerk. I changed the backup settings in LOG4OM and the network backup was very quick. Then I did some performance tests with big databases on the original server, no performance problem for the outlook database (540 Mb). I was
Then I had and did a reboot of the server and after the reboot the backup was performed in about 8 seconds, so much better.
I am still very why for some reason my server is communicating slower to Log4OM as it is communicating to other applications.
But I hope I will find an explanation.
For me it is clear that this could not be a Log4OM issue. Why it is introduced to me directly after the update to v1.24 is a big
Maybe I have to reboot my server on a regular basis

Thanks for your help and advice.

73 Dick

[IW3HMH]

Backup is made everytime you close because you may have updated a QSO or printed a label.
Usually, when an user open the software it makes at least one thing on the database, from there the assumption to make a backup at every program shutdown.

If you're worried about rotation you can enable secondary backup. This is another, fully indipendent backup (log4om exports all data again, doesn't recycle previous backup just made in the primary folder).
In this folder log4om will never delete anything. It's up to you delete the backup every x days/months/years/never