Comments
1 comment
-
A couple of other users had experienced the same issue, and we have addressed it with a patch (6.4.0.1010). In both cases, the trailing space was a mistake, and the issue was resolved by renaming the database. If however the trailing space is significant, you can request Product Support to send you details on where to download patch 6.4.0.1010 from.
The fix will be included in future releases of SQL Backup.
Thank you.
Add comment
Please sign in to leave a comment.
Finally, I tried doing a Red Gate SQL Backup Backup, with NO encryption. It backed up fine. The auto name convention I am using exposed that there was an extrax space, or blank, in the backup file name. D'OH! That let me remember the bug from 5.x. I verified that there was indeed a hidden, trailing space in the db name, and renamed it without that space. Issue resolved!
Please see what you can do to avoid the issue for others.
Thanks,
Dan W