Forum Discussion

MartinJ's avatar
MartinJ
Level 2
12 years ago

Problems backing up SQL data

Wer using Symantec Netback up V7.5.0.4 on a Windows Server 2008 Service pack 2 and all our other tapes\jobs are completing without issues.  Only our SQL data is not getting backed up.  Pretty much a novice at reading errors so help would be very much appreciated.  Here is a copy of the logs below.

 

Look forward to any suggestions.

 

14/03/2013 05:40:46 - Info dbclient(pid=6068) ERR - Error in VDS->Close: 0x80770004.






14/03/2013 05:35:34 - Info dbclient(pid=6068) INF - BACKUP STARTED USING


14/03/2013 05:35:34 - Info dbclient(pid=6068) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)


14/03/2013 05:35:34 - Info dbclient(pid=6068) Jun 17 2011 00:54:03


14/03/2013 05:35:34 - Info dbclient(pid=6068) Copyright (c) Microsoft Corporation


14/03/2013 05:35:34 - Info dbclient(pid=6068) Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)


14/03/2013 05:35:34 - Info dbclient(pid=6068) Batch = C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\Netbackup_WorkSite_Script[0].bch1363239267[0].bch, Op# = 1


14/03/2013 05:35:35 - Info dbclient(pid=6068) INF - Using backup image CLEOPATRA.MSSQL7.CLEOPATRA.db.PBSASSIST.~.7.001of001.20130314053533..C


14/03/2013 05:35:35 - Info dbclient(pid=6068) INF - backup database "PBSASSIST" to VIRTUAL_DEVICE='VNBU0-6068-7928-1363239334' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2

14/03/2013 05:35:36 - Info dbclient(pid=6068) INF - Number of stripes: 1, Number of buffers per stripe 2.


14/03/2013 05:35:36 - Info dbclient(pid=6068) INF - Created VDI object for SQL Server instance <CLEOPATRA.BLME.LOCAL>. Connection timeout is <300> seconds.

14/03/2013 05:40:40 - Info dbclient(pid=6068) ERR - Error in GetConfiguration: 0x80770003.


14/03/2013 05:40:40 - Info dbclient(pid=6068) CONTINUATION: - The api was waiting and the timeout interval had elapsed.

14/03/2013 05:40:46 - Info dbclient(pid=6068) ERR - Error in VDS->Close: 0x80770004.


14/03/2013 05:40:47 - Info dbclient(pid=6068) CONTINUATION: - An abort request is preventing anything except termination actions.

14/03/2013 05:40:47 - Info dbclient(pid=6068) INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\Netbackup_WorkSite_Script[0].bch1363239267[0].bch FAILED with STATUS 1 (0 is normal). Elapsed time = 314(314)
seconds.

14/03/2013 05:40:53 - Info dbclient(pid=6068) INF - BACKUP STARTED USING


14/03/2013 05:40:53 - Info dbclient(pid=6068) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)

14/03/2013 05:40:53 - Info dbclient(pid=6068) Jun 17 2011 00:54:03


14/03/2013 05:40:53 - Info dbclient(pid=6068) Copyright (c) Microsoft Corporation


14/03/2013 05:40:53 - Info dbclient(pid=6068) Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)


14/03/2013 05:40:53 - Info dbclient(pid=6068) Batch = C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\Netbackup_WorkSite_Script[0].bch1363239267[0].bch, Op# = 2


14/03/2013 05:40:53 - Info dbclient(pid=6068) INF - Using backup image CLEOPATRA.MSSQL7.CLEOPATRA.db.Worksite.~.7.001of001.20130314054051..C


14/03/2013 05:40:54 - Info dbclient(pid=6068) INF - backup database "Worksite" to VIRTUAL_DEVICE='VNBU0-6068-7908-1363239653' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2

14/03/2013 05:40:55 - Info dbclient(pid=6068) INF - Number of stripes: 1, Number of buffers per stripe 2.


14/03/2013 05:40:55 - Info dbclient(pid=6068) INF - Created VDI object for SQL Server instance <CLEOPATRA.BLME.LOCAL>. Connection timeout is <300> seconds.

14/03/2013 05:45:55 - Info dbclient(pid=6068) ERR - Error in GetConfiguration: 0x80770003.


14/03/2013 05:45:56 - Info dbclient(pid=6068) CONTINUATION: - The api was waiting and the timeout interval had elapsed.

