Could you please clarify the difference between stopping and cancelling a running backup.

I want to continue using Backup4all v.5 until v.6 becomes solid and stable enough in my opinion, at the same time I would like to use the discounted upgrade to v.6. In fact I have upgraded my licence, and I would like to know if I can: 1. Continue using my currently activated v.5 with the old licenc...

Hello,

I want to upgrade licence from ver. 5 to 6, but still want to use ver. 5.
On the website I see the following warning though: Note: You cannot use the old key anymore after you upgrade to the latest version.

Does that mean that if I upgrade now, I won't be able to use ver. 5?

Use build 414, it works fine despite several minor inconvenient UI things. But these things are nothing comparing to the issues of the latest build. Activation will work, it should be there itself when you reinstall. Try to request the older build from support if you don't have one or find on the we...

Delete these junk files always when the job is aborted, it is a junk and should not be there. It is not a correct behavior of a good program to leave junk. It is not good when you leave junk in temp folders, but it is even worse when you leave junk in a backup output folder. This is not a problem ma...

I have reported this bug on the first day the build came out and wrote on the forum to caution others, but support either does not understand or just don't properly test their program. All they reply to the issues I describe is "we don't have such problems here" or "send us catalog", while I give th...

Why to leave that partial .zip file when the job is canceled? That .zip file is not registered in the catalog so it is a junk that must be removed. On the next run of the job, the program will be adding files to that junk .zip file, right? Because you use zip add method.

1. I mean not the progress view part, I mean the list of all backups where the backup name is shown, the destination of the backup, the date of the last execution, etc... When you run a job, under the backup name in that part a progress percentage bar becomes visible and the program starts examining...

I was already reporting the catalog/database locking issue that happens from time to time: The log shows this error: "Error: SQL error "DELETE FROM JobStatus WHERE JobGuid="{25909D53-9918-4230-9206-08D018B0CD14}" AND ActionType=0" - database is locked, database is locked (5) (SQL81)", however the UI...

I don't mean the temporary files when I write "junk file". Junk file is left in the output folder where the program backups to. So if you have a job that backups folder "A" to folder "B", i.e. in the folder "B" it creates the backups (.zip files), then the junk files are left in that folder "B", i.e...