We have just taken over maintenance of a unity 4.05 system all was going well but we have recently encountered a problem with disk space filing up. I have addressed the immediate problem by shrinking the unity database in SQL (this got me back 5GB). However a closer look at the jobs in Enterprise Manager shows that the weekly cleanup that should automatically take care of shrinking the DB and backups, etc. is missing or removed.
My question is: How do I go about returning the weekly scheduled cleanup and backup to SQL so it works exactly how cisco intended?
Basically, you need to run the Disaster Recovery tools with an account that has proper rights to access SQL and, if messages are selected for backup, Exchange mailboxes. Please see the section ?Configuring Permissions for DiRT?.
DIRT is already configured and runs successfully every night including the night in question when we experienced an outage on unity until we shrank the sql database.
Unity was not responding because of lack of disk space. sql showed an error in enterprise manager/local/management sql server agent/jobs relating to the daily unitydb backup indicating a failure due to lack of disk space, on all other days this backup has been successful. When we manually shrank the database we could run the daily backup in sql enterprise manager without a hitch.
Having shrank the DB we looked for why it grew in the first place and comparing the server with other unitys found that In enterprise manager/local/management sql server agent/jobs there should be 3 items including a weekly cleanup that are configured automatically during installation. We are missing this weekly clean up and would like to get it back as configured on a new unity install. (e.g. Is the weekly cleanup in a batch file that I can import into jobs?)
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.