FBackup starting and reacting very slow

Post here if you have problems installing or using FBackup
diethardw
Posts: 3
Joined: Sun Sep 18, 2011 9:53 am

Postby diethardw » Sun Sep 18, 2011 5:00 pm

Hello from Germany,


I've tested FBackup 4.6 and it reliably does what it is meant for ;-).


My only problem: When I start the program, it takes up to 30 secondes till the program's window appears, and sometimes it takes several seconds when I call up another backup icon inside this window. I found a similar problem under in this forum from 2 years ago, but there was no reason or solution given.


I use the latest release under Windows 7 64bit.


Thanks,

Diethard



Softland
Posts: 1666
Joined: Thu May 23, 2013 7:57 am

Postby Softland » Mon Sep 19, 2011 4:11 pm

Hi,


Do you have a large backup job?

Please note the backup catalogs are loaded at the application startup.


When does the problem appeared?



diethardw
Posts: 3
Joined: Sun Sep 18, 2011 9:53 am

Postby diethardw » Mon Sep 19, 2011 8:54 pm

Hi admin,


so what is a "large" backup job? Don't know... There are 6 fck files, all together between 8 and 9 MB, the largest is 5.5 MB.


Can't remember when I recognized the problem for the very first time. Tried fbackup in the beginning, then Backup4All, and went back to fbackup again.


Diethard



Softland
Posts: 1666
Joined: Thu May 23, 2013 7:57 am

Postby Softland » Thu Sep 22, 2011 7:00 pm

Hi,


Please close FBackup and rename the "C:UsersAppDataRoamingSoftlandFBackup 4" folder

Start FBackup.

It will start without backup jobs. Does it load slowly? you can then rename the folder back to start FBackup with the backup jobs inside.



diethardw
Posts: 3
Joined: Sun Sep 18, 2011 9:53 am

Postby diethardw » Thu Sep 22, 2011 9:50 pm

Hi Admin,


yes, without that folder FBackup starts in about 3-4 seconds.


Diethard



Softland
Posts: 1666
Joined: Thu May 23, 2013 7:57 am

Postby Softland » Fri Sep 23, 2011 4:22 pm

Hi,


It seems FBackup loads the backup jobs and check the destination drives in those seconds.




Return to “Troubleshooting”