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 | .... | 30 | 31 | (Page 32) | 33 | 34 | .... | 36 | newer

    0 0

    The compression rate is calculated on the actual amount of data stored in the backup files compared to the database size. The compression rate of 35% probably indicates that your database files have about 35% unused space, which SQL Server did not need to back up.

    0 0

    Really Thanks for your suggestion

    0 0

    Thank you Pete, I did not know that.

    0 0

    We are running a SQL Backup job at 1:00 in the morning but we get the following Event ID: 18272 This previously worked fine but only started in the last couple of days.

    Log Name: Application
    Date: 2014/06/11 05:20:18 AM
    Event ID: 18272
    Task Category: Backup
    Level: Error
    Keywords: Classic
    User: MURZA\*********
    Computer: ********
    During restore restart, an I/O error occurred on checkpoint file 'G:\SQL Backup\RestoreCheckpointDB15.CKP' (operating system error 1784(failed to retrieve text for this error. Reason: 15105)). The statement is proceeding but cannot be restarted. Ensure that a valid storage location exists for the checkpoint file.
    Event Xml:
    <Event xmlns="">
    <Provider Name="MSSQLSERVER" />
    <EventID Qualifiers="49152">18272</EventID>
    <TimeCreated SystemTime="2014-06-11T03:20:18.000000000Z" />
    <Security UserID="**********" />
    <Data>G:\SQL Backup\RestoreCheckpointDB15.CKP</Data>
    <Data>1784(failed to retrieve text for this error. Reason: 15105)</Data>

    Does anyone know what causes this, on online forums they all say I must log a call with redgate software.

    I also can't seem to find a network or san issue causing this.

    Please help

    0 0


    i would like to know weather did you got time to check on my query?

    So sorry for delay- I have been away. I did verify the instructions I gave and found they work well because the agent ensure everything runs in the correct sequence.


    what is the purpose of re-running a backup right after having shrunk down the log file like rafiqahmeds was asking?

    I think the strategy here is:

    1. Ensure you always have a back-up
    2. Take extra step to create an 'efficient' back-up- one that has no redundant information in.

    The extra step is not essential but if ever the backup needs to be transported- you've got the absolute minimal size of backup handy.

    Its quite an unusual strategy since step 2 is not usually necessary but it can be very smart in the use case mentioned (transportation of file).


    0 0

    help on msg: "error mapping to memory mapped file"

    Very new to SQL Backup Pro... search docs and asking question now in forums before using support. Appreciate any insight.

    The tree of servers has just one with red x

    Installed GUI on aging SQL2005/W2003 Enterprise and tried registering, importing but no joy... yet Smile

    Thank you!

    0 0

    Could you please locate the SQL Backup Agent service in Windows Services, and see if it's started? If not, could you try to start it and see what happens?

    If it does not start, try using a startup account that is an Administrator on the machine. Will the service start then?

    0 0

    Do the fixes described in this document ( address your issue?

    0 0

    SQL Backup Agent located and running without event log error. Running with local services; Double checked by trying to run as administrator... still same message "error mapping to memory mapped file".

    Also tried with Hyperbac service turned off.

    0 0

    When you run the following in Management Studio, what is the result:

    EXEC master..sqlbackup '-sql "BACKUP DATABASE model TO DISK = [<AUTO>]"'

    0 0

    Apologies for not having checked docs first... appreciate guidance where to start and the cool command to learn.. here is the result...

    SQL Backup 7.6.029
    ERRSQB: 5220 (Error mapping to memory mapped file.) (SQBMmf_): 8 (Not enough storage is available to process this command.)


    -- current
    use master
    BACKUP DATABASE MODEL TO DISK = 'F:\Model.bak' --1500K on disk
    BACKUP DATABASE MODEL TO DISK = 'F:\' --0150K on disk

    0 0

    Could you please run the following in Management Studio and post the result:

    EXEC master..sqbmemory


    0 0

    Type             Minimum              Maximum              Average              Blk count                      Total
    ---------------- -------------------- -------------------- -------------------- -------------------- --------------------
    Commit           4096                 262733824               50892                  14560                  740999168
    Reserve          4096                   16773120              105625                  12357                1305219072
    Free                4096                      983040              166996                     606                  101199872
    Private            4096                 262733824                74437                 26345                 1961050112
    Mapped           4096                    1060864               107861                      63                      6795264
    Image             4096                  24948736               153974                    509                     78372864

    (6 row(s) affected

    0 0

    The problem seems to be that your SQL Server process has very little free memory left, and the largest contiguous block of free memory is only 983040 bytes. That's why SQL Server is raising the error 'Not enough storage is available to process this command.'.

    If possible, try restarting the SQL Server instance to reset the memory allocations, and try running the backup. Then you could run sqbmemory periodically to try and identify which process in SQL Server is taking up all the memory.

    0 0
  • 06/19/14--18:45: TDE Encryption and Backups
  • I am trying to use TDE encryption at the database level in SQL Server. Of course, with encryption, the backups are not compressed. Can SQL Backup handle the encrypted data in the database? Like by decrypting it, compressing it and then encrypting it again?

    0 0

    Like by decrypting it, compressing it and then encrypting it again?

    No, that's not possible.

    0 0

    I'm trying to establish a DR server in AWS. The primary server already has a log shipping job that I set up for it that ships the logs to a DR server that exists in a separate network. I'm wondering if it's possible to "add" this new DR server to the log shipping job that already exists. Essentially, all it would need to do is be able to replay the same transaction logs that the shipping generates. The major difference would be that the logs would need to be copied to an additional location.

    If this isn't possible, how does one go about adding a second DR server for log shipping? Can you only have one per database?

    0 0
  • 06/24/14--02:25: RE: SQL Server 2014 support?
  • Do you have any news about the SQL Server 2014 compatibility?

    On the documentation page for requirements I have seen no update since april 2014 and SQL Server 2014 is still missing in the list of supported SQL Server.

    0 0
  • 06/24/14--05:00: RE: SQL Server 2014 support?
  • Hi,

    We're working on this now, and hope to ship in early Q3.

    Best regards,


    0 0

    Win8.1 Pro, SB, SQL Server 2014 Enterprise and Express (with ADV) on the machine.

    Uninstalled server components because the UI complained of a problem with a server dll.

    Attempted to install from the UI and the message below was emitted.

    I clicked the "Details" link but no dice, so went to the page manually.

    There is no exit code 4 documented, so I'm clueless what to do next...

    Help, please.

    BTW: All I want to do is deactivate the license so I can use it on a QA server...


    <<windows 8.1 Pro Laptop>>: Server Component Installation - Failed

    Copying and running SQBServerSetup - Failed

    Error running installer: exit code 4
    See for more information.

    Starting SQL Backup Agent service - Pending

    Operation pending.

    Checking installed versions - Pending

    Operation pending.

    Checking SQLBackup extended stored procedures - Pending

    Operation pending.

    Verifying installation - Pending

    Operation pending.

    Updating SQL Server information - Pending

    Operation pending.

older | 1 | .... | 30 | 31 | (Page 32) | 33 | 34 | .... | 36 | newer