Comments
Sort by recent activity
Hi Tim,
If you specify the MAILTO, MAILTO_ONERRORONLY, or MAILTO_ONERROR keywords as part of the restore command SQL Backup uses, then SQL Backup ought to send out an email with the password obfuscated. This should be exactly the same as performing a restore from the GUI.
If you send out an email from SQL Server containing the command string used (for example), then I'm afraid it will necessarily have the password used in plain text.
Thank you for raising this issue. I think its fair to say that this usecase wasn't considered when we first removed the encrypted password in restore commands. Although its unlikely that we will implement a similar feature for the forthcoming release I hope we can do something to help in a future release. As Priya mentioned earlier in this thread, its quite possible that a 'scheduled restore' wizard might be added to SQL Backup in an upcoming version. / comments
Hi Tim,
If you specify the MAILTO, MAILTO_ONERRORONLY, or MAILTO_ONERROR keywords as part of the restore command SQL Backup uses, then SQL Backup ought to send out an email with the password obfusc...
Hi Tim,
I was under the impression that the automated emails sent by SQL Backup for restores obfuscated the password; when I run a restore with a MAILTO command, it shows the password as:
... PASSWORD = 'XXXXXXXXXX', ...
Is this the scenario you were talking about? Or is there a different case we aren't aware of? I'd certainly agree that sending out passwords in clear text would be a serious security issue.
Thanks for the feedback, / comments
Hi Tim,
I was under the impression that the automated emails sent by SQL Backup for restores obfuscated the password; when I run a restore with a MAILTO command, it shows the password as:
... PASSW...
Hi Andrew,
Thanks a lot for getting back to us,
I believe you've reproduced a bug here that we've seen previously. Could you please try removing any old backup files (from SQL Backup 5.4 or earlier) from the folder you're backing up to, and then run the same command again. If I'm right, the error message should stop happening then.
We have fixed this issue for the 6.0 release in our internal builds, so it shouldn't affect anyone when the final release comes out. / comments
Hi Andrew,
Thanks a lot for getting back to us,
I believe you've reproduced a bug here that we've seen previously. Could you please try removing any old backup files (from SQL Backup 5.4 or earlie...
Thanks for the feedback. I agree that the file browser functionality isn't right coming from the restore wizard. I've raised a bug internally about this, so I hope we can get the fix into the forthcoming release. / comments
Thanks for the feedback. I agree that the file browser functionality isn't right coming from the restore wizard. I've raised a bug internally about this, so I hope we can get the fix into the for...
Hi Jonathan,
I had seen this previously in testing, but have had real trouble reproducing the problem. Could you show me the command run by the offending job? If you'd rather not post it in the forum, you can email me on backup.prerelease@red-gate.com
Thank you, / comments
Hi Jonathan,
I had seen this previously in testing, but have had real trouble reproducing the problem. Could you show me the command run by the offending job? If you'd rather not post it in the f...
Hello,
You're quite right that the duration column of the activity history just shows the time taken for the backup part of the task - not the copy or verify parts. This was also the case in SQL Backup 5.
Out of interest, it sounds like your job spent a lot of time copying/verifying compared to the time taken to back up. Could I ask if this performance is typical compared to what you would expect from SQL Backup version 5, or whether its taking more time than you would normally have expected?
Thanks for the feedback, / comments
Hello,
You're quite right that the duration column of the activity history just shows the time taken for the backup part of the task - not the copy or verify parts. This was also the case in SQL B...
I'm afraid this is happening on the pre-release build with all encrypted backups version 5.4 or earlier. We've raised this internally so it will be fixed for the final release.
Sorry for the inconvenience! / comments
I'm afraid this is happening on the pre-release build with all encrypted backups version 5.4 or earlier. We've raised this internally so it will be fixed for the final release.
Sorry for the incon...
Hi William,
Thanks for the feedback; its great that you're pleased with so many of the new features!
As for your dislikes:
I think its pretty unlikely that we will be able to implement changes for 1), 2) or 3) for the next release, but we'll be sure to look into these feature requests going forward. In particular, I think that moving servers between location tabs would be a great feature to have.
A scheduled restore wizard was strongly considered for this release, but in the end we decided not to include it. Its quite possible that this will be included in a future release.
And finally, 'Log Copy Queue' should definitely have been listed under 'View'! I've now raised a bug about this, and I'm sure it will be there in the final release. Let's chalk this one up to substandard testing [image] / comments
Hi William,
Thanks for the feedback; its great that you're pleased with so many of the new features!
As for your dislikes:
I think its pretty unlikely that we will be able to implement changes for ...
Hi Andy,
I can confirm that you will be able to deactivate licenses remotely.
As for centralized license management, I'm afraid there aren't currently any plans to implement this for the next release, but we'll be sure to review this feature for releases in the future.
Many thanks for your feedback, / comments
Hi Andy,
I can confirm that you will be able to deactivate licenses remotely.
As for centralized license management, I'm afraid there aren't currently any plans to implement this for the next relea...
Hi Dan,
Thanks for raising this with us. I can reproduce this on a test machine here.
Clearly this is a serious issue, and we will want to fix it before the final release. For the time being, I hope you can carry on using the pre-release without too much inconvenience. As you saw, a work-around is to manually remove 5.3 backups from the folders you are backing up to.
Thanks again!
Matt Chandler,
Software tester on SQL Backup / comments
Hi Dan,
Thanks for raising this with us. I can reproduce this on a test machine here.
Clearly this is a serious issue, and we will want to fix it before the final release. For the time being, I h...