I'm coming to the conclusion that my best option is to reschedule my full backups to happen exactly after the snapshot is taken.

Now, is that retarded of Microsoft or what? 🙂

Let me put this another way: Is there any valid reason for Microsoft not to fix this? After all, if we look at both KB articles 951288 and 903643, the issue has been around in a form or another for quite a while. Do they have this scheduled for a fix any time soon?

Additional question:

Is there a way I can setup a trigger to fire my full backup right after the snapshot? This way I can be certain that even if someone creates and unscheduled, ad-hoc snapshot I will not have the problem. What I have in mind is:

1-Setup a trigger on the server to watch for snapshots.

2-On successful snapshot, right after, fire off a full "proper" DB backup.

Is this possible? Is there an after_successful_snapshot trigger somewhere, or something similar that I can use?

Much appreciate the help,

Raphael