MSSQL Backup pending every 40 - 60 minutes

Last post 11-17-2019, 5:25 PM by Anthony.Hodges. 1 replies.
Sort Posts: Previous Next
  • MSSQL Backup pending every 40 - 60 minutes
    Posted: 11-12-2019, 8:14 PM

    Hai, please help me to identifying problem about backup mssql. Mssql backup pending every 40-60 minutes.

    I had add additional setting nSQLQueryWaitMaxRetryCount with value 1000 and add nSQLQueryTimeout with value 0.

    Refers from Article ID: SQL0008 and SQL0014 on documentation commault.

    And i create 1way firewall between commserve, ma1, ma2, and client. I changed keep alive interval to 30s 

    Dedup and compression on client.

    But backup still not running well, backup pending after 40 minutes and 60 minutes.

    Total size db around 6.4TB

  • Re: MSSQL Backup pending every 40 - 60 minutes
    Posted: 11-17-2019, 5:25 PM

    Hi edp, I had a look at the log file you attached and file Firewall Configuration on the sql server is very poorly configured.  For example, you have four overlapping communication rules for port 8403 back to the CommServe.  Given that you are using data interface pairs to communicate over different NIC's I would suggest you look into this documentation too - https://documentation.commvault.com/commvault/v11/article?p=7140.htm.  Also for improved communication speeds to the MediaAgent, I suggest using eight tunnels per route - https://documentation.commvault.com/commvault/v11/article?p=59417.htm.

    [general]
    keepalive_interval=30
    tunnel_init_interval=30
    force_incoming_ssl=0
    lockdown=1
    proxy=0
    bind_open_ports_only=0
    keep_history=1
    dynamic_tppm_iface=localhost
    dynamic_tppm_ports=any
    [http-proxy]=NO
    [incoming]
    tunnel_ports=8403
    [outgoing]
    srv9-dbkpstprm srv9-bak-com1 remote_guid=D7971EE7-91AC-496D-8463-9EFF5CD6EFC4 fallback=1 type=persistent proto=http cvfwd=srv9-hdps-com1:8403 encryption=med
    srv9-dbkpstprm srv9-bak-com1 remote_guid=D7971EE7-91AC-496D-8463-9EFF5CD6EFC4 fallback=1 type=ondemand proto=http cvfwd=srv9-hdps-com1:8403 encryption=med
    srv9-dbkpstprm srv9-bak-com1 remote_guid=D7971EE7-91AC-496D-8463-9EFF5CD6EFC4 type=persistent proto=http local_iface=172.23.76.142 cvfwd=172.23.85.188:8403 encryption=med
    srv9-dbkpstprm srv9-bak-com1 remote_guid=D7971EE7-91AC-496D-8463-9EFF5CD6EFC4 fallback=1 type=ondemand proto=http local_iface=172.23.76.142 cvfwd=172.23.85.188:8403 encryption=med
    srv9-dbkpstprm srv9-hdps--med2 remote_guid=D54E7E29-E69C-4A2A-ACC6-ED513F68D47B type=persistent proto=http local_iface=172.23.76.142 cvfwd=172.23.85.187:8403 encryption=med
    srv9-dbkpstprm srv9-hdps-med1 remote_guid=B7BAC9ED-BE64-4628-BB38-4C615EA67235 type=persistent proto=http local_iface=172.23.76.142 cvfwd=172.23.85.186:8403 encryption=med
The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy