Data Backup and Recovery

How to protect the CIFS Availabilty Group T-Log Repository Share


In creating a backup schedule for a new SMSQL 6.0 implementation with SQL Server 2012 and Availability Groups, I'm curious how to protect the CIFS repository that stores transaction logs for the AG nodes.  In particular, I'm curious how snaps of the CIFS share coincides with the entire backup set of data LUN, t-log LUN, and SnapInfo LUN.  Do I just use the run-after command in the backup wizard after every full or t-log backup?  Is there even a reason to keep the CIFS share snapped if the t-logs are already protected by snaps and backup metadata in the SnapInfo LUN?

All the best,




Justin Welch addresses this in this thread

Basically, use the "run after" command in a backup job to execute a script that updates a SnapMirror relationship.

Register for Insight 2021 Digital

INSIGHT 2021 Digital: Meet the Specialists 2

On October 20-22, gear up for a fully digital, totally immersive virtual experience with a downright legendary lineup of world-renowned specialists. Tune in for visionary conversations, solution deep dives, technical sessions and more.

NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner