Get help with your As-a-Service deployments and workloads (formerly Metallic)
Recently active
SaaS-delivered Cyber ResilienceCommvault Cloud provides a streamlined SaaS solution for data management and protection, featuring easy deployment, low overhead, and simple subscription pricing. It offers unique storage flexibility with options for cloud or on-premises storage to optimize hybrid cloud workload recovery. With automatic upgrades, maintenance-free operation, scalable architecture, and robust security, Commvault Cloud ensures future-ready data protection as IT needs evolve.Scalability: Easily scales to meet growing data demands without the need for significant hardware investments. Cost Efficiency: Reduces upfront capital expenditures and lowers total cost of ownership by leveraging a subscription-based model. Simplified Management: Offers centralized management capabilities that reduce the complexity and resources required to manage data protection. Automatic Updates: Ensures the latest features and security updates are automatically implemented without disrupting business
We are excited to announce a new Kubernetes subscription coming to Commvault Cloud on May 31, 2024. As part of our commitment to enhancing our services, we are implementing changes to the metering and billing process for Kubernetes environments protected in Commvault Cloud.What’s changing?Commvault Cloud Backup & Recovery for Kubernetes will be metered using capacity (front-end terabyte) instead of per-app licensing.How do I protect my Kubernetes Environments going forward?There is no change in how your Kubernetes data is protected. However, Kubernetes usage will be metered using a new Kubernetes subscription instead of the existing VM and Kubernetes subscriptions. How do I benefit?This change simplifies the Kubernetes environment licensing and makes sure your data protection needs are easier to size and scope for future planning.What if I am already protecting Kubernetes Environments using the VM & Kubernetes subscription?If you are currently protecting Kubernetes environments
Welcome to the Commvault Cloud Family! 🎉Hello and a heartfelt welcome to each one of you! We're thrilled to have you as part of the Commvault Cloud family. Our commitment is to make your journey to our platform both seamless and enriching.Why Engage with Your Customer Success Resources? 🤔While not every customer will have a dedicated Customer Success Manager (CSM), every one of you is important to us. Whether you're self-onboarding using our extensive resources or interacting with our team, our goal is to understand your unique needs and assist you in making the most out of Metallic.Tailored Guidance: Regardless of your plan, our resources are designed to offer advice specific to your objectives, ensuring optimal use of our platform. Efficient Onboarding: Utilize our videos, documentation, and community posts to onboard at your pace, effectively and efficiently. Continuous Support: For any queries, feedback, or suggestions, don’t hesitate to reach out to us via this platform or succ
Whether you're a seasoned Metallic user or a newcomer, having the right resources at your fingertips is essential. This post aims to provide some key info for you. Community Interaction: 🗣️Our Community forum is an enriching space for you to ask questions, share best practices, and connect with both peers and Metallic experts. While many of your queries will find answers here, we've also compiled other crucial resources to bolster your Metallic experience. Key Resources to Bookmark: 📌Metallic.io:While it's our company website, its utility goes beyond basic information. Consider this your starting point if you ever feel lost. From release notes, case studies, and white papers to updates about our upcoming webinars – everything's there.Status Page 🚦Check the Ring status page to confirm the scheduled maintenance activity timings and window size. URL: https://ring-status.metallic.io/ For example, to check the Ring M102 scheduled maintenance activity window, access the following URL:: ht
Commvault Cloud supports the protection of Amazon Aurora and Amazon RDS instances in single and multi-AZ configurations using native RDS automated backups, allowing for point-in-time recovery (PITR). To enable the PITR for Amazon Aurora and Amazon RDS, additional permissions for RDS APIs are required to be added to a policy in the user account. These permissions allow for enabling the RDS automated snapshots with appropriate retention, thereby protecting the database transactional log files. What steps should be taken to enable the PITR for the Amazon RDS database? The following steps should be followed in the AWS Console:Sign into the AWS Management Console and Open the IAM (Identity and Access Management) console of the appropriate AWS user account at https://console.aws.amazon.com/iam/. In the navigation pane, choose Policies. Search for the policy named either MetallicRole-RDSPolicy or MetallicTenantRole-RDSPolicy. Choose the Permissions tab and click on Edit to add the set of p
Currently using Metallic and receiving the error message for several clients that jobs are already in progress but not able to locate the job. Has anyone else seen this issue?
Hi team,We are taking the backup through the metallic endpoint one laptop folder (email folder) include 2 PST file but only data backup showing only folder name (email folder) no include PST file name.
We started using Metallic O365 backups back when it was Infinite Retention. We have reached 70% of our Quota in just a little over two years and would like to investigate why. We manage Storage in our On-Prem Commvault by setting the retentions below. I do not find these granular settings in the Cloud Portal.Can I set these specific retentions within the Metallic Office 365 Backup Environment? I want to start with our standard retention limit, Daily, Weekly, Monthly, Yearly.Daily - 7 CopiesWeely - 5 Copies (Each Saturday)Monthly - 12 Copies (Last backup of each day of Month)Yearly 5 Copies - (Last backup of each year)
It seems that the api to GET the credential returns endpoint with a different key as compare to what is expected by PUT api for updating the credential . API : /commandcenter/api/v5/credential/:credentialidEven from the document the key name is different from what is returned. As you can see from actual output , we get extra “Endpoint” in the key name. This results the automation of GET and PUT request , to remove the endpoint completely . I agree that we can modify it in the automation before hitting PUT , but I still feel this is a BUG. Any one faces / observed this issue ?
Hello Metallic Community,I am seeking guidance on two specific queries related to our Azure VMs, particularly SQL Servers, which are being backed up using Metallic.Backup Consistency for Azure VMs:Can someone clarify whether backups taken through Metallic for Azure VMs are application-consistent (e.g., using VSS for Windows) or crash-consistent?If there are any settings or configurations that need to be enabled to ensure application-consistent backups, kindly share the details.Best Practices for SQL Server Upgrades:We are planning an upgrade for our SQL VMs hosted on Azure. What are the recommended steps to ensure data protection and smooth rollback in case of any issues?Should we rely on existing Metallic backups, capture a manual snapshot, or consider creating a clone of the SQL VMs as a precautionary measure?I would greatly appreciate any insights or experiences from the community regarding these points. Your recommendations will help us implement the best possible backup and recove
I am trying to export the old backed up mailbox to a PST but it showed error that “Selected items size [43524715222 bytes] exceed max size allowed to export [26843545600 bytes]”. I could not split the folder as it is just one folder [Inbox]. Any idea how to resolve this? Thank you.
Hi ,In Salesforce I just refreshed a fulldev sandbox , does the sandbox has to reconfigured again ? Is there any documentation for this?
Hi community, Recently we started using Metallic as our backup solution for our Salesforce. There is a field in Salesforce generated automatically as an external ID. I wonder if there is any possibility to remain the same external ID when doing the restore. I tried the record restore and it seems Salesforce generated a new ID. Thanks.
I have several VMs that are supposed to be backing up. . . but for whatever reason, the job gets killed. No error message or code (it says, “not applicable). . . No idea why they are getting killed. I’m new to BDR and CommVault, so please talk to me like I”m 5
How can manage location wise endpoint laptops through the one user in the metallic?
