Hello!
Window 8 Prof x64
Comodo Antivirus
I have installed 4.2.2.15 and rebooted the OS. I run cbu from command line with administrative privileges with script file. CBU starts and hangs (it seems to me), utilizes processor power. I wait for a long time, but cbu still hangs. In taskmngr.jpg processor priority is normal, but in script is high value. In previous version of cbu this script works properly.
Hi Sepp,
Did you run into this errr the during very first backup after the ugprade to 4.2.2.15? (I did).
I’ve re-installed 4.1.4, and have no more problems.
Won’t do automatic upgrades anymore - not reliable engough …
I tried to upgrade from 4.1.4.0 to 4.2.2.15 then I got an error “can’t create registry key!(5)” what does that mean and what can I do about it?
I couldn’t start the comodo backup after that and I couldn’t reinstall 4.1.4.0. So I had to use system restore to have it work again.
I have win7 64-bit with MS Security Essentials
Your Operating System (and whether it’s 32bit/64bit);
Windows 7 Ultimate x64
Other Backup & Security Software Installed;
Comodo Firewall and Anti-Virus
How you produced the problem;
Open Comodo Backup (always runs elevated), Click ‘Manage’, select a schedule and edit, select the ‘Remember Connection Information (Unsafe)’ tick box. Click ‘Save Schedule’. Edit schedule again - observe that the ‘Remember Connection Information (Unsafe)’ tick box is NOT ticked as it should be.
How you tried to resolve the problem;
Attempted the above procedure several times, tried closing/reopening the GUI, stopping/restarting the service etc. This setting will not save. A schedule created in the previous version has the option ticked, but as soon as the schedule is saved, the option becomes unticked. This is definitely a new issue with 4.2.2.15.
Further details;
I send my backups to a shared folder on my local nas device. There is no need for additional authentication when connecting to the relevent UNC path. The previous version worked without issue, but 4.2.2.15 prompts me for authentication when first starting the backup job. Clicking ‘Ok’ without entering any details allows the job to process. The problem occurs when a scheduled task executes in this state - it appears to await authentication, but does not display any pop up, so effectively hangs. I only noticed this when I checked the logs and could see that the task had not executed - attempting to run the task manually resulted in a message stating the task was already running. Checking the processes, I could see an additional instance of CBU.exe that was not showing any activity (although it was not crashed). Forcefully ending this process allowed me to start the job manually - which then prompted me for authentication.
This has only occurred since the upgrade to 4.2.2.15, and is a show stopper. My backups need to run, and I really don’t have time to babysit them.
Running a Sync back up manually between my C Drive, (C:\Usres[i]XXX[/i]\Pictures to Z:\Pictures) the back fails at random points with error code 4 (Internal Error).
Debug file attached.
Z: is an mapped LaCie NetworkSpace 2 (OpenShare).
I suspect this might have something to do with File Permissions but am not totally sure. Any help with this matter would be appreciated.
Your Operating System (and whether it’s 32bit/64bit): Windows 7 Ultimate 32bit
Other Backup & Security Software Installed: CIS 6.0
How you produced the problem:
create custom profile, enable macros while creating
create another custom profile
Bug Summary: when creating second custom profile in Macros field you’ll see the name of previous (first) custom profile (must be empty). Only when you check ‘Enable Macros’ previous name will be changed with the right one.
I set up a new Pictures Synchronisation(one way) backup to a new folder on my Network drive (openspace share). When running the backup manually the backup runs very well. But, when it runs on the saving of a file the backup kicks in but dos not write anything to the Network drive.
I also tried running the same backup to an internal drive, then it work as expected.
- Your Operating System (and whether it’s 32bit/64bit);
Windows 7 64bits - Other Backup & Security Software Installed;
Only Comodo Backup - How you produced the problem;
Error 1: From Shortcuts, click on Backup Now, some backups do not execute and gaves an error (image CB_error1.png
Error 2: In Shortcuts, when I delete the backup (using the cross button) it gaves the error shown in image CB_Error2.png - How you tried to resolve the problem; n/a - Screen-shots with the error (if any);
- if the issue is a BSOD, please post all the dump files in \Windows\Minidump folder (you can compress them); n/a - if the issue is a crash, program stops responding or freezes please see this topic
N/A - if the issue is an error (not program crash or freeze) please run the dbgInfo.bat in installation folder and post the resulting cbu file:
I will upload debug info to my online storage and send you the link in a PM (to Petru Clazan) - Any other Additional Information (for example, any non-default settings used);: N/A
Yesterday upgraded to 4.2.2.15.
Running CB from command line in script as scheduled job, running without anyone logged in:
CBU.exe
/backup_operation destinationtype 1
/silentRun
/log_method “create”
/diskusage high
/processorusage high
/type filesandfolders
/source "C:\ "
/exclusionfilter “.tmp|.bak|hiberfil.sys|pagefile.sys”
/destinationpath “X:CBUfiles\20130201_Differential_FF.cbu”
/log_file “X:\Logs\20130201_Differential_FF.log”
/compressionlevel maximum
/backup_type differential
/parent_backup_backup_type 1
/parent_backup_path “X:CBUfiles\20130127_Normal_FF.cbu”
/description “Differential backup of files and folders”
Previously (before 4.2.2.15) CBU.exe performed the backup and exited, after which my script did some postprocessing.
Now, the CBU.exe does not terminate, but stays active using 25% CPU time (i.e. the full use of one of the processor kernels). Needless to say, my script did not change and has run satisfactorily for at least several months.
Your Operating System (and whether it’s 32bit/64bit);
Windows 7 Ultimate 64-bit
Other Backup & Security Software Installed;
Comodo Internet Security premium 5.12.256249.2599, anti-virus disabled;
Avast Antivirus 7.0.1474
How you produced the problem;
See above
How you tried to resolve the problem;
No actions yet
Screen-shots with the error (if any);
No screen shots (see above; scheduled job runs without terminal window)
if the issue is a BSOD, please post all the dump files in \Windows\Minidump folder (you can compress them)
No BSOD
if the issue is an error (not program crash or freeze) please run the dbgInfo.bat in installation folder and post the resulting cbu file.
No error, the backup was made and the log file terminated with the last lines:
01.02.2013 06:25:04 Writing indexation…
01.02.2013 06:25:16 Items backup is complete.
01.02.2013 06:25:16 Closing backup…
01.02.2013 06:25:16 Size compressed is 2.79 GB, size uncompressed is 3.76 GB.
01.02.2013 06:25:16 Backup Process Complete
Any other Additional Information (for example, any non-default settings used);
Online storage service is NOT started (I do not use online storage).
Other Backup & Security Software Installed: ESET Smart Security
How you produced the problem:
Make an image backup of more than one partition to one .cbu file, as shown on “backup.png”.
After the backup finishes, try to mount one partition of it - “mount.png”.
After clicking the mount button, the progress bar disappears at around 70%, the screen shows that the backup is mounted, but no new drive appears in Windows. This is the state where I made the debuginfo.
Also note that if the backup resides on a network drive, an explicit error message appears, and the backup won’t be mounted (not even the progress bar will appear).
If the backup is on a USB hard drive, the same happens like in the first case, but clicking the unmount button after the faily mount operation doesn’t even unlock the volume where the backup file is stored. So after trying to mount the backup (without success) the USB drive cannot be ejected.
How you tried to resolve the problem:
As an other test, I tried what happens if I put only a single partition to a .cbu file. Actually, then it works from local and USB drives, but the network case still giving the same error message.
For me the image backup option is the most useful in Comodo Backup, and mounting backed up partitions is a really great feature. So please, fix this issue.
- Your Operating System (and whether it’s 32bit/64bit): Windows Home Server v.1 (same platform as Windows Server 2003 32bit) also Windows XP Professional (will confirm if issue is also present under Windows 7 Professional 64bit) - Other Backup & Security Software Installed; None - How you produced the problem; Without warning, after 4.2 update, all previously working command line scripts now fail (CBU.exe runs and consumes vast amounts of processor resources but never completes and produces no backup log file) - How you tried to resolve the problem; I have tried: removing the /silentRun flag from the scripts (no change, Comodo Backup interface never opens even though CBU.exe runs in Task Manager), modifying the scripts to match minor changes in your scripting parameters (no change, interface does not open and CBU.exe process runs while eating lots of processor time), creating a job within the Comodo Backup (it runs fine, including successfully sending an email which was previously broken), exporting that job to a script/.CBS file (the resulting file does not open Comodo Backup but does load a CBU.exe process which consumes most of the processor usage but never completes successfully) - Screen-shots with the error (if any); No error produced, just misbehaving scripts/processes - if the issue is a BSOD, please post all the dump files in \Windows\Minidump folder (you can compress them) - if the issue is a crash, program stops responding or freezes please see this topic - if the issue is an error (not program crash or freeze) please run the dbgInfo.bat in installation folder and post the resulting cbu file. - Any other Additional Information (for example, any non-default settings used); I notice that whereas before a single CBU.exe process would be fired up and used for scripted and/or interactive/GUI processes, now additional CBU.exe processes are fired off and attempt to run concurrently with each call to the GUI or a script.
I have to say, much as I appreciate Comodo providing a free software package, I have suffered through many hours of troubleshooting and frustration as release after release are pushed out the door without proper testing - some problems are fixed but new issues are more often than not introduced with each update. This is largely what drove me to using what should be a stable command line script with various systems I administer. It is only because of users complaining that the servers are running slowly (a result of CBU.exe processes consuming most of the processor resources and never completing) that I became aware of just how badly this update has broken Comodo Backup and the scripts we use. Not only that, you change the scripting parameters without notice, have typos in the manual for version 4.2 regarding the script syntax (page 190 “/destinationType” parameters list “/destinationType1” no space and then “/destinationType 3”, “/destinationType 7” with a space), and provide confusing/inaccurate(?) instructions (page 197 describing manually generating a script file illustrates quotes around the entire script, referencing/calling the CBU.exe executable, and parameters such as “/runmode 1” which are neither shown earlier in the manual for script syntax nor match what is outputted by the Export to Script function within Comodo Backup). Perhaps instead of just releasing “updates” that are not well tested (obviously), you should enroll the help of the community to test them first. This a much better alternative than releasing update after update that breaks things and then saying that it will be fixed again in a future release. Perhaps you should listen to the feedback you get in these forums which express a lot of discontent with this methodology. We appreciate a free application, but if it entails ongoing hours of troubleshooting with each new update, it’s not worth it. Please, please, please change your testing procedure and stop releasing updates that break as much they fix. Thanks from all of us who are (or want to be) fans of your product.
PS: In addition, the email notification function, though at least now working under WHS (Windows Home Server aka Windows Server 2003) v.1 is still broken in the Comodo Backup GUI where remembered addresses if selected prepopulate the wrong fields (offset by 1). In addition, when exporting a script, the subject field lacks quotes around while email security has a single trailing quote after NONE.
Other Backup & Security Software Installed;
Crashplan
How you produced the problem;
Backup to FTP
Everything looks great except after about 10 minutes of backing up
22.02.2013 16:57:25 Total items found is 4184. Total size is 1.12 GB
After about 2500 lines
22.02.2013 17:07:44 Reconnecting to “ftp.XXX:21”…
22.02.2013 17:07:45 Cannot recover from this. Data written to ftp server was lost. Cache size needed minimum was 37739976 bytes
22.02.2013 17:07:45 An error occurred while writing data to backup!
22.02.2013 17:07:47 Error Occurred
22.02.2013 17:07:56 Email notification sent successfully!
22.02.2013 17:07:56 Backup failed with code 4 (Internal error).
I tried again
22.02.2013 17:24:59 Cannot recover from this. Data written to ftp server was lost. Cache size needed minimum was 37623176 bytes
22.02.2013 17:24:59 An error occurred while writing data to backup!
22.02.2013 17:25:00 Error Occurred
22.02.2013 17:25:14 Email notification sent successfully!
22.02.2013 17:25:14 Backup failed with code 4 (Internal error).
A backup to the local hard disk was absolutely fine!
