Virtual Server Restore Issues from proxied MA

Last post 11-18-2010, 11:05 AM by Vincenzo_Basolino. 3 replies.
Sort Posts: Previous Next
  • Virtual Server Restore Issues from proxied MA
    Posted: 11-15-2010, 12:01 PM

    Hi all, we recently uncovered an issue in testing, we are unable to restore either file level or container restore (entire VM) from virtual jobs that are proxied.  A while back it was recommended to us to proxy out all the virtual jobs to our other MAs from one MA, for scheduling simplicity. 

    So all of our virtual jobs are scheduled through gmc0151, which then proxies the jobs out between itself, and 3 other MAs.  If we restore a job from gmc0151 it works, if we try to restore from a server that was proxied we get the below:

    What am I doing wrong?  Also, it seems I have to initiate the job through gmc0151, because if I try to initiate from another server I am unable to view the necessary backup data.



  • Re: Virtual Server Restore Issues from proxied MA
    Posted: 11-15-2010, 2:01 PM

    Can you check if the index path specified has data within it?  It sounds like it tries to restore the data to that index path and fails accordingly.  I'm going to assume all involved machines are on sp5 (so please double check this).

  • Re: Virtual Server Restore Issues from proxied MA
    Posted: 11-15-2010, 3:37 PM

    Yep, all machines are SP5.  The index location does exist on gmc0150 but 4 files are 1KB each, and the index location doesn't exist on gmc0153.


  • Re: Virtual Server Restore Issues from proxied MA
    Posted: 11-18-2010, 11:05 AM

    Can you rename the containing folder just above the one containing the 4 files in the index on gmc0150 and then reattempt the restore?  Alternately you can specify the browse media agent specifically to control which MA is processing the recovery.

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