VMware SAN Backup Failure

Last post 05-24-2017, 12:01 PM by Liam. 5 replies.
Sort Posts: Previous Next
  • VMware SAN Backup Failure
    Posted: 05-22-2017, 9:55 AM

    Hello All,

    After I upgraded the system from v10 to V11 , I sometimes can take SAN backup sometimes not. I have presented datastore to the media agent and they are succesfully. 

    I can take normal NBD backup. When I check the log I can see that error. 

    do you have eny idea please? I have also added job log file

     Agent [cocmvltma01] has started
    11324 24ec 05/22 16:28:17 418877 VSBkpController::OnAgentStarted() - Agent has started
    11324 3268 05/22 16:28:28 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:28:38 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:28:48 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:28:58 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:29:08 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:29:18 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:29:28 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:29:38 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:29:48 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:29:58 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:30:08 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:30:18 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:30:28 418877 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize. [cocmvltma01]
    11324 3268 05/22 16:30:38 418877 VSBkpCoordinator::OnIdle_Starting() - Timeout waiting for agent [cocmvltma01] to initialize.
    11324 3268 05/22 16:30:38 418877 VSBkpCoordinator::OnIdle_Starting() - No Agents are running, stopping
    11324 3268 05/22 16:30:38 418877 CVRemoteAgentServer::MonitorAgents() - There are no running agents
    11324 3268 05/22 16:30:38 418877 VSBkpCoordinator::Run() - VM COSERVERINFO --> NOT_STARTED
    11324 3268 05/22 16:30:38 418877 VSBkpCoordinator::Run() - VM PSCOPSAP04 --> NOT_STARTED
    11324 3268 05/22 16:30:38 418877 VSBkpCoordinator::Run() - ===== JOB SUMMARY REPORT BACKUP PHASE =====
    11324 3268 05/22 16:30:38 418877 VSBkpCoordinator::Run() - Total VMs to backup [2]
    11324 3268 05/22 16:30:38 418877 VSBkpCoordinator::Run() - VMs not processed [2]
    11324 3268 05/22 16:30:38 418877 VSBkpCoordinator::Run() - ===========================================
    11324 3268 05/22 16:30:38 418877 VSBkpCoordinator::Run() - no VMs were processed successfully, job will go to pending.
    11324 3268 05/22 16:30:39 418877 vsIndexClient::Close() - Closed indexing connection to [cocmvltma01]
    Attachment: log.txt
  • Re: VMware SAN Backup Failure
    Posted: 05-22-2017, 10:15 AM
    • Aplynx is not online. Last active: 06-25-2019, 2:53 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,632

    Can you add this key to the proxy(s) involved and set it to false?

    https://documentation.commvault.com/additionalsetting/details?name=
    %22bEnableSanDatastoreDispatch%22&id=

    See if the backup runs at that point. What service pack are you on for 11?

  • Re: VMware SAN Backup Failure
    Posted: 05-24-2017, 4:42 AM

    Hello Liam,

    It is v11SP6. I will add the key and try and share the results here.

    Thank you

  • Re: VMware SAN Backup Failure
    Posted: 05-24-2017, 6:07 AM

    Hello Liam,

    we want to take SAN backup. The additional settings which you sent me is for disabling SAN backup.

  • Re: VMware SAN Backup Failure
    Posted: 05-24-2017, 6:46 AM

    etoman:

    Hello Liam,

    It is v11SP6. I will add the key and try and share the results here.

    Thank you

    I'd recommend updating to SP7; there is a known issue that can affect some san configurations.

     

    etoman:

    Hello Liam,

    we want to take SAN backup. The additional settings which you sent me is for disabling SAN backup.

    That setting is not for disabling san backups, but disabling the detection that is done to ensure that VMs are processed by proxies that have access to the san datastore.  If all of your proxies have access to the san datastores then this dispatching isn't required.  San mode can still be used even if the VM wasn't assigned to the proxy based on its san accessibility.  However, i'd still recommend upgrading to SP7 over adding in this key.

     

     

  • Re: VMware SAN Backup Failure
    Posted: 05-24-2017, 12:01 PM
    • Aplynx is not online. Last active: 06-25-2019, 2:53 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,632

    It disables an additional scan that is timing out to quickly causing the error. Service Pack 7 will correct this and revert the key back. Until then use the key to run the backups. 

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