UnityDB & SQL Maintenance Plan

Unanswered Question
Sep 2nd, 2009

Hello,

I have a customer who's UnityDB Transaction Log is running at 6.5GB in size.

They are looking at running the Cisco document:

Shrink the Cisco Unity Database Configuration Example

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_configuration_example09186a008075ba49.shtml

However, is it safe to keep control of this by configuring a SQL Maintenance Plan?

Has any body done this? Any side effects?

Thanks

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Jaime Valencia Wed, 09/02/2009 - 06:25

Run that doc right now, but after that configure regular DIRT backups. It will trunk the transaction logs every time it runs

HTH

java

if this helps, please rate

neil.woolloff Wed, 09/02/2009 - 06:31

Cheers java,

Seems then that DiRT is not being used otherwise the Transaction Log wouldn't get that big.

Will push that forwards, but what about actually applying a SQL Maintenance Plan.

Is this not good then?

Hoan Mai Wed, 09/02/2009 - 09:09

Shrinking should allow the weekly/nightly jobs in SQL to run properly.

Please check in SQL Enterprise Mgr

SQL Server Group > UnityName > Management > Jobs > SqlNightBackupJob/SqlWeeklyBackupJob

are running daily/weekly without error.

Once you shrink the database, you should be able to manually test the job by right clicking it.

Hoan Mai Thu, 09/03/2009 - 08:30

The jobs should setup by itself so you need not to configure it. If it doesn't run, you might see a red X next to it.

neil.woolloff Thu, 09/03/2009 - 08:38

ah right, sorry now i understand.

will check this, and see what that it is there and if with a red X next to it.

If it is not there, as it seems it should be, is there any harm in creating one? If not, what are the default configuration settings?

Thanks, and apologies if i appeared abrupt.

Actions

This Discussion