How to create new client for NAS/Network Share using workflow/command line

Last post 09-06-2018, 5:54 AM by johanningk. 4 replies.
Sort Posts: Previous Next
  • How to create new client for NAS/Network Share using workflow/command line
    Posted: 08-27-2018, 8:37 AM

    How to create new client for NAS/Network Share using workflow/command line. I couldn't find an xml code.

  • Re: How to create new client for NAS/Network Share using workflow/command line
    Posted: 08-27-2018, 8:38 AM

    Is this what you are looking for? http://documentation.commvault.com/commvault/v11/article?p=19766.htm

  • Re: How to create new client for NAS/Network Share using workflow/command line
    Posted: 08-27-2018, 8:56 AM

    Hi jszutarski,

    No, We are looking xml code for Nas network share [Unix] Pseudo client.

  • Re: How to create new client for NAS/Network Share using workflow/command line
    Posted: 08-28-2018, 11:52 AM

    Got a xml code but it needs improvement in below, its creating psuedo client of nas network share for both Windows and Unix iDA. Need the control over the code on creating Windows [CIFS] or Unix[NFS] type iDA. Can anyone assist on this please.

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

    <clientInfo>
    <clientType>NON_NDMP_CLIENT</clientType>
    <openVMSProperties>
    <cvdPort>0</cvdPort>
    <userAccount>
    <userName></userName>
    </userAccount>
    </openVMSProperties>

    </clientInfo>


    <entity>
    <clientName>Test</clientName>
    <hostName>Test</hostName>
    </entity>


    <registerClient>false</registerClient>

    </App_CreatePseudoClientRequest>
  • Re: How to create new client for NAS/Network Share using workflow/command line
    Posted: 09-06-2018, 5:54 AM

    please try the following:

    <App_CreatePseudoClientRequest>
    <clientInfo clientType="18">
    <nonNDMPClientProperties osType="1"/>
    </clientInfo>
    <entity clientName="dummy"/>
    </App_CreatePseudoClientRequest>

    execute as follows

    qoperation execute -af file.xml -clientName "myClientName" -osType "1" (for Windows)
    qoperation execute -af file.xml -clientName "myClientName" -osType "2" (for Unix)

    if both types are needed use:

    <App_CreatePseudoClientRequest>
    <clientInfo clientType="18"/>
    <entity clientName="dummy"/>
    </App_CreatePseudoClientRequest>

    Both Scripts do not create NDMP / NAS agent configuration for the new client
    IPs / hostnames are not needed for these pseudo Clients, since final target is addressed by subclient content

    have fun
    Klaus

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