Comments
Sort by recent activity
Thanks Jason I have been in contact with support with call ref F0005120 and provided the following extra info, but have not had any feedback for a while now.
I tested the saving of templates on another server which we have SQLBackup running on and found that the template does save correctly. I see the template information gets saved into the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettings\(LOCAL).
The server I am experiencing an issue with is configured differently as it is using a 3rd party product (PolyServe) to provide a type of clustering for SQL Server instances. This software basically virtualises the SQL Server instance. When it does this it changes the server name in the SQL Server serverproperty value.
So the servers NETBIOS name is MEDPOL1 but SQL Server serverproperty is set to MEDSQLVM01. The instance is then attached to this virtual server ie MEDSQLVM01\INSTA
When I save a template on this server nothing is getting created in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettings\. It stays totally blank even though the job states that the template was saved successfully which is slighty confusing.
I think it might be our 3rd party software causing this issue with the templates not being saved. The other thing that is different between this server and the one I successfully saved the template on is that it is Windows Server 2003 x64 edition. / comments
Thanks Jason I have been in contact with support with call ref F0005120 and provided the following extra info, but have not had any feedback for a while now.
I tested the saving of templates on ano...
For completeness the resolution to this issue is that the account that backup is running under requires permissions to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsand not the user account running the GUI.
If it does not have permissions it will still display as the template saving successfully even though it fails. / comments
For completeness the resolution to this issue is that the account that backup is running under requires permissions to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSetting...
Just to update this thread v10.2.0.885 released on August 6th appears to have resolved this issue / comments
Just to update this thread v10.2.0.885 released on August 6th appears to have resolved this issue
No worries, glad you guys are still supporting 2000. Trying to get rid of our 2000 instances but 1 or 2 just wont die.
Please can I have a link to the previous version.
Many Thanks / comments
No worries, glad you guys are still supporting 2000. Trying to get rid of our 2000 instances but 1 or 2 just wont die.
Please can I have a link to the previous version.
Many Thanks
Will cross reference the clock skew alert times with the performance on the server and see if there is any correlation. / comments
Will cross reference the clock skew alert times with the performance on the server and see if there is any correlation.
Just did some more testing.
When I select the create new database radio button the drop down (orginal database data directory) works correctly ie the paths and filenames are correct.
The bug only appears to be when having the overwrite database radio button selected. / comments
Just did some more testing.
When I select the create new database radio button the drop down (orginal database data directory) works correctly ie the paths and filenames are correct.
The bug only a...
I agree with David
When selecting SQL Server Data Directory it should default to the SQL Server settings (specifically it should pick up the log location). [image]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup\SQLDataRoot]
=E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
This appears to be missing the final folder \DATA.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\DefaultLog]
F:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA
When chossing original database directory it should be
Database file locations from the database being overwritten. / comments
I agree with David
When selecting SQL Server Data Directory it should default to the SQL Server settings (specifically it should pick up the log location).
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi...
Hi Matt,
Tested this and working as expected now. Tried it on a few different configurations (2005 & 2008, default instance and named instance) and all ok.
Just curious that the fix appears to be in the GUI but the download also updates the agent? ie with the 6.5.0.75 GUI the funcationality works as expected even on 6.5.0.73 agents? Any reason for this.
Many thanks
Andy / comments
Hi Matt,
Tested this and working as expected now. Tried it on a few different configurations (2005 & 2008, default instance and named instance) and all ok.
Just curious that the fix appears to be ...
Tried this on a SQL Server 2008 and SQL Server 2005 instance and both have the same issue / comments
Tried this on a SQL Server 2008 and SQL Server 2005 instance and both have the same issue
It looks as if it nearly works.
When selecting Original Database Data Directory it is correctly changing the Transaction Logs path to F:\Program Files\Microsoft SQL Server\....
The problem is the Primary database file path and name (screenshot 2), it changes it to
Path
E:\Program Files\Microsoft SQL Server\MSSQL10.INSTC\MSSQL
File Name
DATA (this is totally wrong and is the end of the folder path)
It should read
Path
E:\Program Files\Microsoft SQL Server\MSSQL10.INSTC\MSSQL\DATA
File name
BGInfo.MDF / comments
It looks as if it nearly works.
When selecting Original Database Data Directory it is correctly changing the Transaction Logs path to F:\Program Files\Microsoft SQL Server\....
The problem is the P...