Are you the publisher? Claim or contact us about this channel

Embed this content in your HTML


Report adult content:

click to rate:

Account: (login)

More Channels

Channel Catalog

Channel Description:

Product Support and Discussion

older | 1 | .... | 22 | 23 | (Page 24) | 25 | 26 | .... | 36 | newer

    0 0
  • 01/14/14--02:41: RE: Feature Request
  • Hi Rob,

    Thanks for your post.

    This is a good idea and it seems to be the first time anyone has suggested it to us. I've logged the feature request internally as SB-5557 to be reviewed by our development team.

    I wouldn't expect a feature like this to be added any time soon, but it can at least be up for consideration now.

    Your idea of writing a powershell wrapper sounds like a good workaround for the time being.

    If you have any success, it would be great if you could post your script so other users with the same issues can make use of it. Seeing your script would also help us understand your requirements better, if the feature is ever implemented.


    0 0

    Can SQL Backup Pro 7 can restore SQL Backup Pro 3 (xxx.sqb)?

    0 0
  • 01/17/14--16:17: Data Transfer options
  • From SQL 2012 BOL...

    Data Transfer Options
    The options enable you to optimize data transfer from the backup device.

    BUFFERCOUNT = { buffercount | @buffercount_variable }
    Supported by: RESTORE

    Specifies the total number of I/O buffers to be used for the restore operation. You can specify any positive integer; however, large numbers of buffers might cause "out of memory" errors because of inadequate virtual address space in the Sqlservr.exe process.

    The total space used by the buffers is determined by: buffercount*maxtransfersize.

    MAXTRANSFERSIZE = { maxtransfersize | @maxtransfersize_variable }
    Supported by: RESTORE

    Specifies the largest unit of transfer in bytes to be used between the backup media and SQL Server. The possible values are multiples of 65536 bytes (64 KB) ranging up to 4194304 bytes (4 MB).

    Key point is that SQL Server supports a value up to 4194304 bytes form MaxTransferSize whereas SQLBackup limits this value to 1048576 bytes. It also doesn't have an option for buffercount.

    The reason I ask is that I am trying to reduce the restore time of the REDO phase of a highly active transaction log. I have read that increasing these values can help that.

    0 0

    I don't know, but could you please send me ( a backup of the model database made using SQL Backup 3, and I'll see if it can be restored using SQL Backup 7.

    Thank you.

    0 0
  • 01/18/14--23:55: RE: Data Transfer options
  • During the development of SQL Backup, we found that it made very little difference in backup throughput when bumping up the buffer size from 1 MB to 4 MB, but it increased the memory requirements fourfold.

    We also found out that errors sometimes occur when during a restore, a MAXTRANSFERSIZE value that's different from the value used during the backup is used. Thus, to avoid situations where the secondary server cannot meet the memory requirements and fail to restore the backup, we decided to limit the MAXTRANSFERSIZE to a conservative 1 MB.

    Could you please post the link to the article you mentioned?

    Thank you.

    0 0
  • 01/19/14--19:47: RE: Data Transfer options

    BTW, I did find that increasing the thread count helped a lot too. It did increase the buffer count to by 6 * Threadcount up to 28 buffers max, which sped the redo phase up. But I do think that that if SQL Server allows up to a 4MB transfer size natively then Red Gate SQL Backup should allow it too. I'm not suggesting that you change the 1MB default, but should allow for manual adjustment of MaxTransferSize and buffercount parameters.

    0 0
  • 01/22/14--11:41: Backup Job Hangs
  • We have been using red-gate's backup pro since July 2013, however after the minor releases at the beginning of December 2013 we have experienced a couple instances where a log backup execution hung and prevented further backups until the blockage was identified and resolved. When this has occurred we have observed the following.

    1. SQL Server 2008 was unable to cancel the execution of the job. Manually restarting the red-gate backup service allowed SQL Server to abort the execution.
    2. No backup attempt appears in the backup activity history.
    3. No log backup file existed before process was cancelled. No log backup file existed after service restart.
    4. No errors were reported.
    5. The script being executed:

    [code]DECLARE @errorcode INT
    DECLARE @sqlerrorcode INT
    EXECUTE master..sqlbackup '-SQL "BACKUP LOGS [Billing]
    TO DISK = ''S:\Log Shipping\<SERVER>\<DATABASE>\<DATABASE>_<DATETIME YYYYmmddhhnnss>_<TYPE>.sqb'' WITH ERASEFILES = 7,
    COPYTO = ''\\ServerName\s$\Log Shipping\<Server>\<Database>'',
    THREADCOUNT = 7"', @errorcode OUT, @sqlerrorcode OUT;

    IF (@errorcode >= 500) OR (@sqlerrorcode <> 0)
    RAISERROR ('SQL Backup failed with exit code: %d SQL error code: %d', 16, 1, @errorcode, @sqlerrorcode)

    0 0
  • 01/23/14--16:49: RE: Backup Job Hangs
  • When SQL Backup encounters a critical error, it generates a stack trace of events leading up to the error. This stack trace is then stored in a file named SQBCoreService_<instance name>_bugreport.txt, and is located in 'C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\' on Windows 2003 and older, and 'C:\ProgramData\Red Gate\SQL Backup\Log\' on Windows Vista and newer.

    Could you please check if that file exists on your system? If it does, could you please send it to us? If the file does not exist, it may be because the SQL Backup Agent service startup account does not have rights to create the file in that folder. You can test this by manually creating the stack trace file by running the following command from Query Analyzer/Management Studio when connected to the SQL Server instance:

    EXEC master..sqbutility 9997

    If the file is not created, try granting read/write permissions on the abovementioned folder to the SQL Backup Agent service startup account.

    0 0


    I'm currently running, and I have a very annoying issue.

    Every week I have a series of six DB backups that need to be restored to the same reporting/snapshot machine. All the backup files are on the same (but different from the target) networked machine.

    SQL Backup allows up to four restores to be running at one. However, I often get the following problems when I try to get them running at once.

    1/26/2014 9:03:04 AM: VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. Check that the SQL Server instance is running, that you have the SQL Server System Administrator server role; and that no other
    processes are blocking the backup or restore process; or try increasing the value of the VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]
    1/26/2014 9:03:04 AM: Also check that the database is not currently in use.

    (I've done all the suggested VDITimeout solutions, but none of them work because, I think, of the later errors)

    1/26/2014 9:05:27 AM: SQL error 3013: RESTORE DATABASE is terminating abnormally.
    1/26/2014 9:05:27 AM: SQL error 3201: Cannot open backup device 'SQLBACKUP_7C19257A-80B8-4857-AE48-AFF278BDE9C3'. Operating system error 0x80070002(The system cannot find the file specified.).

    Now, I'm not entirely sure what that final error means. Does it mean that the OS on the machine holding the backup file is reporting an error message? Does it mean the DB Server OS is reporting some issue with a virtual file? Because the file does exist. If I simply wait until one or more of the running restores are completed and then retry the restore, it works fine.

    Any idea what might be causing this?

    The databases in question are roughly 500GB in size.



    0 0
  • 01/27/14--11:28: RE: Backup Job Hangs
  • There was not an error file at the location provided. After executing the SQL command a file was created successfully.

    date/time : 2014-01-27, 19:17:24, 418ms
    computer name : ...
    user name : ... <admin>
    registered owner : Windows User
    operating system : Windows NT New x64 Service Pack 1 build 7601
    system language : English
    system up time : 37 days 3 hours
    program up time : 5 days 2 hours
    processors : 8x Intel(R) Xeon(R) CPU X5550 @ 2.67GHz
    physical memory : 1396/16371 MB (free/total)
    free disk space : (CSmile 25.94 GB
    display mode : 1024x768, 32 bit
    process id : $4a8
    allocated memory : 32.52 MB
    command line : "C:\Program Files (x86)\Red Gate\SQL Backup 7\SQL2008\SQBCoreService.exe" -i SQL2008
    executable : SQBCoreService.exe
    exec. date/time : 2013-12-03 16:20
    version :
    compiled with : Delphi 7
    madExcept version : 3.0i beta 2
    callstack crc : $835fda28, $f53d4f4b, $6a8f8539
    exception number : 1
    exception class : EConversionError
    exception message : Dump callstack for Red Gate support purposes. Please ignore the EConversionError code.

    0 0
  • 01/28/14--05:52: RE: Backup Job Hangs
  • The next time this error occurs, could you please run the

    EXEC master..sqbutility 9997

    command and send me the resulting file? That command will provide a snapshot of what SQL Backup is doing at that point in time.

    0 0

    Hi Marc,
    Thank you for your forum post and sorry that you have encountered a problem. There are several situations that can cause SQL Backup VDI Error 1010.

    Two of the most common causes are insufficient contiguous memory in the SQL Server Virtual Memory Space and VDITimeout. I will explain each one of these two causes:

    Insufficient Contiguous Memory
    SQL Server specifies an amount of virtual address space (in megabytes, default value is 128MB in SQL 2000 and 256Mb in SQL 2005 / 2008) that SQL Server will leave available for memory allocations within the SQL Server process but outside the SQL server memory pool. This area is used by SQL Server for loading extended procedure .dll files, such as xp_sqlbackup.dll used by SQL Backup. It is in this area of memory that SQL Backup creates the VDI device for use when running a backup or restore task.

    Unlike the backup task, where the user can configure a parameter called MAXTRANSFERSIZE and the number of CPU threads that affect the amount contiguous memory used. Also in a backup task, when encountering a VDI error, SQL Backup will reattempt the backup job reducing automatically the value for the MAXTRANSFERSIZE parameter in case the error was caused by an insufficient amount of continuous memory, THIS DOES NOT OCCUR FOR A RESTORE TASK. On average SQL Backup requires approximately 6MB of continuous memory per thread (MAXTRANSFERSIZE x 6 x Number of Threads).

    1 thread = 6MB
    5 threads = 30MB
    8 threads = 48MB
    10 threads = 60MB
    15 threads = 90MB
    20 threads = 120MB
    32 threads = 192MB (Highest number of threads that can be used)

    When a backup is performed the MAXTRANSFERSIZE value and the number of threads used is recorded into the backup file header. This information is then used by the restore process.

    Therefore in your environment when you attempt to run the 5th restore job, you may have insufficient contiguous memory. If this is the case, investigate either reducing the number of threads used to create the backup file or the MAXTRANSFERSIZE value or combination of both settings.

    When SQL Backup issues the backup or restore command to SQL Server, SQL Backup creates the Virtual Device Interface (VDI) and waits for SQL Server to respond. If SQL Server does respond within 30 seconds, SQL Backup generates VDI Error 1010.

    The delay could be caused by many things e.g. a blocking process such as another backup of the same database, or a CPU intensive task that's running and has tied up the server.

    As you have discovered you can set a Registry Key called VDITimeout which increases the time that SQL Backup waits for SQL Server to respond to the backup or restore request.

    I do not know what value you have specified for the VDTImeout registry key but I suspect that you need to increase the value of between 180 to 300 seconds, based on the log file information in your post.

    Assuming that the restore command was issued at 9:02:34. SQL Backup waited 30 seconds before creating the VDI 1010 error:
    1/26/2014 9:03:04 AM: VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed...........
    Approximately two and half minutes later, SQL server responds to the restore request but the VDI is no longer available and this entry in the log file is created:
    1/26/2014 9:05:27 AM: SQL error 3201: Cannot open backup device 'SQLBACKUP_7C19257A-80B8-4857-AE48-AFF278BDE9C3'. Operating system error 0x80070002(The system cannot find the file specified.).

    A support call has been created for you HERE, to view or update the call either reply to this forum post or directly to the support call. If you have not already done so, you will need to create a RedGate ID to view the support ticket in our call logging system.

    I hope the above helps.
    Many Thanks

    0 0

    I was trying to take backup of the file and copy it into hosted storage and i get the error below.

    Unable to upload file F:\Backup to hosted storage (error 14 -Error while checking client / service compatibility: Unable to connect to the remote server)

    I was thinking it might be because of SQL Backup Agent service login details but i don't know how to fix it. Can anyone tell me how to fix the issue?


    0 0

    Although Eddie sent me an email to which I replied very swiftly, SILENCE has ensued, sadly...

    Eddie Davis (Support)
    Nov 29 09:48 (GMT)


    This is an undocumented feature which allows SQL Backup users to disable the timeline component of the SQL Backup GUI. By enabling this feature, you may experience improved performance of GUI.

    If you wish use this feature, please follow the instructions:

    To disable the time line, close the SQL Backup GUI and add the following registry key on the machine where the GUI is installed: HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\Client (please note, you may need to create the 'Client' folder).
    Create a new string value called DisableTimelineItemRequests and set the value to = 1 or true

    Restart the SQL Backup Agent service for each of the registered servers.
    Open the SQL Backup GUI and see if the performance has improved in populating the registered servers.
    Once the spinning wheel has stopped, it appears that the registered server is not connected. You will need to expand the registered server to see a successful connection and to see entries in the Activity History.


    Upon opening the GUI and once the registered server or servers has completed loading, it appears that the registered server is not connected. You will need to expand the registered server to see a successful connection and to see entries in the Activity History or the other bottom grid items.

    When navigating through the databases listed for a registered server, you may experience that the entries in the Activity History disappear. Simply click on another server or database and then click back to the original server or database to reload the Activity History or the other bottom grid items.

    Many Thanks
    Eddie Davis
    Technical Support Engineer
    Red Gate Software Ltd

    My Reply:
    Thanks for the info BUT that doesn't address the issue at hand. If you refer to the behavior cited in Profiler, the top pane continues to function with auto-scroll turned off. The lower pane is then static, allowing the user to choose which activities to view. The auto UPDATE of the chronological pane should continue, just DON'T move the lower pane - that is what constitutes a huge time waster when paging through the Activity History, as in: I scroll down to the activity I'm interested in, then, having found the group of backups to investigate, along comes auto-refresh and resets the list to the top - stop THAT!

    Hope this clarifies.

    Referring to my final sentence, above, DOES MY REPLY CLARIFY THINGS?

    Is this thread dead?

    Is Support Case 8828 dead?

    This is still causing issues as I cannot research an ongoing remote file erase issue, support case 10148, while this dumb refresh goes on sticking it to me by presenting the latest activity in my face all the time... Yes, Eddie has provided an "undocumented" workaround, but is that the best there is - turn off ALL refresh when only the lower pane refresh should be togglable? Not exactly desirable for everyday usage, IMO.

    Yes, I'm a bit peevish because I've been using SQL Backup seems like since forever, and this ONE pain in the rear behavior is still a pain in the rear after how many years? Five? Six? Seven? Lost count...

    "SQL Profiler behaves better than SQL Backup" - is that a statement to live down or what?

    0 0

    Sent another email to ZenDesk in hopes of a response after a three week silence.

    Update, please?

    0 0

    You mentioned that the backup files of another database copied to the same instance does not experience the same problem. Could you please post the backup command used to back up that database? Just want to compare the options used.


    0 0

    Hi PDinCA,

    Sorry for the delay, I can confirm that we understand the scenario you've described. I'm currently working on SQL Backup planning, and this is on my list of things to be looked into.

    Best regards,


    0 0

    Further information, there is a patch for SQL Backup that will allow a backup of replica database that is a member of an always-on availability group and allow the ERASEFILES and COPYTO processes to run.

    The patch suppresses SQL Error 976 that is generated so that the ERASEFILES and COPYTO processes will run.

    There is still the need to create the SkipChecks registry key by creating a DWORD registry entry, SkipChecks, with the value 1. This entry needs to be created in the

    HKEY_LOCAL_MACHINE\Software\Red Gate\SQL Backup\BackupSettingsGlobal\<instance name>

    registry node.

    Please contact the support team, [] will provide details of where to download the patch and instructions on how to install.

    PLEASE NOTE: The Backup of a replica database will report successful with warnings. The backup process will still generate a warning, Warning 167: Failed to get database size from server.

    Many Thanks

    0 0

    --> nevermind

    0 0

    Thanks, Colin, good news indeed.


older | 1 | .... | 22 | 23 | (Page 24) | 25 | 26 | .... | 36 | newer