@Neeraj If this is urgent and you’re expecting assistance to resolve asap, you need to raise a support incident for the Commvault support team to review / provide guidance.I’d also suggest refraining from showing site specific content / data (e.g. server names etc). In the meantime, I’ll see what I can dig up and share with you.Regards,Chris
@Neeraj Just so I understand this, why are we wanting to disable the subclient backup activity? If the SLA is the concern, let’s just disable the SLA option on these subclients?Steps are here: https://documentation.commvault.com/2024/expert/configuring_sla_and_strike_settings_for_subclients.htmlThere are only 6 subclients so shouldn’t take long to manually update.. unless I’m misunderstanding something.Regards,Chris
Hi @carvalhos Are you referring to this? https://documentation.commvault.com/2024/expert/sql_server_restore_to_hot_standby_server_01.html Or are you talking about the Commserves SQL Database? (CS Live Sync)?If you’re talking about SQL itself, you would apply the latest logs with recovery option enabled (apply log backups only) as per these isntructions here:https://documentation.commvault.com/2024/expert/restoring_sql_transaction_logs_to_hot_standby_server.html Hopefully this helps!Regards,Chris
@Aishwarya B Pillai For any further University access issues, partner users please email TechEnablement@commvault.com. For end customers, you should contact Registrar@commvault.com helpdesk.Regards,Chris
@kiran Hope you’re well.Good question… the answer is here: https://documentation.commvault.com/2023e/essential/updating_commvault_software_on_server_group_01.html To perform database maintenance for the CommServe computer and the clients that have server packages installed, such as the Web Server and Workflow Engine, move the Run database maintenance (includes checkdb and reindexall) toggle key to the right. It doesn’t ‘stop’ your database, it just does a checkdb and reindexall where required, it won’t restart services or anything like that if that’s your concern (the dbmaintenance portion).It’s also only applicable to servers that have the above packages installed… so those clients i doubt would.Regards,Chris
@mach123 What are the specs of the VM? Does it meet our system requirements? (and the requirements for each component you have installed on it… e.g. is it a Commserve + Media Agent?)CS H/W Requirements are here: https://documentation.commvault.com/2023e/expert/hardware_specifications_for_commserve_server_01.htmlMA H/W Requirements are here: https://documentation.commvault.com/2023e/expert/hardware_specifications_for_mediaagents.html We have a couple of regkeys we can utilise to prevent certain processes from consuming cpu/memory but it might negatively impact the software.. Any particular process consuming the most resources? Also make sure SQL 2019 is patched.Regards,Chris
Hi @JonDoe Yes they can.Only limitation we’re aware of is that since the OS is RHEL 7, you won't be able to restore from Linux-based VMs installed with newer release versions than the proxy. Here’s the article: https://documentation.commvault.com/2023e/expert/linux_proxy_support_for_vsa_with_vmware.htmlRegards, Chris
Hi @drPhil That’s interesting… I’d probably raise a support case if possible to try identify what has changed in this release that prompted this issue.Before you try to add the DAG node, could you ensure the DAG members have the exchange agent installed and configured?Installing the agent won’t be enough, you’ll need to ensure the agent itself is configured as per: https://documentation.commvault.com/2023e/expert/adding_exchange_database_agent.html Please let me know if that helps?Regards,Chris
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.