SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Backup jobs failed for encrypted databases


Backup jobs failed for encrypted databases

Author
Message
coolchaitu
coolchaitu
SSCrazy Eights
SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)

Group: General Forum Members
Points: 8255 Visits: 1627

Good Morning Experts,

One of our SQL Server instance has few databases with encryption turned on. The backups for these databases were failing with below error:

Cannot open session for cryptographic provider 'LunaEKMProvider'. Provider error code: 5. (Authentication Failure - Consult EKM Provider for details)

However, when the server team rebooted this server on sunday as part of planned activity, the backup jobs ran successfully.

I just checked the encryption state and it is turned on. I am unable to understand why the backup jobs failed before the reboot?Please advise


Sue_H
Sue_H
SSC Guru
SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)

Group: General Forum Members
Points: 72184 Visits: 14878
coolchaitu - Monday, January 15, 2018 9:39 PM

Good Morning Experts,

One of our SQL Server instance has few databases with encryption turned on. The backups for these databases were failing with below error:

Cannot open session for cryptographic provider 'LunaEKMProvider'. Provider error code: 5. (Authentication Failure - Consult EKM Provider for details)

However, when the server team rebooted this server on sunday as part of planned activity, the backup jobs ran successfully.

I just checked the encryption state and it is turned on. I am unable to understand why the backup jobs failed before the reboot?Please advise



You'd probably need to check with SafeNet, their documentation or whoever works with that piece. It sounds like it's however they protect/manage the keys and not really a SQL Server thing. From using it once years ago, there is something you install to work with the keys so maybe that got installed and then needed a reboot? Check first with whoever is managing that piece in your infrastructure, they probably know.

Sue



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search