Resuming VMWare VSA Backup After Going Pending

Last post 02-05-2020, 9:37 AM by Liam. 1 replies.
Sort Posts: Previous Next
  • Resuming VMWare VSA Backup After Going Pending
    Posted: 02-05-2020, 9:15 AM
    Resuming VMWare VSA Backup After Going Pending


    We have a VM that is about 5 TB and takes more than 24 hours for a bull backup which we do once a month.

    The latest month end job was running for close to a day and in the job controller it stated that the MA was ---MA1.

    I stopped and then restarted the services on ---MA2 due to a different restore issue on another server (I've got a ticket started about that issue)
    and the VM backup job went pending.

    It was about 75% complete when this happened. Another user killed this particular job when they saw that it was in a pending state.

    Would I have been able to resume this job and continue on? Also would it automatically restart from the beginning and take another full day to complete?


    4640 894 02/03 07:10:54 157388 VSBkpCoordinator::UpdateJobManagerVMList_Restart() - This is a new job
    4640 894 02/03 07:10:54 157388 vsJobMgr::updateVMBkpJobStatus() - Sending VM status for [1] virtual machines
    4640 894 02/03 07:10:55 157388 VSBkpCoordinator::calculateRequiredStreams() - There are [1] VMs and [2] Disks to be processed by a max of [4] streams
    4640 894 02/03 07:10:55 157388 VSBkpCoordinator::calculateRequiredStreams() - [1] streams have been allocated, [2] streams are allowed, [1] additional streams will be requested
    4640 894 02/03 07:10:55 157388 VSBkpCoordinator::InitStreams() - Streams will be distributed by agent resource percentage
    4640 894 02/03 07:10:55 157388 VSBkpCoordinator::InitAgents() - Adding [---ma1] as a remote agent
    4640 894 02/03 07:10:55 157388 CVRemoteAgentServer::AddAgent() - Added Agent [---ma1]
    4640 894 02/03 07:10:55 157388 VSBkpCoordinator::InitAgents() - Adding [---ma2] as a remote agent
    4640 894 02/03 07:10:55 157388 CVRemoteAgentServer::AddAgent() - Added Agent [---ma2]
    4640 894 02/03 07:10:55 157388 VSBkpCoordinator::InitAgents() - Adding [---vsa1] as a local agent
    4640 894 02/03 07:10:55 157388 CVRemoteAgentServer::AddAgent() - Added Agent [chlvsa1]
    4640 894 02/03 07:10:55 157388 VSBkpCoordinator::InitAgents() - Adding [---vsa8] as a remote agent
    4640 894 02/03 07:10:55 157388 CVRemoteAgentServer::AddAgent() - Added Agent [---vsa8]



    4640 894 02/04 10:39:25 157388 VSBkpCoordinator::DumpStreamInfo() - StreamId = 3, RCID = 892088, ReservationId = 668242, MediaAgent = [---ma1], Agent = [] [Released]
    4640 894 02/04 10:39:25 157388 VSBkpCoordinator::DumpStreamInfo() - StreamId = 2, RCID = 892090, ReservationId = 668245, MediaAgent = [---ma1], Agent = [---ma1] [Assigned]
    4640 894 02/04 10:42:17 157388 CVRemoteAgentSession::receiveObject() - Failed to receive object. Error : [0x80070306:{CCvNetwork::ReceiveXMLMessage(3899)} + {CCvNetwork::CheckIfDataAvailable(5247)/---ma2/---ma2/:0/0 vsbkp.exe(10088:6b0)} + {CCvNetwork::CheckDataWaiting(5915)} + {CSessionConnectionSocket::CheckDataWaiting(719)/W32.774.(One or more errors occurred while processing the request.)-Ioctl returned zero waiting bytes; Connection has been lost}]
    4640 894 02/04 10:42:17 157388 CVRemoteAgentServer::RecvMsgsFromAgents() - Failed to receive message from agent [---ma2], stopping agent
    4640 894 02/04 10:42:17 157388 VSBkpCoordinator::OnAgentStopped() - Agent [---ma2] has stopped
    4640 894 02/04 10:44:35 157388 VSBkpCoordinator::OnIdle_Running() - Waiting for [1] VMs to be processed. [---sea21]
    4640 894 02/04 10:44:35 157388 VSBkpCoordinator::DumpStreamInfo() - StreamId = 3, RCID = 892088, ReservationId = 668242, MediaAgent = [---ma1], Agent = [] [Released]
    4640 894 02/04 10:44:35 157388 VSBkpCoordinator::DumpStreamInfo() - StreamId = 2, RCID = 892090, ReservationId = 668245, MediaAgent = [---ma1], Agent = [---ma1] [Assigned]
    4640 894 02/04 10:49:45 157388 VSBkpCoordinator::OnIdle_Running() - Waiting for [1] VMs to be processed. [---sea21]


    It looks to me like this job would have been able to continue, but I'd like to know in case it happens again.

    Thanks in advance.
  • Re: Resuming VMWare VSA Backup After Going Pending
    Posted: 02-05-2020, 9:37 AM
    • Aplynx is not online. Last active: 04-01-2020, 9:30 AM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,818

    It depends on the error that you were seeing, but yes in general you can resume the job and it should run. 

    Killing the job should have caused it to 'commit' unless the force option was used, so you should have at least 75% of the data available to restore. 

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 © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy