Forum Discussion

NBU_BEX_Support's avatar
NBU_BEX_Support
Level 4
11 years ago

Backup is not completed - Connection timeout is <300> seconds.

Hello Folks! I need some help!

I have a problem in my Netbackup environment.

The backup is not completed in a client, because just stay on status "Connection timeout is <300> seconds". No change from this status.

15/01/2014 17:17:15 - Info nbjm(pid=3920) starting backup job (jobid=116434) for client srvvm63, policy srvvm63-sql_server, schedule Diario  
15/01/2014 17:17:15 - Info nbjm(pid=3920) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=116434, request id:{30A7A23C-5CDB-41E2-BD49-B2D33D29F3B5})  
15/01/2014 17:17:15 - requesting resource srv03-hcart-robot-tld-1
15/01/2014 17:17:15 - requesting resource srv03.grupomaggi.corp.NBU_CLIENT.MAXJOBS.srvvm63
15/01/2014 17:17:15 - requesting resource srv03.grupomaggi.corp.NBU_POLICY.MAXJOBS.srvvm63-sql_server
15/01/2014 17:17:15 - granted resource srv03.grupomaggi.corp.NBU_CLIENT.MAXJOBS.srvvm63
15/01/2014 17:17:15 - granted resource srv03.grupomaggi.corp.NBU_POLICY.MAXJOBS.srvvm63-sql_server
15/01/2014 17:17:15 - granted resource srv03-hcart-robot-tld-1
15/01/2014 17:17:15 - estimated 0 Kbytes needed
15/01/2014 17:17:15 - Info nbjm(pid=3920) started backup job for client srvvm63, policy srvvm63-sql_server, schedule Diario on storage unit srv03-hcart-robot-tld-1
15/01/2014 17:17:16 - started process bpbrm (8064)
15/01/2014 17:17:17 - Info bpbrm(pid=8064) srvvm63 is the host to backup data from     
15/01/2014 17:17:17 - Info bpbrm(pid=8064) reading file list from client        
15/01/2014 17:17:17 - connecting
15/01/2014 17:17:20 - Info bpbrm(pid=8064) starting bphdb on client         
15/01/2014 17:17:20 - Info bphdb(pid=1664) Backup started           
15/01/2014 17:17:20 - connected; connect time: 00:00:03
15/01/2014 17:17:24 - Info dbclient(pid=4460) INF - BACKUP STARTED USING        
15/01/2014 17:17:24 - Info dbclient(pid=4460) Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)    
15/01/2014 17:17:24 - Info dbclient(pid=4460) Apr  2 2010 15:48:46        
15/01/2014 17:17:24 - Info dbclient(pid=4460) Copyright (c) Microsoft Corporation         
15/01/2014 17:17:24 - Info dbclient(pid=4460) Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
15/01/2014 17:17:24 - Info dbclient(pid=4460) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\backup_full.bch, Op# = 1      
15/01/2014 17:17:24 - Info dbclient(pid=4460) INF - Using backup image SRVVM63.MSSQL7.SRVVM63.db.Creditflow_AMaggi_Des.~.7.001of001.20140115171723..C       
15/01/2014 17:17:24 - Info dbclient(pid=4460) INF - backup database "Creditflow_AMaggi_Des" to VIRTUAL_DEVICE='VNBU0-4460-4400-1389817044' with  compression,  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
15/01/2014 17:17:25 - Info dbclient(pid=4460) INF - Number of stripes: 1, Number of buffers per stripe 2.
15/01/2014 17:17:25 - Info dbclient(pid=4460) INF - Created VDI object for SQL Server instance <SRVVM63>. Connection timeout is <300> seconds.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Anyone has seen this error? I appreciate if could help me.

7.1.x and Earlier
Backup and Recovery
NetBackup
Remote Agent for Windows Servers
Windows Server (2003-2008)

24 Replies

