1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This message will disappear after you have made at least 12 posts. Thank you for your cooperation.

Some database of MS SQL Server can't be backed up using TDP for database

Discussion in 'Microsoft SQL Server' started by hungng89, Jun 2, 2011.

  1. hungng89

    hungng89 New Member

    Joined:
    May 25, 2010
    Messages:
    115
    Likes Received:
    2
    Occupation:
    System Specialist
    Location:
    VietNam
    Dear everyone

    I have installed TDP for SQL on my SQL Server . The TDP backup goes well with 8/10 database . Only 2 database GVSIS GVSIS_DEV can't be backed up , the problem seem come from MSSQP , but i can manually backup them using MSSQL Backup ultilitiy
    Code:
    04/20/2011 17:00:47 ============== Log file pruned using log retention period of 60 day(s)
    04/20/2011 17:00:47 ============== No log entries pruned
    04/20/2011 17:00:47 =========================================================================
    04/20/2011 17:00:47 =========================================================================
    04/20/2011 17:00:47 Request                       : FULL BACKUP
    04/20/2011 17:00:47 Database Input List           : *
    04/20/2011 17:00:47 Group Input List              : -
    04/20/2011 17:00:47 File Input List               : -
    04/20/2011 17:00:47 Number of Buffers             : 3
    04/20/2011 17:00:47 Buffer Size                   : 1024
    04/20/2011 17:00:47 Number of SQL Buffers         : 0
    04/20/2011 17:00:47 SQL Buffer Size               : 1024
    04/20/2011 17:00:47 Number of Stripes specified   : 1
    04/20/2011 17:00:47 Estimate                      : -
    04/20/2011 17:00:47 Truncate Log?                 : -
    04/20/2011 17:00:47 Wait for Tape Mounts?         : Yes
    04/20/2011 17:00:47 TSM Options File              : C:\Program Files\Tivoli\TSM\TDPSql\dsm.opt
    04/20/2011 17:00:47 TSM Nodename Override         : -
    04/20/2011 17:00:47 Sqlserver                     : GVLHCMHOSQL01\PRODUCT
    04/20/2011 17:00:47  
    04/20/2011 17:00:47 Backup of SQL Database GVSIS will not be attempted.
    04/20/2011 17:00:47 ACO5422E Received the following from the MS SQL server:
    04/20/2011 17:00:47 Specified cast is not valid. (HRESULT:0x80004002)
    04/20/2011 17:00:47 Backup of SQL Database GVSIS_DEV will not be attempted.
    04/20/2011 17:00:47 ACO5422E Received the following from the MS SQL server:
    04/20/2011 17:00:47 Specified cast is not valid. (HRESULT:0x80004002)
    
    
    Does any one has any advice ?

    Thanks and Best Regards
     
  2.  
  3. chad_small

    chad_small Moderator

    Joined:
    Dec 17, 2002
    Messages:
    2,205
    Likes Received:
    44
    Occupation:
    AIX/SAN/TSM
    Location:
    Gilbert, AZ
    hungng89 likes this.
  4. hungng89

    hungng89 New Member

    Joined:
    May 25, 2010
    Messages:
    115
    Likes Received:
    2
    Occupation:
    System Specialist
    Location:
    VietNam
    Dear all

    As we can backup all remain database to TSM Server , the issue can only come from MSSQL
    database setting include : Access Right , Structural , Configuration, Database Logical Files setting.

    After doing a health check on your Microsoft SQL Server , i can clarified the issue root cause come
    from Page Verify Configuration

    Issue root cause:
    =============================================================================
    Database page verify method on Microsoft SQL Server Database GVSIS
    and GVSIS_DEV is Torn page detection. Torn page detection does not
    completely fix a DB structural integrity issue.
    =============================================================================

    Setting changed:
    =============================================================================
    Page verify configuration changed from Torn page detection to Checksum
    =============================================================================


    Thanks and Best Regards.
     
  5. eric06

    eric06 New Member

    Joined:
    Dec 21, 2011
    Messages:
    1
    Likes Received:
    2
    Hello hungng89,

    I think solutions are

    TDP - Put QUERYOPTIMIZATION 0 in tdpsql.cfg (Configuration file by default) or SQL - sp_dboption 'MyTroubleDatabase', 'autoclose', 'FALSE'
    for each affected database.
    Rgds
     
    hungng89 and Moebius like this.
  6. Moebius

    Moebius New Member

    Joined:
    Jul 9, 2008
    Messages:
    39
    Likes Received:
    2
    Occupation:
    IT Consultant
    Location:
    Italy
    hungng89 likes this.

Share This Page