It states we need Full recovery model, or the 'nightly truncates' will fail. If they do fail, surely this can be ignored as truncations are not required with the Simple recover model?
Anyone any other reason full recovery would be required? The difference AFAIK is that with simple, the transaction log is cycled and therefore kept small.
With full, it is written to, and can grow, and the log is only truncated/reused after a full backup.
If, therefore, our customers don't back up their DB regularly (and we all know they don't!) they get this problem... eventually it grows.
Why would full recovery be required when even if we did a full system restore we wouldn't likely do a transaction log restore, as we have a full DB backup taken at the point the whole system was backed up?
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
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...