Sort By
  • revarooo's avatar
    revarooo
    Level 6
    11 years ago

    Try changing the CLIENT_READ_TIMEOUT on the media server - the default is 300 seconds. Try setting it to 900, repeat and see if the error re-occurs, if it does and 900 pops up, increase further.

     

    www.symantec.com/business/support/index?page=content&id=HOWTO13869

     

    If your media server is unix/linux add CLIENT_READ_TIMEOUT = 900 to the /usr/openv/netbackup/bp.conf file

  • NBU_BEX_Support's avatar
    NBU_BEX_Support
    Level 4
    11 years ago

    Hi revaroo!

    Thank you for help me....so, when I go to change in the Media properties, An error occurs:

    Unable to save data on some Hosts. This erro is "file write failed (14)."

    My server run on W2K8 R2

    Do you know what means?

  • NBU_BEX_Support's avatar
    NBU_BEX_Support
    Level 4
    11 years ago

    Hi! revaroo!

    I can change the CLIENT_READ_TIMEOUT, ​​but when I start the Job again, it still shows "300 seconds.

    Where did I Wrong? I just restart the application!

    I wait!

     

    Tks!

  • revarooo's avatar
    revarooo
    Level 6
    11 years ago

    ahhh change

     

    VDITIMEOUTSECONDS XXXX in the batch file located

     

    • install_path\NetBackup\DbExt\MsSql\ 

    http://www.symantec.com/business/support/index?page=content&id=TECH127055

     

    Page 114

     

     

    So something like:

    VDITIMEOUTSECONDS 900

  • NBU_BEX_Support's avatar
    NBU_BEX_Support
    Level 4
    11 years ago

    Actually I changed what you asked "client_read_timeout". But when I start up again, the status is shown: INF - Created VDI object for SQL Server instance <SRVVM63>. Connection timeout is <300> seconds.

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    Yes. On the Client. Where the script (batch file) was created....

    Can we go back to the beginning, please...

    Is this a new SQL backup that has never worked before?

    You have selected W2003/W2008 as OS and NBU 7.1 and earlier as NBU version.

    Are the Client, Master and Media server all on same OS?

    Which NBU version and patch level?

    Have you confirm connectivity between Master and Client?
    and connectivity when connection is initiated on Client?

    Have you created log folders on client, master and media server?

    On client: bpcd and dbclient
    On master: bprd (restart NetBackup Request service after creating log folder)
    On media server: bpbrm and bptm

    Have you tried to run a manual backup from the client using the NBU for SQL GUI?

  • NBU_BEX_Support's avatar
    NBU_BEX_Support
    Level 4
    11 years ago

    On the Client. Where the script (batch file) was created....
    R=I cant find any bacth file in this path (install_path\NetBackup\DbExt\MsSql\)

    Can we go back to the beginning, please...
    R=Sure!

    Is this a new SQL backup that has never worked before?
    R= It Was being backed up normally.

    You have selected W2003/W2008 as OS and NBU 7.1 and earlier as NBU version.
    R= Yes...it is selected without qualifyed name. Just "SRV63" and like W2003/W2008. NBU Version 7.1.0.4

    Are the Client, Master and Media server all on same OS?
    R= Yes...all same OS W2K8 R2

    Which NBU version and patch level?
    R= NBU Version 7.1.0.4 - Hotfix 4

    Have you confirm connectivity between Master and Client?
    R= Yes. All Connected.

    and connectivity when connection is initiated on Client?
    R= Yes

    Have you created log folders on client, master and media server?
    R= No...I Haven't Created Log...

    On client: bpcd and dbclient
    On master: bprd (restart NetBackup Request service after creating log folder)
    On media server: bpbrm and bptm


    Have you tried to run a manual backup from the client using the NBU for SQL GUI?
    Yes...so return this error "Server status = 245"

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    I cant find any bacth file in this path (install_path\NetBackup\DbExt\MsSql\)

    We see the following in your opening post:

    Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\backup_full.bch, 

    Are you saying it is no longer there?

    Status 245 confirms that we need log files. Especially bprd on the master.

    Let us know what happens once you have increased the VDI Timeout in the backup script.

  • NBU_BEX_Support's avatar
    NBU_BEX_Support
    Level 4
    11 years ago

    Ok...I found in this path the file "backup_full.bch". So, I open it and I dont see "VDI Timeout". Need I to insert this information in this file?

     

    Abou t error 245, I´ll enable the log on the master server.

     

    I Wait!