Comments
Sort by recent activity
I figured it out. The gmsa account didn't have Server Administrator access. Everything cleared up after that. Issue resolved. Hoping this lengthy ramble helps someone else down the road. / comments
I figured it out.The gmsa account didn't have Server Administrator access. Everything cleared up after that.Issue resolved. Hoping this lengthy ramble helps someone else down the road.
Is it perhaps that the gmsa running the service likely doesn't have any access to the SQL instance hosting the SQLBackup repository database (it's on a different instance the the one I'm trying to backup).? I'll bet that's it, and it's what I'm working on now. I'd appreciate any other suggestions. --update-- Ignore this. There is no SQLBackup repository. I was getting it confused with the SQL Monitor repository. / comments
Is it perhaps that the gmsa running the service likely doesn't have any access to the SQL instance hosting the SQLBackup repository database (it's on a different instance the the one I'm trying to...
The problem was indeed the SQL Backup license on that server...just like the error message said. Thanks RedGate for the support. / comments
The problem was indeed the SQL Backup license on that server...just like the error message said.Thanks RedGate for the support.
This is still a mystery. Perhaps I missed something in the original config. Regardless, using the GUI I have revised all of my backups to be encrypted and it appears to be working as I expected. Chalk this one up to user error I guess. / comments
This is still a mystery. Perhaps I missed something in the original config.Regardless, using the GUI I have revised all of my backups to be encrypted and it appears to be working as I expected.Chal...
Thanks Petey2. It's late. I'll get back to you Monday. Thanks for the help. / comments
Thanks Petey2. It's late. I'll get back to you Monday. Thanks for the help.
Sorry. Had trouble finding it. Then I recalled that it's set up as FULL COPY ONLY, so it's not in the log. / comments
Sorry. Had trouble finding it. Then I recalled that it's set up as FULL COPY ONLY, so it's not in the log.
Thanks for the response. I did run the script you provided, and the results indicate that I used the wrong password. SQL Backup v10.0.12.1149 ------------------------------------------------------------------------------ Reading SQB file header of "D:\Temp\filename_here.sqb" Wrong password entered. SQL Backup exit code: 710 I must be missing something somewhere. / comments
Thanks for the response.I did run the script you provided, and the results indicate that I used the wrong password.SQL Backup v10.0.12.1149----------------------------------------------------------...
When I run this query against the instance where I attempted the restore (that failed), I get zero results. Did you intend to have me run this against the instance that created the backup? / comments
When I run this query against the instance where I attempted the restore (that failed), I get zero results.Did you intend to have me run this against the instance that created the backup?