How to make a run backup copy for VSA subclient in workflows?

Last post 09-06-2018, 4:00 PM by bstibal. 1 replies.
Sort Posts: Previous Next
  • How to make a run backup copy for VSA subclient in workflows?
    Posted: 08-28-2018, 5:55 AM



    I have a vCenter with few datastores in it and to backuped these, I create a snapshot through CommVault and run a backup copy of it manually, one by one.


    But we waste time to verify the status of each datastore backup manually. I tried to create a workflow to backup all the datastore one after another by making a snapshot, run a backup copy and making a snapshot of the second datastore, run its backup copy and so on.


    Currently, I can iterate with the ForEach and make a Snapshot with a Backup activity but I didn't find how to run a backup copy after the Snapshot backup.


    Could you please help me?

  • Re: How to make a run backup copy for VSA subclient in workflows?
    Posted: 09-06-2018, 4:00 PM

    Not understanding why you need to run the Backup Copy manually? There is the advanced option in the schedule policy to “Create Backup Copy immediately”

    In case I am not understanding the requirements, you could start a Backup Copy with the xml listed at the end. Make sure to change the following parameters: <subclientName>, <backupsetName>,      <instanceName>, <appName>, <clientName>, & <storagePolicyName>

    You could then get the JobID of the backup copy using XPathQuery and then use WaitForJobCompletion

    The issue with that is if you have multiple clients using the Storage Policy, starting the Backup Copy could result in more than the 1 Snap you are interesting in being processed and the  WaitForJobCompletion would wait for all Snaps to be processed that were available at the time the Backup Copy was started.


    <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
















          <appName>Virtual Server</appName>

          <clientName>PROD VCenter</clientName>










































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