This is more of an observation than a bug report. The help section does not appear to contain a description of command line parameters for excluding hidden and system files. However, the CB GUI supports these options.
CB does not let me schedule a daily backup to a network location and let me run the backup as a service. However, I can schedule it as a normal backup.
Steps to create problem:
Use the GUI to create a backup to a network location.
I notice the following behaviour when I use the REV_NO macro in a backup job.
I am performing incremental backups to a network location using an automatic base. The destination file has the REV_NO parameter specified.
When I run the backup the first time, CB performs a full backup and creates a backup file with a revision number of 0000000001.
When I run the job a second time, CB performs an incremental backup using revision 0000000001 as a base and creates a new backup file with a revision number of 0000000000 (all zeros).
When I run the backup on all following occasions, CB performs an incremental backup using revision 0000000000 as a base and APPENDS the further incremental backups to revision 0000000001, which was the original full backup.
Perhaps I am misunderstanding something but it seems to me that the CB should logically increment the revision number each time it runs the backup.
Just following on from my last post regarding the REV_NO macro, I wish to make the following observation about the sparse level of detail in the Help file on the macro parameters in general. Whilst each macro parameter is self-evident, there is no guidance on how to use them to best effect. For example:
Apart from the different names, what is the difference between REV_NO and INCREMENT_NO? When is it better to use one instead of the other?
How does using the parameters affect the way CB behaves when performing full, differential and incremental backups with pre-defined and automatic base files?
How does using the the macros affect the before operations?
I ask these questions because after having experimented with the macros to work out a coherent backup strategy to network locations and to a FTP server, I get strange and unexpected bahaviours.
I look forward to receiving some clarification on these parameters.
I am running Windows 7 SP1 64 bit on a Lenovo ThinkCentre M82 computer.
Following the update of Comodo Backup to V.4.3.9.27, I began experiencing frequent instances of Windows Explorer hanging and having to be restarted.
After a lot of troubleshooting using Microsoft CleanBoot procedures, I found that by disabling Comodo Backup integration into Windows Explorer Shell, the problem ceased. I think there is a bug in this version of Comodo Backup.
I have been using Comodo Backup for many months without any problems whatsoever. I am not using any other backup software.
I am using Norton internet Security software V. 21.5.0.19.
Kind regards.
Windows 8.1 64-bits
Security software: Norton Internet Security Version: 21.4.0.13
No other back-up programs
Problem: no progress in backup.
CB stuck at message “Initializing Shadow Copy. It might take some time…”
How to produce the problem:
When I first ran CB I got error 180, but I discovered this was due to the fact that I did not run CB as an administrator. I then ran it as an administrator, choosing a “simple copy” with back-uptype “incremental”. I try and back-up “My Pictures” and %appdata% to a local USB hard drive. CB has been saying "Initializing Shadow Copy. It might take some time…’ for 60 minutes now. No change. Could you please resolve this?
How to resolve: No idea.
Alright: time for me to uninstall Comodo Backup. It has never once been stable, and I noticed Comodo’s moderators stopped being active on the subject January 2014. This makes me think CB has been abandoned. Too bad: the specs are wonderful and I would have loved to use it. I do wonder about Comodo’s policy though: wouldn’t it be better to let users know you don’t see a future for a certain product anymore?