CONTINUE_AFTER_ERROR | STOP_ON_ERROR

jrandalljrandall Posts: 35
edited July 15, 2009 6:37AM in SQL Backup Previous Versions
This option is not explained in the documentation. It's listed, but there's no discussion. What is the effect of using either of these options?
· Share on Twitter

Comments

  • priyasinhapriyasinha Posts: 548 Silver 1
    Hi,

    The effect of using these keywords is mentioned below:

    STOP_ON_ERROR
    Will instructs BACKUP to fail if a page checksum does not verify. This is the default behaviour.

    CONTINUE_AFTER_ERROR
    Will instruct BACKUP to continue despite encountering errors such as invalid checksums, torn page etc.

    These options are not discussed in the documentation because they are native SQL Server keywords and not SQL Backup keywords. Please read BOL if you need more information.

    Thanks,
    Priya
    Priya Sinha
    Project Manager
    Red Gate Software
    · Share on Twitter
  • jrandalljrandall Posts: 35
    Thanks for the explanation. I was hoping they were related to the new network resilience feature. How does one enable/use network resilience from a command line?
    · Share on Twitter
  • priyasinhapriyasinha Posts: 548 Silver 1
    Hi,

    You will need to use DISKRETRYCOUNT and DISKRETRYINTERVAL keywords. The easiest way to get the script for the command line .. is to perform this action on the UI and then in the last step of the wizard, you can view the command line as well as extended stored procedure format of the script. Copy the command line version of the script and use it as you like.

    You can get more information about the keywords from the help file here

    http://www.red-gate.com/supportcenter/Content.aspx?p=SQL%20Backup&c=SQL_Backup/help/6.0/SBU_BACKUP_cmd.htm&toc=SQL_Backup/help/6.0/toc816062.htm

    Hope this helps.

    Regards,
    Priya
    Priya Sinha
    Project Manager
    Red Gate Software
    · Share on Twitter
Sign In or Register to comment.