Q about SQL Transaction log best practice on CCM servers
Just come on board to a new position and taking a look over the CMCS servers I'm now supporting and had a question about the SQL Transaction logs on the servers and what's considered best practice out in the field.
I've found that the Transaction Logs for both the CCM0302 and CDR databases are growing unchecked, and don't appear to be truncated by BARS during backup.
Given I'm running BARS nightly, and any restore would be from a BARS restore, am I best off switching the DB's to simple logging instead of Full Logging? I realise I loose the ability to do a point in time recovery of the DB, but given I'm not ever likely to do that, instead just doing a full BARS restore, is there any issues in this change?
Haven't found anything in net searches regarding this topic so would be interested in hearing if anyone else has changed their logging settings or are running a seperate process to truncate the logs after a BARS Backup.
Re: Q about SQL Transaction log best practice on CCM servers
Okay, so apart from managing to post my Q twice (damn those browser delays + refresh), I think I have the answer.
When BARS runs, it actually does a truncate of the CDR DB Tlog. It doesn't shrink it though. So if for whatever reason, the tlog has grown to a large size, it will remain that way unless you go into SQL EM and manually shrink it.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...