Quantcast
Channel: Red Gate forums: SQL Backup 7
Viewing all 713 articles
Browse latest View live

RE: Network Copy Location keeps trying to copy to the old path

0
0
When a transaction log is marked to be copied, it is placed in a queue, and the copying performed by a separate process, but still running within the SQL Backup Agent service. The details of the target location is stored at that point in time.

When you changed the target location, it does not update the details of the files already in the queue that are still waiting to be copied. That is why SQL Backup attempts to copy the files to the previous target location. After 24 hours, SQL Backup gives up trying to copy the files.

To address this, you will need to update the target location details manually. You can find details of the files in the backupfiles_copylist table, in the SQL Backup local database (a SQL Server Compact database). You can use the sqbdata extended stored procedure to view the contents e.g.

Code:
EXEC master..sqbdata 'SELECT * FROM backupfiles_copylist'

Those entries with a status of 'P' (Pending) means they have not been copied yet, and copyto indicates the target location. Assuming that your previous location was 'g:\backups\copies\' and you now want to copy to 'h:\sqlbackup\copies\', you can use the REPLACE function via sqbdata to perform the change e.g.

Code:
sqbdata 'UPDATE backupfiles_copylist SET copyto = REPLACE(copyto, ''g:\backups\copies\'', ''h:\sqlbackup\copies\'') WHERE status = ''P'''

Copy job status codes

0
0
When I run

Code:

exec master..sqbdata 'SELECT * FROM backupfiles_copylist where status <> ''s'' order by lastattempt desc'


one of the columns I get back is 'status'. I'm guessing that:

'S' is 'Success' (applied when the copy has succeeded),
'E' is 'Error' (applied after the copy job gives up),
'P' is 'Pending' (applied when the job is queued up but has run yet)

but there seem to be a few others.

What are the possible values, and what do they all mean?

Kitchens In Southwick

RE: Copy job status codes

0
0
A for active, meaning that the file is currently being copied.
C for cancelled, when the source file cannot be found, or when copying to the hosted storage is cancelled.

E for expired, which by default happens 24 hours after the file has been placed in the queue and could not be copied during that interval.

License

0
0
Hi, How do I find out which servers have installed active license (sql backup 7). thanks

RE: License

0
0
Also, I have been deactived some current license from other server and try to active a trial one, but keep getting The number of activations for this serial number has been exceeded message

RE: License

0
0
We will be in touch via email to address this issue you have raised in regards to licensing.

To help us in this matter when you are in receipt of the email are you able to respond back with the requested information?

Thanks for your patience and feedback in this matter.

How can I get the meta data from an SQB file directly?

0
0
How can I get the meta data from an SQB file directly without an instance that has RedGate SQL Backup installed?
I need to get those information directly in an automatic way. After some investigation I can got the LSNs. But I still can't got other information. Please check the following snapshot. Hope you can give me some suggestions.

Thanks.[/img]

backup percent complete

0
0
Does the backup function have the ability to indicate percent completion for long running backups?

RE: backup percent complete

0
0
No it does not. You can run the sqbstatus extended stored procedure to find out how much data has been backed up e.g.

Code:
EXEC master..sqbstatus 1

RE: How can I get the meta data from an SQB file directly?

0
0
server name - offset 294, 164 bytes
82 2-byte character values.

database name - offset 518, 258 bytes
129 2-byte character values.

group ID - offset 288, 4 bytes
4 byte integer value.

backup type - offset 506
1 = full, 2 = differential, 3 = log, 4 = file
14 = file differential, 19 = partial, 20 = differential partial,

native backup size - offset 9, 8 bytes
Is a 64-bit integer value.

database size - offset 1008, 8 bytes
Is a 64-bit integer value.

backup start - offset 17, 8 bytes
8-byte floating point value, where the integer portion represents the number of days since 30 Dec 1899, and the fractional portion represents the fraction of a 24-hour day that has elapsed. If it helps, the range for this data type ranges from 5.0 x 10^-324 to 1.7 x 10^308.

backup end - offset 25, 8 bytes
As above for backup start.

RE: How can I get the meta data from an SQB file directly?

0
0
Thank you very much for providing this information petey!

RE: How can I get the meta data from an SQB file directly?

0
0
petey could you also provide the way to get the data return from "restore filelistonly"? Thanks.

RE: How can I get the meta data from an SQB file directly?

0
0
That isn't possible without SQL Server. One option is to use the SQL Backup converter (SQBConverter.exe) to convert SQL Backup files to native backup files, then use the Express editions of SQL Server to run and return the results of the RESTORE FILELISTONLY command via the command line interface (osql).

RE: How can I get the meta data from an SQB file directly?

0
0
Thanks I'll give it a try.
Smile

Backup 7, (ERR 2006

0
0
I have two servers, with SQL Backup 7.0.0.597. Each has this issue.

I open SQL Backup GUI client. Right-click on server name, select RESTORE. I do drop-down combo box, select BROWSE FOR FILE, then click the ADD FILES... button. I get an error box

--------------------------------------------------------
Object reference not set to an instance of an object.

[chk-box] Ignore this error and attempt to continue.

[Send Error Rpt] button
--------------------------------------------------------

ERR 2006: Could not load file or assembly 'System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.
The system cannot file the file specified @ 0x0011)

Preparing the error report (ERR 2006: WriteStart Document needs to be the first call @ 0x0011)

--------------------------------------------------------

I have tried the "ignore" check box, no difference.

I have done a few "send to RedGate"

Windows 8, SvcPk 2

SQL 2008R2

RE: Backup 7, (ERR 2006

Hanging Wine Racks

0
0
Hanging wine racks are specially produced racks that can be hung up from the ceiling, under cabinets, on walls (although there are special wall wine racks that are constructed differently), or on another piece of high-situated furniture. Aside from the intended purpose, these hanging wine racks have multiple functions; they provide revolving dcor, storage facilitation, and stylish design.

RE: Backup 7, (ERR 2006

0
0
Thanks for your post.

We have logged a support call for you, call reference for which is F0075370.

Issue with Server Component registration v7.3.2.3

0
0
In one of my environments, running a 5 node cluster, I have a single node in this cluster that despite having successfully installed and updated the version of the server components is still showing in the SQL Backup UI as needing an update.

The imagine below confirms that all of the instances hosted on the problem node have the same version of the server components :



This image then shows what the SQL Backup UI is showing. The icon indicating that there is a newer version of the server components is showing and looking at the properties for this node, it shows that the SQL Backup version is still the old version :



Is there somewhere in the file system/registry that I can look at/update to force the SQL Backup UI to see this node as actually being up to date ?
Viewing all 713 articles
Browse latest View live




Latest Images