Running DIRT to do a backup for the first time completes no errors.
Running DIRT the second (or any subsequent) time get 1 error as per error log below.
\\------------ log output ---------
Starting disaster reocovery backup at: 9/10/2003 10:38:41 AM
Backing up registry to: \\10.83.1.134\f$\BackupTest\UnityReg.REG
Backing up the Cisco TSP branch to:\\10.83.1.134\f$\BackupTest\CiscoTSP.reg
Backing up active switch file 1 :D:\CommServer\IntLib\cisco0002.ini
Backing up all AVD files
Backing up StreamFiles folder
Copying out system greetings for default objects
(error) in cmbBackup routine:Permission denied number= 0
Copying EMS Database file out from: D:\CommServer\utilities\EventMonitoringService\database
Backing up UnityDB SQL table
User elected to skip backup of reportDB
Finished disaster reocovery backup at: 9/10/2003 10:38:45 AM
------------ end output --------- \\
Problem seems to be caused by files in the EMSDatabase backup directory - these files all have read only attribute which is causing the problem, when DIRT tries to overwrite them on subsequent backups.
The files backed up in the EMSDatabase dir such as EMSDB_FRESH.MDB, are read only in the ~\Commserver EventMonitoringService origin drectory. Clearing the read only attribute on the EMSDB_FRESH.MDB, EMS_Default_DEU.wav, EMS_Default_FRA.wav and EMS_Default_ENU.wav (in the ~\Commserver EventMonitoringService directory)stops the error occuring.
Not a major problem but an annoyance when you get error reports from DIRT backups and you have to check out the log to make sure it's not something else.
what version of DiRT backup are you using here? The one that comes with 4.0(3) or did you grab an updated version from CiscoUnityTools.com?
Running some tests on my box here the scenario seems to work OK - I'll have to dig around a bit more to see why you're config would be throwing that error. It should be smart enough to rip through and set the read only files to read/write before toasting them (this is a common problem to have with a number of files bulk copied by Unity's setup application).
just a follow up on this - it turned out to be related to some files in the Event Monitoring Service database folder being marked read only which doesn't happen on new installs of EMS but can on installs of Unity left at default. This didn't cause a problem since if the files were marked as read only still they weren't being used (i.e. you weren't using the Event Monitoring Service) so the fact that the database info from this app wasn't included in backups was not a huge deal.
You can fix it quickly by simply marking the 4 files found in \commserver\utilities\eventMonitoringService\Database so that they're not read only.
I've also posted an updated version of DiRT backup (1.0.96) that explicitly handles this situation.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...