Commvault Initial Setup

VladanKojanic
Head of Information Technology Group at Ministry of Environmental Protection
For me, the initial setup was not so complicated, because I'm an IT guy. I understand what is needed. But if I look at it from the point of view of someone else, it's still not too complicated. The documentation is very well written and tells you what you need to do next. Of course, you need to know some rules about backups, but the installation is usually done by guys and girls who are in that field. A regular user will likely never install Commvault by him or herself. And even though I am not a technician and I am not a backup engineer, the setup was okay for me. I was able to understand what the system was asking and what I needed to do. In terms of how long the deployment took, we tested it just to see if we could back up a part of our database. We have two networks. One is the primary, official, and public network, and the other has secret information. So we tested backing up both of them. Including testing, the deployment took around two months from zero to putting everything on. That also included deploying it on our system, connecting it with our storage, our databases, and installing it on some clients to see how the clients work. Our implementation strategy for Commvault was very simple: Do it fast and secure all the information we need. We needed to back up everything we had. We just wanted to do it correctly, by the book, and to protect everything. View full review »
Sheron K Brown Sr.
Systems Engineer at PAREXEL International Corporation
To convert over to Commvault from NetBackup took us three days, and part of that was standing up the environment. With Commvault, it's easy to bring new data and new platforms in. It's simply a matter of clicking on the agent, installing it, and then going from there. The fact that it's agent-based made it a little bit easier to adapt to and back up multiple platforms and storage devices. Generally, it takes about five hours to two days to drop an architected solution and start the implementation process. You need time for whatever issues may arise, so it could take three to five days to get Commvault up and running. But to get started, it's just a matter of a few minutes. The fact that you can push out and do all your installs from Command Center is a good feature from Commvault. It's easy to get rolling and get started. To really get it fully leveraged takes some time. Our company is in its fourth year with Commvault and we're just now getting to the tip of the iceberg with leveraging a lot of its features and the licensing that Commvault offers as a data warehouse. Training-wise, there's a lot of information out there, a lot of free training. There are tutorials and a lot of YouTube videos and virtual classrooms. They encourage you to learn and leverage their data suite without paying for a lot of training. View full review »
Jean-Christophe Bettinelli
Data Retention & Backup Specialist at a tech services company with 51-200 employees
The setup is complex. I would definitely recommend using Professional Services for implementing Commvault. This is not something you should be doing on your own, especially in large environments. When I say "large environments," Commvault has to be really well-sized in terms of the resources that you assign to the servers or the components that you need to put in place for the backup. If you don't put the right components in place or you don't think about the global picture from the beginning, you may have trouble. You could recover from this, but it's better to have people with experience who will help you to do the right sizing from the beginning. They have experience with areas where you may need to pay more attention, and you're sure to have a successful deployment from the beginning. In our large environment, it took more than one year to deploy it for the aspects that we wanted to back up. It is not only a large environment but it's complex, based on different software and different hardware vendors that we wanted to integrate. So it took some time to accomplish what we wanted to accomplish. We back up more than 5,000 virtual machines and we have deployed more than 1,900 agents in our infrastructure. View full review »
Learn what your peers think about Commvault. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
442,517 professionals have used our research since 2012.
Brijesh Parikh
Senior Architect, Cloud Infrastructure at a tech vendor with 501-1,000 employees
The deployment took about a month. The planning was another month or two. We wanted to ensure that we were able to protect all our systems and data not protected up until then. At the same time, the strategy was that we did not want to incur a lot of significant costs on just deploying the solution itself. Plus, we did not want a lot of administrative overhead while maintaining the servers and application environment. We did not want that routine daily administration activity. We wanted to set up the environment and not worry about it until something went wrong. View full review »
Filip Hasa
Backup Engineer at a pharma/biotech company with 10,001+ employees
The initial setup was really easy for me because I already had experience with NetBackup and TSM. It wasn't difficult for me to understand Commvault's logic. But, in my opinion, it's very easy to understand because the logic involved is minimal yet it offers a lot of configurable options. Because the process for the installation of agents, such as for databases and applications, is fully automated, you don't need to touch the application at all. That is one of the main reasons I prefer Commvault over other tools, where you always need to touch the client. A basic implementation of Commvault depends on the size of the company. Installation of the server takes a couple of hours, but that is the same as with other backup tools. But the installation of it on clients and their configurations will take days if you don't want to customize it because Commvault comes with pre-defined groups. The process will take a number of days for a small company. In terms of staff for deployment and maintenance, it could be just one person involved, depending on the roles of the people in the company. This person has to be able to do a lot of things, so it depends on whether he has these responsibilities and the capabilities. We have about 100 users of the solution because we have a lot of operations. View full review »
MatthewMagbee
Datacenter Manager at a healthcare company with 5,001-10,000 employees
The setup is extremely easy. The first time I did it I was a little worried that I didn't do it properly because it was so easy. The overall configuration is a little bit more difficult, but that's roadmap-based configuration, so you have to think very far down the road when putting this together. You can't be thinking, "Oh, I only need this for a couple of months." It's a 10-year plan. The setup itself took a couple of hours. View full review »
Mostafa Atrash
Sr. Enterprise Solutions Engineer at CMC
With Commvault, if you need basic integration and configuration but no advanced features, then you can do the setup in maximum three to four hours. However, if you need to do everything, you will need everything to be organized for you to work. View full review »
Javier_Gonzalez
Head of Virtualization and Backup Infrastructure at a healthcare company with 5,001-10,000 employees
The initial setup was not complex for me. If you know the tool it's not complex. It could be a little complex for newer people because there are a lot of features. For a beginner, it's really not the best tool. It's not a tool for small business, it's more for medium and big companies. We deployed Commvault, in this company, about four years ago, so I don't recall exactly how long it took. I think we needed three weekends to deploy and move all the data. In terms of an implementation strategy, we have a team that takes care of backups. We first planned the whole architecture, what we wanted. Then we voted on the pros and cons of the architecture elements and decided where we were going with it. In addition to help from Commvault, we had an external analyst from a third-party who helped us with the initial deployment. Our experience with them was very good. I really appreciated it. Internally, there are two of us in the organization who share the backup roles. View full review »
reviewer1273227
Data Analyst at a tech services company with 501-1,000 employees
In both my current and my previous company, I was the one responsible for the initial setup and it is straightforward. But the next step is the initial configuration and that is difficult for a less experienced person. Now, I can say that I could set it up and configure it much more quickly. From deployment to production, in my current company, took two to three weeks. Our initial setup was one CommServe, so it was a simple deployment, without disaster recovery clusterization. In addition there were two MediaAgents. We are extensively using a firewall proxy setup as well. The setup has grown over the years and now, the infrastructure of Commvault is around 50 servers. We're planning to deploy another one in another installation. The current one will be preserved as it is, and we will deploy a new one with some improvements from our side and perhaps with a different overall design. View full review »
Syed FasihUr Rahman
Enterprise Solutions Architect at a tech services company with 51-200 employees
The initial setup is straightforward. However, issues do not start at the initial setup stage. Once the environment is set up and you are going to take the backup job, pushing the enterprise policies, then problems can arise. It may be because of the backend infrastructure or the network, or something else. Whatever the issue, it is at this point where our customers sometimes need better support. When it comes to the implementation and deployment, from day one until the backup process begins, it should not take more than one week. This is for a new system. The deployment time for our enterprise-level, telecom customer was longer than average, in part because they already had an existing backup solution and they had to migrate to Commvault. It needed to be planned and implemented gradually, which required some cutoff dates. From start to finish, including streamlining the documentation and handing over everything, it took approximately one month. View full review »
Michel Scheepers
Technical Consultant at a comms service provider with 10,001+ employees
The setup of Commvault was complex but that's related to our environment. As an MSP we have very high security guidelines, so that made it hard. But that's not related to Commvault, it's related to our security environment. Our deployment took almost a year. We had to make sure our design was good before we did anything. Most time of the implementation time was in the design phase. The actual building-up of the solution was quite fast. We were done in a month, starting from scratch. For deployment and maintenance we need four to five people who are backup system admins. View full review »
MithilaPerera
Senior Technical Support Engineer at a tech services company with 11-50 employees
The setup was straightforward. We didn't have many complications. When we had to install the agents on the servers, there were some issues with authentication with the SQL database, but that was from the database side. That was sorted and there was nothing much more than the usual administrative stuff. The initial deployment took about three weeks because we had some complications with database servers. Some of them had to study the user account permissions. After that was sorted out, it was fine. Our strategy was to install it on critical servers. After the vendor installed the physical servers for Commvault, we had to download about nine to 10 GB of their setup files. After that, they installed and there were some prerequisites to complete such as .NET. After that, it was pretty easy. Once we installed we had some local support. We also had to plan and provide retention periods. View full review »
SIVASHANMUGAM NATARAJAN
CTO at Greenware Technologies LLC
The setup is not straightforward. It is a little complex. It really needs expertise, unlike other software. The deployment time depends on the size of the environment, the number of servers and the storage size. It has taken us anywhere from one week to three months. As a result of our experience in setting it up, we have created our own plan for doing so. We do a complete environment study of the client by using a solution survey sheet. That gives us complete visibility into the databases they have, the number of servers, the virtualization platform, and the physical machines. According to that, we suggest a plan for the size, if it is on-prem. We have a project management professional to make the process smoother. We have four engineers who implement Commvault and they are also responsible for maintenance. View full review »
Amin Ibrahim
Senior Systems Consultant | Virtualization at eSky IT
The setup process is complex. The person who implements it has to pay close attention to certain things. The index cache must be in SSD storage, and the same is true for the deduplication database. The sizing of the CommServe must be done well. In terms of agents, and other features, everything must be calculated very well. All these things will affect the performance in the future. It can take hours or days to implement, depending on the project. The administrative part of the deployment takes about a day, but the integration part can take from three days to a couple of months, depending on the size of the project. After we do the first implementation, the customer can do future implementations. View full review »
Praveen
Backup Administrator at a manufacturing company with 5,001-10,000 employees
With guidance from their team, and based on the documentation, it was easy to install. The deployment took one-and-a-half hours. There are updates every quarter and they are getting easier to deploy. We have about seven staff members on my team, IT analysts, who handle the solution, to account for different shifts and meal breaks, etc. Within the company there are 10 clients using it, mostly within IT. View full review »
Thamer Salah
Senior Presales Consultant at OFFTEC International
The initial setup was complex. The company itself and technology do not have a market share here in the region. Compared to other software or solutions which have most of the market share in the Middle East, it might be that people could use on the other software or other solution better. From the Commvault perspective, the way to install this solution is totally different than others. The mentality of how the solution should work is totally different than other competitors. In the Middle East, we don't have many technical people to work on it. The time it takes to deploy will depend from sector to sector. If it is an enterprise with more than 1,000 users it can take around three weeks. If it's mid-range like SAP accounts it could take one week. Taking into account the features that you want to enable will not take that much time. View full review »
reviewer1253568
Director of Technology Infrastructure at a healthcare company with 10,001+ employees
The initial setup was straightforward but that was primarily because of all the planning and a clear architecture design. We were able to run production backups in two weeks View full review »
Arunesh Rajendran
Sr. IT Administrator at a comms service provider with 201-500 employees
The initial setup is complex because we are going to set up a DR and cloud. There are different networks in our site as well. The deployment didn't take much time. Within a day to two days we had configured everything. But the test cases are taking time because right now we are working from home. We are connecting our systems remotely so there are some connection issues, due to our internet connectivity. View full review »
Mehmet Erdogan
Data Storage and Protection Team Leader at a tech services company with 201-500 employees
The initial setup of this solution is not complex, and it was not hard for me. The deployment takes between two and three hours. View full review »
KobusRas
Infrastructure Solutions Architect at a computer software company with 5,001-10,000 employees
It's not that easy to implement. It takes some time to implement and make it work. It was complex to implement and understand how to get everything correctly. View full review »
HamadaFarag
Technical Consultant at Beta Information Technology
For some customers we do the implementation on-premise, and others use the cloud version. It's very easy and straightforward. The design, implementation, and documentation is very straightforward, especially the Commvault hybrid product. The deployment time depends on the customer and it depends on the environment. It takes a minimum of two to three days, and the maximum is 10 days. It depends on the size of the environment. We have straightforward procedures for the implementation. We have a manual. We have procedures for the automation of installation for HA environments, whether it's for a virtual or physical, and for different operating systems. View full review »
ChiefSystemEngineer9
Chief System Engineer at a media company with 501-1,000 employees
I didn't install Commvault. It's not complex, but it demands optimization to do. An integrator did the implementation. It didn't look too complex, but there some things you need to take into consideration and there were configuration issues, fine-tuning, and things like that. The deployment took around two days. View full review »
JoaoLavrador
Pre-Sales at Arrow ECS Portugal
The initial setup is straightforward. We need one or two integrators to deploy and maintain this solution. View full review »
Learn what your peers think about Commvault. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
442,517 professionals have used our research since 2012.