Requirements to run CV CLI scripts on a remote workstation?

Last post 10-01-2018, 10:33 AM by Sky. 3 replies.
Sort Posts: Previous Next
  • Requirements to run CV CLI scripts on a remote workstation?
    Posted: 09-27-2018, 2:27 PM

    Goal:  I would like to run Commvault scripts that I have saved in the Commcell Console and run them on a remote workstation.  I would be nice to also keep saved authentication in them so they can run automatically via a third party scheduler.

    Can someone point me in the right direction on how to get started?  What do I need installed on the remote Windows workstation?  Where can I aquire that?  What syntax do I need to connect the CommVault Server?  How can I run this with saved authentication so they can run automatically?

    Thank you.

  • Re: Requirements to run CV CLI scripts on a remote workstation?
    Posted: 09-28-2018, 2:18 AM

    I believe this contains all the information your looking for:

    http://documentation.commvault.com/commvault/v11/article?p=45108.htm


    Jos Meijer
    Senior Technical Consultant
  • Re: Requirements to run CV CLI scripts on a remote workstation?
    Posted: 10-01-2018, 10:15 AM

    Thanks for the reply, I did come across that article too.  What I could not find in it is if there is a installation piece on the remote workstation to run the "q" commands from the local workstation command prompt.  I.E.  Do I need anything installed on the remote workstation to run qlogin...

    E:\commandline>qlogin -cs server1 -u user1
    Password:

  • Re: Requirements to run CV CLI scripts on a remote workstation?
    Posted: 10-01-2018, 10:33 AM

    For the qcommands, you will need the File System Core at a minimum - follow standard deployment to suit your needs (push install, silent install, etc.)

    Alternatively, if you don't desire the commvault agent on that host to execute commands, recommended path would be to use REST API instead via favourite tool (PowerShell, python, whichever favourite tool has a http library).   

     

    Command parity is there between qcommand and REST API - and if you're submitting a XML blob straight into the message bus, you can call QOperation Execute via REST API as well (BOL Developer section -> http://documentation.commvault.com/commvault/v11_sp13/article?p=48618.htm & https://api.commvault.com/ )

    Full REST API library here

    http://documentation.commvault.com/commvault/v11_sp13/article?p=45619.htm


    Cheers,
    Luke
    (@cv_skywalker)
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