The only time a log should be shrunk is if some abnormal database activity (or failed log backups) has resulted in the log growing far beyond the size it needs...

I thought I saw a post stating that someone had issues on a 64-bit system, but I don't recall seeing a post addressing it. Has anyone tried the script...

I would like to implement a similar solution but I don't understand what role snapshots play in this scenario? Is it not enough to just set up the mirror...