Home Dashboard Directory Help
Search

BACKUP MASTER KEY error reporting oddity by dhammer3407


Status: 

Resolved
 as Not Reproducible Help for as Not Reproducible


2
0
Sign in
to vote
Type: Bug
ID: 771101
Opened: 11/14/2012 10:56:21 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I have encountered and odd behavior with the BACKUP MASTER KEY command when using SQL Server 2008 R2 with SP1 (10.50.2500). When I execute the BACKUP command on a UNC path that I do not have write access to I would expect an error. What I have observed and can reproduce is that when I run the command once I receive the Command Executed Successfully message but I do not get my backup because I didn't have write access. Then if I run the same script again I get the appropriate error thrown.

Test script used (master key encrypted by the service master key):
USE [Master];
BACKUP MASTER KEY TO FILE = '\\Networkpath\TDEKey.key' ENCRYPTION BY PASSWORD = 'MySuperSecretPassword123#@!';

Once I start to get the error I will continue to get it from re-running the script but I can reproduce the issue if I change the name of the file with the file path remaining the same. Once I alter the file name I will once again get the Completed Successfully and followed by the error on attempt number 2.

The only work-around I have found is that local paths do not appear to have this behavior. I did check MSDN and UNC paths are explicitly stated as supported.
Details
Sign in to post a comment.
Posted by Microsoft on 9/30/2013 at 9:20 PM
We were not able to repro this problem and there are no known issues in this functionality. If you're still experiencing this problem, please contact CSS.

Thank you.
Posted by Microsoft on 12/4/2012 at 11:59 AM
Hi,

We're taking a look at this problem and get back to you once we've determined whether this is a bug or not.
Sign in to post a workaround.