Comments
Sort by recent activity
Is this true encryption of the entire file? I'm just a little skeptical, since Microsoft can't make encryption and compression work together in SQL Server 2008. / comments
Is this true encryption of the entire file? I'm just a little skeptical, since Microsoft can't make encryption and compression work together in SQL Server 2008.
Thanks for the reply. Honestly, we were thinking about dropping RedGate when we moved to SQL 2008, because Microsoft is implementing compression and encryption finally, but they can't do both at the same time, which made me a little curious. Between the great support we get from RedGate, and the features of the product, we just renewed our licenses for another year. / comments
Thanks for the reply. Honestly, we were thinking about dropping RedGate when we moved to SQL 2008, because Microsoft is implementing compression and encryption finally, but they can't do both at th...
That is excellent news! / comments
That is excellent news!
Mostly business driver. We have white papers that we present to our customers that detail the security measures we employ in our operations. The savvy customer sees the section on FIPS security, and asks if we are using FIPS certified products or products that use FIPS approved algorithms, knowing that a poor implementation of a secure algorithm can be worse than a good implementation of a more secure one. You're far from alone in not having FIPS certification though. Out of 7 products that we use for various tasks that employ encryption, only one is FIPS certified, and it is a VPN concentrator. All of the rest point to their use of AES, the NIST-approved algorithm. Common Criteria has a little better results in terms of number of approved products, but it is also probably much more inexpensive to obtain, compared with FIPS 140. / comments
Mostly business driver. We have white papers that we present to our customers that detail the security measures we employ in our operations. The savvy customer sees the section on FIPS security, an...
Thank you, I will do that.
eddie davis wrote:
Hi,
sorry that you are getting this problem.
A support call has been created for this call. Call Reference F0009695.
Can you please send an e-mail to support@red-gate.com and attach a copy of the SQL Backup Log file for this failing job. SQL Backup creates a log file for each backup/restore job ran. By default the SQL Backup Log File is located in the following directory:
C:\Documents and settings\All Users\Application Data\Red Gate\SQL Backup\Log\(local) or SQL Instance Name.
Also can you please include the call reference in the subject of the e-mail.
Many Thanks
Eddie
Eddie Davis
Technical Support Engineer
Red Gate Software Ltd
E-Mail: support@red-gate.com
/ comments
Thank you, I will do that.
eddie davis wrote:
Hi,
sorry that you are getting this problem.
A support call has been created for this call. Call Reference F0009695.
Can you please send an e-mail to...
Thank you for the quick response! So, if I use FILEOPTIONS = 1, it will apply the same delete parameters to both locations? Ok, so I guess my request now becomes that this option be added to the GUI. That's typically how I create all of my jobs if possible, which is why I thought that option wasn't available.
Brian Donahue wrote:
Hi,
Thanks for your feedback. I'd just like to point out that it is possible to have files automatically deleted from a COPYTO location using the FILEOPTIONS parameter in the SQL Backup command.
FILEOPTIONS=1 will apply erasefiles to the primary backup location and any copyto or moveto location simultaneously. FILEOPTIONS=2 will only delete the files if the archive bit is clear (ie they have been backed up to tape).
/ comments
Thank you for the quick response! So, if I use FILEOPTIONS = 1, it will apply the same delete parameters to both locations? Ok, so I guess my request now becomes that this option be added to the GU...
Ok, you got me pointed in the right direction and I got it figured out. It was:
query10 = "-SQL ""RESTORE DATABASE " & myString6 & " FROM DISK = 'G:\myFiles\CompressedBackups" & myFile6 & "' WITH MOVE '" & myString6 & "' TO 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data" & myString6 & ".mdf', MOVE '" & myString6 & "_LOG' TO 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data" & myString6 & ".ldf', MAILTO='myemail@mydomain.com', THREADPRIORITY=6 "" -I sql -U user -P password "
The comma before the MAILTO was needed to make it a continuation of the previous WITH statement. Thanks for your help. It was really confusing getting the single quotes, double quotes, two sets of double quotes, etc. all figured out to make this work.
Jason Cook wrote:
Hi,
The generated command will not function correctly because of confusion between the various tags.
Any part of the SQL Backup command needs to go inside the -SQL "..." tag, and the -I, -U and -P tags come afterwards.
So in your example, this should be:
query10 = "-SQL ""RESTORE DATABASE " & myString6 & " FROM DISK = 'G:\myFiles\CompressedBackups" & myFile6 & "' WITH MOVE '" & myString6 & "' TO 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data" & myString6 & ".mdf', MOVE '" & myString6 & "_LOG' TO 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data" & myString6 & ".ldf' WITH MAILTO='myemail@mydomain.com', THREADPRIORITY=6"" -I sql -U user -P password "
Hope that helps,
Jason
/ comments
Ok, you got me pointed in the right direction and I got it figured out. It was:
query10 = "-SQL ""RESTORE DATABASE " & myString6 & " FROM DISK = 'G:\myFiles\CompressedBackups" & myFile6 & "' WITH M...
thank you for the suggestions and links. My script is definetly not VB.Net. I'm behind in my learning. But if I get into a lot more scripting, I would like to get up to date with the new options that are available with the newer scripting languages.
Jason Cook wrote:
Indeed, my mistake... didn't spot that you had two "WITH" statements as well. Of course should only have a maximum of one.
Not sure what version of VB you are using, but if you are using .NET, you could use the String.Format function to try and make the code easier to understand (if you have to do this again in the future):
For example, your code would become something like:
query10 = String.Format(@ -SQL "RESTORE DATABASE {0} FROM DISK = 'G:\myFiles\CompressedBackups\{1}' WITH MOVE '{0}' TO 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\{0}.mdf', MOVE '{0}_LOG' TO 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\{0}.ldf', MAILTO='myemail@mydomain.com', THREADPRIORITY=6 "" -I sql -U user -P password",myString6,myFile6);
Granted it's still not ideal, but it's eliminated a significant number of the double quotes... so seems slightly less complicated. The following link may be useful (mentions C#, but should be the same in VB.net): http://blog.stevex.net/index.php/string ... in-csharp/
Hope that helps,
Jason
/ comments
thank you for the suggestions and links. My script is definetly not VB.Net. I'm behind in my learning. But if I get into a lot more scripting, I would like to get up to date with the new options th...
Thanks for the help. I think I've figured out the problem now. Our mail servers block emails that don't have a FQN in the From field. The default for SQLBackup uses SQLBackup@servername or something like that. I changed it to servername@ourdomain.com and it worked fine. I thought at first maybe I needed to specify the parameters at the command line. The test emails worked from the GUI, and in a couple of hours the SQLBackupC jobs will have run, and I'll know if it working properly or not.
Thanks!
petey wrote:
The command line interface uses the settings you specified using the GUI, thus you do not need to provide the mail server settings.
One difference when using the command line interface is that all the work will be performed using the credentials of the logged-on user. When using the extended stored procedure, all work is performed using the credentials of the SQL Backup service startup user.
/ comments
Thanks for the help. I think I've figured out the problem now. Our mail servers block emails that don't have a FQN in the From field. The default for SQLBackup uses SQLBackup@servername or somethin...
When I try that I get a syntax error, and SQL Backup exit code: 500.
Jason Cook wrote:
Hi,
The generated command will not function correctly because of confusion between the various tags.
Any part of the SQL Backup command needs to go inside the -SQL "..." tag, and the -I, -U and -P tags come afterwards.
So in your example, this should be:
query10 = "-SQL ""RESTORE DATABASE " & myString6 & " FROM DISK = 'G:\myFiles\CompressedBackups" & myFile6 & "' WITH MOVE '" & myString6 & "' TO 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data" & myString6 & ".mdf', MOVE '" & myString6 & "_LOG' TO 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data" & myString6 & ".ldf' WITH MAILTO='myemail@mydomain.com', THREADPRIORITY=6"" -I sql -U user -P password "
Hope that helps,
Jason
/ comments
When I try that I get a syntax error, and SQL Backup exit code: 500.
Jason Cook wrote:
Hi,
The generated command will not function correctly because of confusion between the various tags.
Any part...