14/03/2013 05:46:02 - Info dbclient(pid=6068) ERR - Error in VDS->Close: 0x80770004.


14/03/2013 05:46:02 - Info dbclient(pid=6068) CONTINUATION: - An abort request is preventing anything except termination actions.

14/03/2013 05:46:03 - Info dbclient(pid=6068) INF - OPERATION #2 of batch C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\Netbackup_WorkSite_Script[0].bch1363239267[0].bch FAILED with STATUS 1 (0 is normal). Elapsed time = 311(311)
seconds.

14/03/2013 05:46:05 - Info dbclient(pid=6068) INF - Results of executing <C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\Netbackup_WorkSite_Script[0].bch1363239267[0].bch>:


14/03/2013 05:46:05 - Info dbclient(pid=6068) <0> operations succeeded. <2> operations failed.


14/03/2013 05:46:06 - Info dbclient(pid=6068) INF - The following object(s) were not backed up successfully.


14/03/2013 05:46:06 - Info dbclient(pid=6068) INF - PBSASSIST


14/03/2013 05:46:07 - Info dbclient(pid=6068) INF - Worksite


14/03/2013 05:46:07 - Info dbclient(pid=6068) INF - This batch was run 2 times and resulted in 0 successful backup(s) and 2 failure(s) after repeated attempts.

7.5
Backup and Recovery
NetBackup
Tip-How to
Troubleshooting
Windows Server (2003-2008)
  • Roger_C's avatar
    Roger_C
    Level 4
    12 years ago

    The 300 second gap is the most likely giveaway

    14/03/2013 05:35:35 - Info dbclient(pid=6068) INF - backup database "PBSASSIST" to VIRTUAL_DEVICE='VNBU0-6068-7928-1363239334' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
    14/03/2013 05:35:36 - Info dbclient(pid=6068) INF - Number of stripes: 1, Number of buffers per stripe 2.
    14/03/2013 05:35:36 - Info dbclient(pid=6068) INF - Created VDI object for SQL Server instance <CLEOPATRA.BLME.LOCAL>. Connection timeout is <300> seconds.
    ** HERE **
    14/03/2013 05:40:40 - Info dbclient(pid=6068) ERR - Error in GetConfiguration: 0x80770003.

    Without going into dbclient itself - to me this appears to be simple Client Read Timeout issue.
    I'm assuming that the database "PBSASSIST" will take longer than 5 minutes to backup hence the 300 default
    seconds timeout.

    Try extending the Client Read Timeout to about 1800 and then retry the backup.
    Also, try to stick simple characters and exclude characters such as "[" in your batch script.
    Not that this is related but can cause probs with mixed locales etc,

    RogerC

  • MartinJ's avatar
    MartinJ
    Level 2
    12 years ago

    Hi Roger

    I have increased the timout but it is still staying with the 300.  I have restarted the netbackup services and also rebooted the netback up server.

     

    Any thoughts?

  • MartinJ's avatar
    MartinJ
    Level 2
    12 years ago

    I have gone to the client server by the master server (Media server) and edited from there, and also set on the client.  Here is a screen shot.  I have removed our server names etc.

     

  • Marianne's avatar
    Marianne
    Level 6
    12 years ago

    Your screenshot is too small...

    You need to go to Host Properties -> Media Server (select media server) -> Timeouts

  • MartinJ's avatar
    MartinJ
    Level 2
    12 years ago

    Hi Marianne

    I recognise your name from previous posts.  I have found the correct area and have made the appropriate changes.  But it is still picking up 300 as the default.

    Info dbclient(pid=6068) INF - Created VDI object for SQL Server instance <SERVERNAME>. Connection timeout is <300> seconds

    Restarted services on both server and client.  I am at a loss. 

  • Mauro_Gabriel_B's avatar
    Mauro_Gabriel_B
    Level 3
    12 years ago

    I have the same issue, and it's not related to any Client Read timeouts. Not on the Media Server, nor Client, nor Master Server. I've changed them all, bounced daemons even on the Master Server, also unchecked "use OS default vaules" on Host properties, changed file browse timeout... its not that, it's something else.

    It seems to be related to a connection to database timeout... maybe something to be set on the BCH, or the database? I'll keep looking, but it's definitely not a client read timeout.

  • C_Moisan's avatar
    C_Moisan
    Level 4
    12 years ago

    Make sure the the host/instance names in the script are EXACTLY like they are in Netbackup. Upper and lower case differences might be the reason too.