Dyncache Settings for Simpana 8.0 Media Agents

Last post 09-24-2011, 10:11 AM by Mike M.. 0 replies.
Sort Posts: Previous Next
  • Dyncache Settings for Simpana 8.0 Media Agents
    Posted: 09-24-2011, 10:11 AM

    I recently upgraded to Commvault 8.0 sp5 from 7.x and it has been running fine for the last several months. I just then added new data domain appliances in all locations and via gridstore license configured additonal data paths for each storage policy making them the default for the sake of aging off from the old mount paths. The data path configuration for each is set to "use preferred data path".

    The symptons I have are as follows:

    All of the media agents stop responding at random each night during backups. They are pingable and you can manage the services using computer managment remotley but cannot RDP or login to them via console. They have to be power cycled.

    The jobs themselves remain in the job controller as if everything is working or running. There are no errors but there also is no progress on the jobs.

    After power cycling, the jobs will either go pending, update index failed restarting job most common, or will simply resume.

    It might finish or it might not and the media agent will need to be bounced again.

    The worst part is that there are absoluteely no windows errors in the event logs to help direct me and support has been reviewing the commvault logs and basically telling me the errors I already see with the update index and unable to access mount path which usually occurs after the issue starts on the media agent.

    The last information I got from support was install DYNCache. When I checked my media agents it seemed to already be in the registry and in the system32 folder but an older version then I was copying over. I'm not sure this is going to address my issue but I remain open to try anything at this point.

    Does 7.0 or 8.0 come with dyncache?

    What would be the recommened settings for Dyncache on a DL360 G5, 4 GB ram, Windows 2003 64 bit server with 8.0 update 5? Not using single instancing, not using archiving and writing directly to a data domain/SAN and tape library.





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