Storage Policy only with Index Client

Last post 04-27-2019, 1:25 AM by Wwong. 1 replies.
Sort Posts: Previous Next
  • Storage Policy only with Index Client
    Posted: 04-26-2019, 11:48 AM

    So I had a OCUM clients that were migrated over NetApp Open replication with a new storage policy. The OCUM storage policy now is orphan and just sitting in my commcell with only its IndexServer client associated to it. 

    When I try to disable the storage policy, it says that I should reassociate its clients to a different storage policy before disabling it. No more backups will be performed using the OCUM storage policy, however I cant disable the storage policy anyway. 

     

    1- How do disable the storage policy?

    2- Should I disable backup activity for the OCUM IndexServer client?

    3- Usually when it is a new client, you have the option to leave Storage Policy field blank, but once you assign one, you can no longer leave it blank. Why is that?

    Thanks

  • Re: Storage Policy only with Index Client
    Posted: 04-27-2019, 1:25 AM

    Hi pereirath

    For this dedicated Storage Policy for the OCUM client, is this purely use for Snap Backups, do you have configuration for Backup Copy (where snap backup are written in CommVault manner) to Disk or Tape?

    If Backup Copy is setup, we would recommend to leave it, as it can still be used for restore purpose. 

    In relation to the disabling Storage Policy, because there are client association (i.e. Index Client), the only method is to do the following:

    • At the Storage Policy Level, right-click Properties -> Associated Clients.
    • If you are sure you want to move the client association, you can select the Client and choose 're-associate"
    • Once the above is done, you should be able to disable the Storage Policy 
    In relation to your other two questions:
    • 2- Should I disable backup activity for the OCUM IndexServer client?
      • If you are on SP13 and later, where Index Server is setup at the Storage Policy level, if the OCUM SP is not required it should be safe to disable the backup activity
    • 3- Usually when it is a new client, you have the option to leave Storage Policy field blank, but once you assign one, you can no longer leave it blank. Why is that?
      • This is by design, so the system can ensure the Client are backed up correctly. 
    Hopefully this helps 
     
    Regards
     
    Winston 
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