When does an alert get raised after a copy failure?

November 28, 2013, 8:00 am

≪ Previous: RE: SQL Backup failed with exit code: 669

Hi, what is the trigger for an alert being raised after a backup copy to a network location fails? Is it after the retry interval and retry amounts have all be exhausted? Or does the alert get raised on the first time a copy to a network share fails, and then the retries will still continue?

Thanks.

↧

RE: Please STOP auto-refresh!

November 29, 2013, 1:42 am

≫ Next: RE: Please STOP auto-refresh!

≪ Previous: When does an alert get raised after a copy failure?

Hi

Thank you for your forum post.

A support call has been created for you the call reference is 8828. I have added the details of the support call and this forum post to an existing Bug Report / Feature Request whose reference is SB-3123. I will request the SQL Backup Product Manager to review SB-3123.

I will also provide an update to you from our call logging system.

Many Thanks
Eddie

↧

RE: Please STOP auto-refresh!

November 29, 2013, 12:44 pm

≫ Next: RE: When does an alert get raised after a copy failure?

≪ Previous: RE: Please STOP auto-refresh!

I second that request. I do have a cluegy work around but agree it would be better if they stop running auto refresh and turn off client side caching altogether. It's much faster to just query the data you need from the server when you need it. Especially when you have many instances and databases.

Here is the work around: Create a group for each instance and put the instance in that group.

I know, this is a real pain to do, but at least auto refresh does not kick in until you open the given group.

↧

RE: When does an alert get raised after a copy failure?

December 1, 2013, 5:00 pm

≫ Next: SQL Backup 7.6

≪ Previous: RE: Please STOP auto-refresh!

The error is raised only after the retry amounts have been exhausted.

↧

SQL Backup 7.6

December 4, 2013, 7:09 am

≫ Next: Error When Upgrading Server Components

≪ Previous: RE: When does an alert get raised after a copy failure?

SQL Backup 7.6 has been released.

This release addresses a security vulnerability identified in SQL Backup 7.4 and 7.5. For more information, see http://www.red-gate.com/sqb76security.

It also includes the enhancements and fixes previously released as SQL Backup 7.5.

SQL Backup 7.6 is a free upgrade from versions 7.0, 7.1, 7.2, 7.3, 7.4 and 7.5. To upgrade, from the Help menu select Check for Updates or download a trial from the SQL Backup page and use your serial number to activate.

User interface version: 7.6.0.26 (to check the version number, from the Help menu select About SQL Backup).

Server components version: 7.6.0.29 (to check the version number, from the Edit menu select Properties).

↧

Error When Upgrading Server Components

December 4, 2013, 10:09 am

≫ Next: SQL error 3013 Backup Database is terminating abnormally

≪ Previous: SQL Backup 7.6

Hi

I upgraded the GUI on my laptop to version 7.6 this afternoon, and subsequently updated the server components on one of my servers.

I then tried the second server, and got an error - code 262144.

When I checked the web page that the error linked to, it said:

Quote:

The version of the SQL Backup Pro extended stored procedure dynamic-link library (xp_sqlbackup.dll) is incorrect.

How do I get hold of the correct version of the DLL - can I just copy it from my other server, or do I need to do a full re-install? I'd rather not have to take this approach if it means that I have to re-build all of my log ship jobs.

Thanks

Ben

↧

SQL error 3013 Backup Database is terminating abnormally

December 4, 2013, 11:51 am

≫ Next: SQL error 3013 Backup Database is terminating abnormally

≪ Previous: Error When Upgrading Server Components

We have a backup job which backing up 5 databases and 4 out of 5 as are running OK. however one database keep failing for full and increment too.

Searched forum for error code. and there was one topic which has same error but it also has a line for memory issue. however there is no mention for memory so I created new topic.

Can you take a look at this log please?

SQL error 3013: BACKUP DATABASE is terminating abnormally.
SQL error 3271: A nonrecoverable I/O error occurred on file "SQLBACKUP_02C205BD-4A11-431F-AF1A-84F77F20BA3F:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQL error 3043: BACKUP 'Interfax' detected an error on page (1:8650358) in file 'G:\Data\Interfax_DataNew.MDF'.
Thread 0 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 1 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 2 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 3 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 4 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 5 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 6 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 7 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 8 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 9 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 10 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 11 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 12 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 13 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
Thread 14 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)

↧

SQL error 3013 Backup Database is terminating abnormally

December 4, 2013, 11:51 am

≫ Next: RE: Error When Upgrading Server Components

≪ Previous: SQL error 3013 Backup Database is terminating abnormally

↧

RE: Error When Upgrading Server Components

December 5, 2013, 1:09 pm

≫ Next: RE: Error When Upgrading Server Components

≪ Previous: SQL error 3013 Backup Database is terminating abnormally

You can uninstall the SQL Backup Server Components without it affecting your SQL Backup Scheduled jobs. It will mean that any jobs that try to run when the components are not present will fail, but once they have been re-installed these jobs should run successfully.

First copy the SQBServerSetup.exe file, which can be found in the SQL Backup UI installation folder, to the machine hosting the SQL Server instance. Then uninstall the existing components, once complete, execute the .exe.

↧

RE: Error When Upgrading Server Components

December 5, 2013, 2:27 pm

≫ Next: RE: SQL error 3013 Backup Database is terminating abnormally

≪ Previous: RE: Error When Upgrading Server Components

Thanks Chris

Do I need to de-activate the licence first before uninstalling so that I can re-install on the same licence key?

Thanks

Ben

↧

RE: SQL error 3013 Backup Database is terminating abnormally

December 9, 2013, 5:52 am

≫ Next: Object level Recovery Error using Backup SQL 7.3

≪ Previous: RE: Error When Upgrading Server Components

Based on the following in the output:

Quote:

SQL error 3043: BACKUP 'Interfax' detected an error on page (1:8650358) in file 'G:\Data\Interfax_DataNew.MDF'.

It looks like your database has a consistency issue. Try running DBCC CHECKDB on that database to see if the same error is reported.

↧

Object level Recovery Error using Backup SQL 7.3

December 9, 2013, 12:42 pm

≫ Next: RE: Object level Recovery Error using Backup SQL 7.3

≪ Previous: RE: SQL error 3013 Backup Database is terminating abnormally

Hi,

error is:
redgate unable to get pfs page

Restoring Database with no encryption, no checking, is it a bug?

I tried different drives with same result, full DB recovery went ok.

Thank You

↧

RE: Object level Recovery Error using Backup SQL 7.3

December 10, 2013, 2:42 pm

≫ Next: RE: Error When Upgrading Server Components

≪ Previous: Object level Recovery Error using Backup SQL 7.3

Sorry you are experiencing this.
It appears you are running into a known issue under the internal reference number of OLR-200.
Unfortunately I am unable to provide a definitive timeline for when this may be fixed.

↧

RE: Error When Upgrading Server Components

December 11, 2013, 4:38 am

≫ Next: Licensing.

≪ Previous: RE: Object level Recovery Error using Backup SQL 7.3

Assuming that the hardware stays the same, then deactivation is not necessary.

↧

Licensing.

December 12, 2013, 12:22 pm

≫ Next: RE: Licensing.

≪ Previous: RE: Error When Upgrading Server Components

How does the SQL Backup Pro licensing works?

I know there are 2 pieces - client and server to the SQL Backup Pro.
1) Is the license just for the client?
2) Are there limitations to number of sql server instances? Or is this a question for our contract? I think we have the SQL Toolbelt http://www.red-gate.com/products/sql-development/sql-toolbelt/

Thanks!

↧

RE: Licensing.

December 12, 2013, 12:47 pm

≫ Next: RE: Licensing.

≪ Previous: Licensing.

I think I found it ... http://documentation.red-gate.com/display/SBU7/Installing#

↧

RE: Licensing.

December 12, 2013, 12:50 pm

≫ Next: RE: Licensing.

≪ Previous: RE: Licensing.

What happens if we need to test restores of our backups to a different server? We're going to need to install the server component to the other server. Is that a violation of the licensing if we only have 1 license for server component?

↧

RE: Licensing.

December 13, 2013, 6:14 pm

≫ Next: RE: Error When Upgrading Server Components

≪ Previous: RE: Licensing.

I would suggest contacting your Red Gate sales representative to see if they can set you up with a 'restore only' license, or you could just write directly to sales@red-gate.com to explain your needs. In the meantime, you could use a trial license on the other server to test your restores.

Another option, space and time permitting, is to convert the SQL Backup backup file to a native SQL Server backup file using the SQL Backup conversion utilities (no license required), and restore from the native backup file.

↧

RE: Error When Upgrading Server Components

December 16, 2013, 3:06 am

≫ Next: RE: Licensing.

≪ Previous: RE: Licensing.

Quick update:

I managed to upgrade the components without uninstalling in the end. The server was rebooted as part of a maintenance outage, and subsequent to this, the software upgraded with no issues.

Thanks

Ben

↧

RE: Licensing.

December 16, 2013, 8:44 am

≫ Next: RE: Licensing.

≪ Previous: RE: Error When Upgrading Server Components

I have read somewhere that there are tools that will verify the backup file without actual test restores.
Does Red-Gate SQL Backup Pro requires an actual test restores to verify the backup file?

Where can I download SQL Backup Conversion Utilities?
Edit: Found it on C:\Program Files (x86)\Red Gate\SQL Backup 7 but it kept error out with: "SQBConverterGUI has stopped working"

with options to close the program or debug the program.

↧

Latest Images