COMODO BackUp 3.0 BUG REPORTS

[Maciek]

@Emanuel Sescu post:36

Hi

Please right click on CBU.exe file in installation folder and choose Properties, choose Compatibility and make sure that all options are unchecked then click “Change Settings for all users” button and make sure all options are unchecked.

Thanks

Thanks a lot! I don’t know what was happened - but Compatibility was at XP mode! :-TU

[emanuels]

@lucapsg post:40

Strange behavior for Settings → Default Destination:
when set to H:\ the proposed path, for example, to backup the My Documents folder is H:\MyDocumentsBackup.cbu

But when it is set to H:\Backup the same path becomes H:\Backup\Backups\MyDocumentsBackup.cbu

Innocent youth

Hi

.cbu file is the default backup format in Comodo Backup.
You can use other backup formats (in advanced mode) such as simple copy, sync, ISO, ZIP.

Thanks

[lucapsg]

@Emanuel Sescu post:42

Hi

.cbu file is the default backup format in Comodo Backup.
You can use other backup formats (in advanced mode) such as simple copy, sync, ISO, ZIP.

Thanks

I am referring to the fact that choosing a destination folder, rather than a drive letter, the string “\Backups” is added to the proposed backup file name:

Default Destination = H:
Proposed file backup = H:\MyDocumentsBackup.cbu

Default Destination = H: \ Backup
Proposed file backup = H:\Backup\Backups\MyDocumentsBackup.cbu

[emanuels]

@lucapsg post:43

Default Destination = H: \ Backup
Proposed file backup = H:\Backup\Backups\MyDocumentsBackup.cbu

Please try
Default Destination = H: \ Backup
then proposed file backup will be = H:\Backup\MyDocumentsBackup.cbu

The issue will be fixed in next release.
Thanks

[ReapedBrain]

Hello to everyone.

• Operating System: Windows XP SP3 (x86)
• Other Backup & Security Software Installed: NANO Antivirus (v.0.14.0.5)
• How you produced the problem: start “Express system test (express-scan)” or “Main memory” scan by NANO Antivirus
• Post Memory Dumps on crash if you encounter any: see the attachment
• File system: NTFS
• Any other Additional Information:

BSOD appears in one of your drivers (bdisk.sys) when we try to get access to it. To be exact we call

PFILE_OBJECT FileObject = NULL;
PDEVICE_OBJECT DeviceObject = NULL;
IoGetDeviceObjectPointer(sDeviceFullName, FILE_READ_ATTRIBUTES, &FileObject, &DeviceObject)

where sDeviceFullName - full path to “device”, created by bdisk.sys (to specify the name of “device” is not possible).

The case wasn’t tested on any another OSs. The problem occurs from v.2.0.108800.9 until the last currently available v.3.0.171317.130 of Comodo Backup. If you need any additional information please contact us here in the thread or via e-mail: support[at]nanoav.ru.

[attachment deleted by admin]

[MetalShaun]

• Windows 7 Home Premium SP1
• CIS 5.3 - UAC is off
• When online backup is mounted as a local drive trying to double click a folder within the mounted drive i get “X is not accessible. The handle is invalid” error and it causes COSService.exe to crash.
• CBU will then prompt to create a diagnostic report and prompt to restart online storage but trying to open the folder will do the same thing again.
• It also does this when viewing the online files within CBU and using the little Plus sign to expand the folder.
  -Here is the Diagnostic report.

---

12.04.2011 21:48:37 Comodo BackUp 3.0.171317.130 12.04.2011 21:48:37 Checking if restart is needed... 12.04.2011 21:48:37 No restart needed... OK! 12.04.2011 21:48:37 Verifying your windows version... 12.04.2011 21:48:37 64bit... 12.04.2011 21:48:37 Windows 7 12.04.2011 21:48:37 Windows version check OK! 12.04.2011 21:48:37 Current user has administrator privileges! 12.04.2011 21:48:37 Checking if Synchronization service is running... 12.04.2011 21:48:37 Synchronization service is running! 12.04.2011 21:48:37 ONLINE STORAGE SERVICE IS NOT RUNNING! 12.04.2011 21:48:37 Checking CBU.exe integrity... 12.04.2011 21:48:37 CBU.exe is ok! 12.04.2011 21:48:37 Checking CSE.exe integrity... 12.04.2011 21:48:37 CSE.exe is ok! 12.04.2011 21:48:37 Checking vss_xp.dll integrity... 12.04.2011 21:48:37 vss_xp.dll is ok! 12.04.2011 21:48:37 Checking vss_vista.dll integrity... 12.04.2011 21:48:37 vss_vista.dll is ok! 12.04.2011 21:48:37 Checking vss_s2003.dll integrity... 12.04.2011 21:48:37 vss_s2003.dll is ok! 12.04.2011 21:48:37 Checking libeay32.dll integrity... 12.04.2011 21:48:37 libeay32.dll is ok! 12.04.2011 21:48:37 Checking ssleay32.dll integrity... 12.04.2011 21:48:37 ssleay32.dll is ok! 12.04.2011 21:48:37 Checking SynchronizationService.exe integrity... 12.04.2011 21:48:37 SynchronizationService.exe is ok! 12.04.2011 21:48:37 Checking COSService.exe integrity... 12.04.2011 21:48:37 COSService.exe is ok! 12.04.2011 21:48:37 Checking ShellExtension.dll integrity... 12.04.2011 21:48:37 ShellExtension.dll is ok! 12.04.2011 21:48:37 Checking cbufs.sys integrity... 12.04.2011 21:48:37 cbufs.sys is ok! 12.04.2011 21:48:37 Checking BDisk.sys integrity... 12.04.2011 21:48:37 BDisk.sys is ok 12.04.2011 21:48:37 Checking CBReparse.sys integrity... 12.04.2011 21:48:37 CBReparse.sys is ok 12.04.2011 21:48:37 Checking cbvd.sys integrity... 12.04.2011 21:48:37 cbvd.sys is ok 12.04.2011 21:48:37 Checking cbvdbus.sys integrity... 12.04.2011 21:48:37 cbvdbus.sys is ok 12.04.2011 21:48:37 Checking cbunat.exe integrity... 12.04.2011 21:48:37 cbunat.exe is ok! 12.04.2011 21:48:37 Checking if BDisk.sys is working properly... 12.04.2011 21:48:37 BDisk.sys is working properly! 12.04.2011 21:48:37 Checking if cbufs.sys is working properly... 12.04.2011 21:48:37 cbufs.sys is working properly! 12.04.2011 21:48:37 Checking if CBReparse.sys is working properly... 12.04.2011 21:48:37 CBReparse.sys is working properly! 12.04.2011 21:48:37 Checking if cbvd.sys is working properly... 12.04.2011 21:48:37 cbvd.sys is working properly! 12.04.2011 21:48:37 Checking if cbvdbus.sys is working properly... 12.04.2011 21:48:37 cbvdbus.sys is working properly! 12.04.2011 21:48:37 Checking windows task scheduler functionality... 12.04.2011 21:48:37 Windows task scheduler is working OK! 12.04.2011 21:48:37 Diagnostics detected some errors (see uppercase errors)!

---

[attachment deleted by admin]

[MetalShaun]

I don’t think the next Sync date and time is quite right here.

[attachment deleted by admin]

[MetalShaun]

When i delete a file from a synced drive the file is just copied back from the other drive at the next synchronization. Surely when you delete a file it should also be deleted from the synced drive at the next synchronization??

Cheers
Shaun

[emanuels]

@MetalShaun post:48

When i delete a file from a synced drive the file is just copied back from the other drive at the next synchronization. Surely when you delete a file it should also be deleted from the synced drive at the next synchronization??

Cheers
Shaun

Delete operation doesn’t propagate in this version.
The issue will be fixed in next release.

Thanks

[Phazed]

Version 133. Windows 7 64 bit.

1. Setting the backup location never sticks, it always is empty when returning to the screen.
2. Once a full backup has completed to a network device, it is impossible to do a differential backup because CB does not see ANY devices on the network for step 3, though there are several present. There NEEDS to be a “Browse” key on this screen! Note that CB does see the devices under Restore and at Step 1.
3. Sometimes CB simply hangs, showing spinning gears

[clemo]

Sorry posted in wrong forum.

[emanuels]

@Phazed post:50

Version 133. Windows 7 64 bit.

1. Setting the backup location never sticks, it always is empty when returning to the screen.
2. Once a full backup has completed to a network device, it is impossible to do a differential backup because CB does not see ANY devices on the network for step 3, though there are several present. There NEEDS to be a “Browse” key on this screen! Note that CB does see the devices under Restore and at Step 1.
3. Sometimes CB simply hangs, showing spinning gears

You can try the 4.0 version here.
It should have issues fixed.
Regarding issue number 2). You can also perform a differential backup by simply choosing the same source and the same destination file. The differential backup will be appended to existing backup file.

Thanks