Client 1.4.9 slowed access to mysql database and postgre

Hello,

i’ve two problems, on two different systems.

Windows 7 32 bits : a software use postgreSQL with big database (9GO)
Windows server 2008 R2 : a software use mysql with big database (7GO)

The folder of the database is selected on urbackup client.

When the backup is run or not run, after a few hours, we see bug slower of the applications used the database.

If i stop the Urbackup service client, the problem stop, and the slower disappear.

What is the problem ?

I’m trying to reproduce this, but haven’t managed that yet with postgres.

Can you have a look at the files in C:\Program Files\UrBackup\urbackup and tell us how big they are?

Can you also have a look at the UrBackupBackend.exe service in the Windows resource monitor and tell us if it is a IO, memory or CPU issue? Thanks!

backup_client.db is 102Mo
filelist.ub 25,469 Mo
open_files.dat is 691Ko

For urbackupclientbackend :
mémory is 11,5Mo
CPU is 12 Threads and now is 0% because no backups

What do you see the IO on the monitor ?

So, i have two server : one local, et one other in Internet.
The Internet backup have an error, and stop to backup.
It’s a file backup.
Is the snapshot can be not clothed (by a bug), which would slow down the computer because there is a lot to write to the database, and if the snapshot is open, the system saturate.
The last time, the system was saturate, i’ve just restart the service, and the database run properly.

(sorry for my english, i’m French)

and i give you the data, but actually the computer is ok…
i will try to see tomorow.

Yes, it currently does not delete the snapshot it creates on backup agressively if there was an error during backup. It gets deleted during the next backup or (as you found out) when you restart the service. I guess it should remove the snapshot more aggressively.

I was just confused because you said performance improved when the service is stopped, because stopping the service does not remove the snapshot.

Having an active snapshot can essentialy half your write performance at the beginning. The Windows server variants allow you to specify that it should store the snapshots on a different volume (shadow storage). If that disk is as fast as your main array you can get back to full speed. See here https://technet.microsoft.com/en-us/library/cc788050.aspx .