TDE Encryption

  • Hi,

    I am wondering if anyone has had this problem.

    I recently encrypted my sql server 2008r2 databases and after that the automated backup job didn't run.

    My backup jobs have been running like clockwork before the encryption, but once the database was encrypted, the job wouldn't run again,

    Does anyone know what is happening?

    Thanks for any insight at all

  • TDE enabled databases can't be compressed. Although this shouldn't stop a backup from running, it is the only thing I can think of off the bat.

    Are you compressing them?

    Edit: I lied, they CAN be compressed. It is just not as much compression as a non TDE enabled database.

    "Encrypted data compresses significantly less than equivalent unencrypted data. If TDE is used to encrypt a database, backup compression will not be able to significantly compress the backup storage. Therefore, using TDE and backup compression together is not recommended."

    ______________________________________________________________________________________________
    Forum posting etiquette.[/url] Get your answers faster.

  • Thanks for your reply

    I am getting frustrated

    I just cant seem to figure out why my backup job stopped running all of a sudden. I thought it had something to do with the job owner but then the job owner hasn't got anythiong to do with encryption or does it

  • What is the exact error you are getting. If the backup fails, it's gotta tell you why.

    ______________________________________________________________________________________________
    Forum posting etiquette.[/url] Get your answers faster.

  • Hi calvo,

    That's exactly my frustration.

    The job doesn't even run at all. It wouldn't even start. and the job is enabled.

    If it ran and failed, then there would be an error but the thing doesn't run at all!

  • What is the error that you are getting when you run the job?

    Adi

    --------------------------------------------------------------
    To know how to ask questions and increase the chances of getting asnwers:
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • If the job doesn't run at all check the fallowing:

    1) Is the SQL Server is up and running?

    2) Is the job enabled or disabled?

    3) Is the job's schedule is enabled or disabled?

    Adi

    --------------------------------------------------------------
    To know how to ask questions and increase the chances of getting asnwers:
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • Perhaps you can run the backup code by itself, outside the scope of the job.

    BACKUP DATABASE [database] TO DISK = '<path>'

    If this works, it's not a backup issue but a job issue.

    ______________________________________________________________________________________________
    Forum posting etiquette.[/url] Get your answers faster.

  • Thanks all for taking out time to assist.

    I can maually run the backup using the same scripts with no problem

    It is just the job that refuses to fire off at the scheduled time

  • So when you right click the job and start it it does nothing.

    When you right click the job and check the job history, what does it say is the result of the run? It must say if it completed or failed.

    ______________________________________________________________________________________________
    Forum posting etiquette.[/url] Get your answers faster.

  • Cool, That's a valid check.

    I have not done that (Right clicked the job and ran it)

    as it is a heavily used system. However, I intend to do that around the time that the job is supposed to run.

    When I do this, I will post what happens.

    Thanks so much for your insight

  • Hi Calvo,

    There was absolutely no window for me to manually run the job so I decided to create another maint plan.

    It ran and the associated job ran on schedule!

    I am relieved though still confused as to why the former job refused to kick off

    All in all, Thanks for your insight

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply