Comments
Sort by recent activity
I had other backups failing with the same errors as in my first post; we resolved them by adding the Skipchecks registry entry. For the answer to your question, I am using the Redgate SQL Backup UI to create the job schedules. / comments
I had other backups failing with the same errors as in my first post; we resolved them by adding the Skipchecks registry entry. For the answer to your question, I am using the Redgate SQL Backup UI...
Thanks, Dan. I'll check out the article. Tony / comments
Thanks, Dan. I'll check out the article.Tony
Well, after tinkering some more with settings and permissions, the backup is now working. I assigned the cld\gss_npsql login sysadmin permissions and it now works. However, on the Dev instance, this login does not have sysadmin permissions and works (with similar database configurations). I don't understand, but now it works. I have another question that came up during all of this testing. Why does SQL Backup use the account configured for the SQL Server Agent service instead of the account configured for the SQL Backup agent service? / comments
Well, after tinkering some more with settings and permissions, the backup is now working. I assigned the cld\gss_npsql login sysadmin permissions and it now works. However, on the Dev instance, thi...
Thanks for the reply. There is a RegSrvr.xml file under the first path you listed in your reply, but the app doesn't appear to be reading it. I do not have a RegSrvr.xml file under the second path you listed. / comments
Thanks for the reply. There is a RegSrvr.xml file under the first path you listed in your reply, but the app doesn't appear to be reading it. I do not have a RegSrvr.xml file under the second path ...
Thank you for your reply. It appears we have our backups configured correctly. I want to ask again a question that was not answered. For our Redgate backup jobs for TDE-enabled databases using native SQL Server compression, our full backups are being compressed, but our transaction log backups are not compressed. Is this expected and why? / comments
Thank you for your reply. It appears we have our backups configured correctly. I want to ask again a question that was not answered. For our Redgate backup jobs for TDE-enabled databases using nati...
We recently implemented TDE for all of our SQL Server databases. Afterwards, we began receiving a warning from SQL Backup to use native compression, so we checked that box in the backup job configuration window which disabled Redgate compression and should be using native SQL Server backup compression. We are using SQL Backup version 10.1.24.2187 and SQL Server 2019 (latest or near to the latest CUs). I have read through this post, and I think we have SQL Backup configured as discussed above. A registry change is mentioned in the post; is it still needed? For our backup files, our full backups are being compressed, but our transaction log backups are not compressed. Is this expected? Also, I can't find Redgate SQL Backup documentation with specific instructions on backing up and compressing TDE enabled databases. If there is one, please provide a link. If not, please ask your documentation department to write one. Thanks. / comments
We recently implemented TDE for all of our SQL Server databases. Afterwards, we began receiving a warning from SQL Backup to use native compression, so we checked that box in the backup job configu...