09:02:31,223 INFO - Creating plan status monitor communication channel. 09:02:01,210 INFO - Creating plan status monitor communication channel. 08:19:15,352 INFO - SQL query 'SELECT SUM(ver.size) as size FROM cloud_files as fl INNER JOIN cloud_file_versions as ver ON ver.file_id=fl.id AND fl.destination_id = ?'. 08:19:00,409 INFO - ForceCheckForUpdate=False 08:18:59,834 INFO - VersionCheckWebServiceBased initialized 08:18:59,834 INFO - Start checking for a new version 08:18:59,205 INFO - MemoryManager instance created 08:18:56,825 INFO - Database file accessed: c:\programdata\cloudberry backup enterprise edition\data\cbbackup.db 08:18:55,955 INFO - Refreshing plan list 08:18:54,559 INFO - Creating plan status monitor communication channel. 09:02:01,521 WARN - Communication channel faulted. 09:02:00,595 WARN - Communication channel faulted. 08:18:54,232 NOTICE - CloudBerry Backup Enterprise Edition Console started. I started looking at CloudBerry logs and did not get much information. We have been using CloudBerry Lab Enterprise Backup to store backups in cloud storage. Backups have been running fine for some time but recently ceased to run. It's quite possible that I could have missed it, however.Running a member server 2008R2 server. I believe it uses the built-in Exchange Information Store writer, as I didn't see anything that looked like a third party writer when I ran vssadmin list writers.
#Cloudberry backup for windows server 2008 software
The backup software is CloudBerry Enterprise Backup. I've checked group policy and DCOM there's no antivirus on the system and the firewall is disabled. The service performing the backup is running as Local System, so I don't understand why it wouldn't have access. This is often caused by incorrect security settings in either the writer or requestor process. I'm getting the following error on the start of the backup: Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. I'm having trouble with VSS based backups of my Exchange server.
0 kommentar(er)
