Could anyone offer ideas around how to manage the log truncation for applications like Exchange/SQL when moving to CloudConnect from a product that used to perform that automatically?
This seems like a pretty important aspect which I can't seem to find any information on.
Best answer by mmcghee
You bring up a good topic. I think your overall list is correct, but I'd want to ensure the choice is matching your requirements. An application/VSS aware backup has benefits with not only truncating logs, but allowing for increment/differential backups and for recovery with log reply/roll forward.
If the last point-in-time backup (or snapshot in this case) matches your RPO requirements (ie. you don't need roll forward), then truncating logs through circular logging or simple recovery mode with SQL databases might suffice. In fact, you'll find Microsoft recommendations to enable circular logging where DAGs are used (https://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx).
But if you have requirements to restore with roll forward, you'll need an application which performs both incremental backups and restores along with log truncation (since you won't want circular logging enabled or simple recovery with SQL). Today something like cloud connect does not perform incremental application level backups, so you would need a third party to perform that operation independently.
Happy to discuss further so we can ensure our documentation is clear.