July 17, 2017 at 10:16 am
Hey Guys,
I suddenly start to get the message while performing backup, I know i have taken backup of the certificate and stored it in my password manager which I still have access to.
My question is that do we need to have backup cycle of certificate(s) backup? is there any default limit set from Microsoft that we need to take backup every x days. I know ,I took backup of certificate on '2017-02-03 15:57:53.000' i.e. 164 days ago.
Warning: The certificate used for encrypting the database encryption key has not been backed up. You should immediately back up the certificate and the private key associated with the certificate. If the certificate ever becomes unavailable or if you must restore or attach the database on another server, you must have backups of both the certificate and the private key or you will not be able to open the database.
July 19, 2017 at 11:13 am
goher2000 - Monday, July 17, 2017 10:16 AMHey Guys,I suddenly start to get the message while performing backup, I know i have taken backup of the certificate and stored it in my password manager which I still have access to.
My question is that do we need to have backup cycle of certificate(s) backup? is there any default limit set from Microsoft that we need to take backup every x days. I know ,I took backup of certificate on '2017-02-03 15:57:53.000' i.e. 164 days ago.Warning: The certificate used for encrypting the database encryption key has not been backed up. You should immediately back up the certificate and the private key associated with the certificate. If the certificate ever becomes unavailable or if you must restore or attach the database on another server, you must have backups of both the certificate and the private key or you will not be able to open the database.
If it's expired, you typically get a warning about expiration instead of the "has not been backed up" warning. I thought the has not been backed up warning was only if the key was not backed up. Did you check sys.certificates? It has start date, expiry date and backup date.
If you don't specify the expiry date when you create the certificate, the default expiry date will be a year after the start date.
Sue
July 21, 2017 at 5:00 am
goher2000 - Monday, July 17, 2017 10:16 AMHey Guys,I suddenly start to get the message while performing backup, I know i have taken backup of the certificate and stored it in my password manager which I still have access to.
My question is that do we need to have backup cycle of certificate(s) backup? is there any default limit set from Microsoft that we need to take backup every x days. I know ,I took backup of certificate on '2017-02-03 15:57:53.000' i.e. 164 days ago.Warning: The certificate used for encrypting the database encryption key has not been backed up. You should immediately back up the certificate and the private key associated with the certificate. If the certificate ever becomes unavailable or if you must restore or attach the database on another server, you must have backups of both the certificate and the private key or you will not be able to open the database.
As long as you have the password for the cert backup it's valid. It doesn't need to be backed up every week and indeed you don't want multiple backups of the cert lying around.
An expired cert will not stop the backup operations, just apply a new cert as soon as possible and take a backup of the new cert
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 21, 2017 at 11:15 am
phew.. figured out, I have created one certificate on one of the SQL server and took backup of it, then i restored that certificate to rest of the servers for cross-server database restore. since there were no backups taken on rest of the servers, it gives warning of not having backup of the cert.
Thanks for your help
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply