Comments
Sort by recent activity
Hi
Can you please try the following steps below to resolve this issue:
1. Close the SQL Backup GUI.
2. On the SQL Server server you are attempting to connect too, stop and restart the SQL Backup Agent service.
3. Once the service has restarted, open the GUI and attempt to reconnect to the registered server.
I have known this type of error to occur if there are any changes to the SQL Backup Agent Service, for example changing the account name or changing the password for the account name. Closing the GUI and restarting the service in a majority of cases resolves this problem.
Many Thanks
Eddie / comments
Hi
Can you please try the following steps below to resolve this issue:
1. Close the SQL Backup GUI.
2. On the SQL Server server you are attempting to connect too, stop and restart the SQL Backup ...
Thank you for your post into the forum.
I suspect that the SQL Backup Test Utilities available in the SBaTU.exe do not support the file format change introduced in SQL Backup V6.
As workaround, you can use the SQBConverterGUI.exe to convert a copy of the backup file into V5 format and then run the SBaTU.exe at the converted file. You will find the SQBConverterGUI.exe on a machine with the SQL Backup GUI instaled in the installation folder '\Program files\Red Gate\SQL Backup 6.
Meanwhile I will check with the development team to see if there is an updated version of the SQL Backup Test Utilities available.
Many Thanks
Eddie / comments
Thank you for your post into the forum.
I suspect that the SQL Backup Test Utilities available in the SBaTU.exe do not support the file format change introduced in SQL Backup V6.
As workaround, you...
Thank you for your post into the forum.
I believe that you may have already contacted Red Gate Product Support Team and opened a support ticket, call reference F0027852.
I have just replied to you.
Many Thanks
Eddie / comments
Thank you for your post into the forum.
I believe that you may have already contacted Red Gate Product Support Team and opened a support ticket, call reference F0027852.
I have just replied to you....
Thank you for your post into the forum.
One possible use of the standby or destination database in a Log Shipping setup, is to have the database used for reporting purposes configured using the WITH STANDBY recovery model.
You will need to be aware, depending on how frequent you wish to restore additional log files to the destination database. If you have a user connected to the database, the restore process will fail due to the well known Exclusive Access could not be obtained, SQL Error 3101.
The restore process requires exclusive access to the database, so to restore additional files to the database you must wait for all users connected have finished using the database.
Alternatively you can use the 'Kill any existing connections to the database' option when performing a restore. However, you may annoy connected users who are running long queries to obtain the data they are seeking for their report.
Are there any Red Gate SQL Backup users that have 'real world' examples or experiences to share using a Log Shipped Read-Only database?
Many Thanks
Eddie / comments
Thank you for your post into the forum.
One possible use of the standby or destination database in a Log Shipping setup, is to have the database used for reporting purposes configured using the WIT...
Thank you for your post into the forum.
On a machine with the SQL Backup GUI 5.4 installed, locate an executable called SQBServerSetup.exe. By default you will find the file in the following directory:
C:\Program Files\Red Gate\SQL Backup
Copy the SQBServerSetup.exe file to your SQL Server 2008/x64 machine and run the executable.
In most circumstances the above action successfully resovles the issue you have reported.
Please reply if the above fails or you need further assistance.
Many Thanks
Eddie / comments
Thank you for your post into the forum.
On a machine with the SQL Backup GUI 5.4 installed, locate an executable called SQBServerSetup.exe. By default you will find the file in the following direc...
Thank you for your into the forum.
I am little puzzled by your question:
I need to put some objects on the destination server, but are not yet currently on the source server.
I am assuming you mean destination database and source database.
SQL Server will not allow you to create new objects on the log shipped destination database.
In a Log Shipping setup, the transaction log backups are restored to the destination database using one of the two recovery states:
WITH NORECOVERY - Database is non-operational. When the log restore is complete, the database is not returned to ready operational status and it cannot be used for normal operations. You can continue to restore transaction log backup files. Therefore you will be unable to create new objects on the database.
WITH STANDBY - Database is in a Read Only condition. This is similar to the non-operational condition with some exceptions. When the restore process ends, the database is placed nto Read-Only mode. It is available to accept additional transaction log backups. In Read-only mode you can query the database but you cannot modify the database or add new objects to the database.
If you create new objects in the source database, these actions are recorded in the Transaction Log which is log shipped for restore to the destination database. When you recover the target database and make it operational these new objects will be available in the destination database.
To summarise the above, you cannot create new objects and modify or delete existing objects in the destination database in a Log Shipping set-up.
Many Thanks
Eddie / comments
Thank you for your into the forum.
I am little puzzled by your question:
I need to put some objects on the destination server, but are not yet currently on the source server.
I am assuming you ...
As per the support call created for you.
By default SQL Compare does not have option to encrypt the connection string.
When you start up SQL Compare, Project Configuration - Data Sources Tab.
Enter the server name, you could try entering the following to force an encrypted connection:
Default Instance
<Server Name>;ENCRYPT=TRUE;TRUSTSERVERCERTIFICATE=TRUE
Named Instance
<Server Name>\<Instance Name>;ENCRYPT=TRUE;TRUSTSERVERCERTIFICATE=TRUE
Or if server is not running on the default SQL Port 1433,
<Server Name>,<port number>;ENCRYPT=TRUE;TRUSTSERVERCERTIFICATE=TRUE
<Server Name>\<Instance Name>,<port number>;ENCRYPT=TRUE;TRUSTSERVERCERTIFICATE=TRUE
Many Thanks
Eddie / comments
As per the support call created for you.
By default SQL Compare does not have option to encrypt the connection string.
When you start up SQL Compare, Project Configuration - Data Sources Tab.
Enter...
Thank you for your post into the forum.
New to SQL Backup V6, users can create a new registry key and list the user accounts that are able to browse.
The Registry value name is BrowsingUserList. Key type is either REG_SZ (single value) or REG_MULTI_SZ (multiple names) and the value data list the user names or names and must be in the DOMAIN\user format.
Can you please try configuring the above registry on the SQL Server with SQL Backup Server Components installed in the following registry directory:
HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\(local) or SQL Instance Name
Many Thanks
Eddie / comments
Thank you for your post into the forum.
New to SQL Backup V6, users can create a new registry key and list the user accounts that are able to browse.
The Registry value name is BrowsingUserList. Ke...
Thank you for your reply.
The answer to your question is no. The SQL Backup download will remain at V6.2.0.134 until the release of SQL backup V6.3 and therefore will not be part of the 'Check for updates' process.
Many Thanks
Eddie / comments
Thank you for your reply.
The answer to your question is no. The SQL Backup download will remain at V6.2.0.134 until the release of SQL backup V6.3 and therefore will not be part of the 'Check for...
Thank you both for your posts into the forum.
Unfortunately SQL Backup V6.0 through to V6.2.0.134, will not delete backup files created by previous versions, via the ERASEFILES or ERASEFILES_ATSTART.
The good news is there is a patch release of SQL Backup 6.2 that will fix this issue, V6.2.0.1000.
Please use this LINK to download the patch release.
The downloaded zip file contains two files:
SQLBackupC.exe
SQBCoreService.exe
To apply the new files:
1. Ensure that no backup or restore task is running.
2. Stop the SQL backup Agent Service.
3. Navigate to the server componets, by default - C:\Program files\Red Gate\SQL Backup\(local) or SQL Instance.
4. Rename the existing V6.2.0.134 SQLBackupC.exe and SQBCoreService.exe files, for example too OLDSQLBackupC.exe and OLDSQBCoreService.exe.
5. Copy from the extracted zip the V6.2.0.1000 SQLBackupC.exe and SQBCoreService.exe files to the server components installtion folder.
6. Restart the SQL Backup Agent.
7. Ensure that the service starts successful and that you can perform a backup.
I hope the above helps.
Many Thanks
Eddie / comments
Thank you both for your posts into the forum.
Unfortunately SQL Backup V6.0 through to V6.2.0.134, will not delete backup files created by previous versions, via the ERASEFILES or ERASEFILES_ATSTAR...