I deployed it back on-site in 2007. The initial deployment was not complex. We didn't encounter any complexities for the data types we usually work with, such as data SAP and other data in our area. But, with new types of data, like net earnings or OpenStack, which are relatively new for us, there might be some challenges. But with documentation, we can do it.

I can't speak too much about the installation process. 

My understanding is that the installation is simple as it has an appliance that's installed. The usage is a bit complex and there needs to be extra licensing to customize the reporting - however, that's a different issue.  

It's straightforward. My team members were able to handle it independently.

We use an on-premises deployment.

The deployment of the appliance was pretty straightforward. It gets complex when we start integrating the appliance into the media server to increase the library and back up multiple operating systems. Our landscape is not small. The deployment can be simple or complex, depending on the phase we are in at a particular time. We cannot deploy the solution and walk away. The product evolves as the environment grows.

Last year, we swapped out some appliances that were at the end of life. Taking those out and bringing in other things was simple. Deploying libraries is complex. It's not a static space. It's a very dynamic space. Every year, we take a look at the environment and make changes. The number of people involved in the deployment varies. Sometimes, we need two, other times, more. We have about five people in our backup team.

I was involved in the migration from the old appliance to the new appliance which was straightforward. 

To migrate the data, we logged in remotely and opened the old console and the new console.

The initial setup process is straightforward. However, we encountered a few challenges while configuring security templates, such as two-factor authentication and certificate validation.

The solution’s initial setup is straightforward.

The initial deployment was straightforward. The installation takes two hours and after the installation, we have to create the policies for backup jobs and make schedules.

A professional services representative will assign an IP address to the backup server and open the port for the security team to connect the backup server to the clients.

The initial setup of Veritas NetBackup is not difficult. Veritas NetBackup's initial setup is easy because it is a mature solution.

The solution’s initial setup is easy.

I was involved in the deployment. The process was rather complex. You do need some skill to implement it. 

It took one year to really migrate to the new product.

You need to set up all your cabling and firewall ports and make sure that your solution is available for the infrastructure you want to backup and restore. Technically, you need to involve other people that you want to have file-level backups or database backups. You need to know what to back up and what you don't need to back up. You need to do some test backups and test restores to make sure that everything is available.

We had four people managing the implementation and we have two people now handling maintenance. 

The installation is not difficult. It's more about the recurrent operations, the command lines. The installation process itself is straightforward if you follow the steps and have a basic understanding of what you're doing. It's an easy-to-install product and also supports multiple platforms.

When you have multiple installations, you will need to set up the agents on the clients, but for product installation on the server, half an hour should be plenty to have the minimum preparation and to launch it. But to set up the environment, it wouldn’t be half an hour; it would take more time depending on what you are trying to back up.

NetBackup is not a user-based application, so I don’t have many deployments; it is just deployed at my agency. If we have been requested to update to a new server or upgrade the application, in which case I would have to update the clients as well, it might take longer to do that, but that can all be handled by one person.

The solution will require maintenance because you will have problems with the backups: there will be sensitive things that you need to monitor because you will have all kinds of issues, even if they are not related to NetBackup. It depends highly on the client. Maintenance here is about backups, not the application. The application maintenance itself would be the upgrades. Otherwise, it works well if there is no problem with any of the clients. When I say clients, I only mean the OS or the application where the solution is running that we want to back up.

The initial setup is pretty straightforward, but it's just very, very detailed. There's a lot of different things you have to do to set it up. It's not difficult. It's just a lot of steps, but that's how it should be because NetBackup is so flexible. You do have to go in and select your different options based on your environment.

It had been installed long before I joined.

If you use Veritas with Linux, the deployment is a bit more complex. Typically, we need a week to deploy the solution so that we have time to set up policies and so on. The setup can take anywhere from three days to a week.

We have two or three people that can be involved with the setup. However, typically, only one person is needed. 

If the policies are applied well and the backup is done automatically, there are fewer problems and maintenance. 

If we do the deployment once, the second time will be easier. The number of people required for deployment depends on the environment and its size. One person is enough to deploy the solution if there is no hardware to deploy. Our customers use the solution in multiple locations. Our latest customer has two main data centers and branch offices worldwide. The tool requires maintenance. If there are some bugs or errors that the administrator cannot resolve, we contact support.

NetBackup is too complex to set up. 

The initial setup is not straightforward. it's quite complex. The process required a lot of engineering and had lots of components that needed to be addressed.

I don't recall the amount of time it took to deploy the solution.

The solution does require maintenance, however, I don't know too much about the process. We're a quite large company. I don't know how many people are working on this solution in total. 

The initial setup process was not complex. We have gone through it multiple times and performed updates on several occasions, making the process straightforward. The deployment process for Veritas NetBackup is straightforward. It involves setting up a master server and a media server.

You can assign both roles to a single server or keep them separate. Additionally, clients, representing the machines for which backups are needed, require the installation of a client component. Ensuring open communication ports is crucial for successful backup operations. If the implementation engineer is skilled, they can handle the deployment process independently.

It's not difficult to maintain Veritas NetBackup. Maintenance mainly involves upgrades; as long as there are no issues, it runs smoothly day and night. Regular upgrades are the only maintenance requirement for the system.

The tool's deployment is straightforward and gets completed in months. 

I was involved with the implementation. We would have to devise retention policies and strategies for our backups. After we did that, we did a central setup and implementation. We also maintain the backups. If we ran into issues, we had a clear troubleshooting process. It was a bit complex. It would take us one to two days to deploy it. 

We had two or three people involved in the deployment process. One person manages the strategy, and another checks everything and goes on to perform maintenance. 

The initial setup is very easy. Commvault has a lot more convoluted setup. NetBackup is really easy to set up. I've never used Commvault, but from other colleagues I know who use it, you need professional services because it's so convoluted to set up. NetBackup is not that convoluted. Commvault is nice. It's a very nice application, don't get me wrong. I'm not going to put it down or anything like that. Once it's running, it's a good product. But from being exposed to Commvault a little, I like NetBackup better. I just think the downside to NetBackup is that it's not policy driven. That's the only thing I don't like about it.

The initial setup is pretty straightforward. It's not overly complex. We have a PC. We are familiar with everything as we have 10 years of experience using it. It's not an issue. A company shouldn't have too much trouble with the process either.

While I was not a part of the initial setup, I understand that it is fairly simple. 

I was involved in the product version upgrade. We were able to finish it and begin using the built-in appliance.

We completed the implementation in three weeks and have been using the appliances on a daily basis since then.

It is currently managed by a team of three people.

Veritas is a pretty straightforward initial setup. It's not difficult to install.

The deployment times vary depending upon how widely it's going to be used, how many backup instances are going to be, how many policies you have to create for recovery time objectives, recovery point objectives. It's all relative to how many policies the customers have, for retention cycles, for backup recovery, as well as archive and disaster recovery. Some can be deployed in a day, others take weeks.

Its initial setup was straightforward.

The initial installation is more complex than that of Commvault.

The initial setup is quite straightforward. The solution itself is very user friendly, so we didn't find the implementation very complex.

Deployment took about half a day of work.

The initial setup was straightforward. You will not find much difficulty in setting up clients.

The initial installation is quite straightforward. Overall, installation takes roughly one hour.

The initial setup was very straightforward and took about 15 minutes. We had help from the vendor. There isn't much maintenance required, only if there's an issue with something. We are  small company, so it's not a problem - we do backups of the servers and almost everything that we have on our infrastructure. When we carry out the backup for the exchange server, we do backups for everyone in the company, so it's not just one specific user or a couple of users. There are three admins in the company. 

The implementation of Veritas NetBackup is very difficult because we have two types of data storage, one is a regular disk and the other is a tape drive. We are using both. Installing each and every service on the servers, licensing for each in the servers, certifications, and connecting takes a long time.

It took us almost two months to fully implement Veritas NetBackup.

Its installation is quite straightforward. The deployment can take a week if you have a clear backup requirement.

The initial setup of Veritas NetBackup is straightforward and not complex. We have been using it for a long time and are very comfortable on the platform. A small setup can be done in 30 minutes. Then it is just a matter of deployment and mastering the solution.

The setup was completed before I joined the company.

While we've encountered occasional minor issues, overall, the deployment has been relatively straightforward.

The initial setup is very easy and there's no similar service. 

The initial setup of this solution was straightforward, with no complexity.

Veritas NetBackup is easy to install and I would rate it a seven out of ten. 

The complexity of the deployment depends on the data we are protecting. It's a bit complicated if we're working with databases, but it's simple to back up a file system. We can do everything ourselves, but we open a case with Veritas if we have a problem. Two full-time IT employees are enough to deploy, maintain, and manage NetBackup. 

The implementation is simple.

In my experience, the Veritas NetBackup installation is hard. However, when it is running in operation, it works with no issues or problems. There are some challenges here in Chile and the whole implementation process can take 60 to 75 days.

The complexity of the initial setup largely depends on the client's infrastructure. If they want to protect VMware workloads, then it's quite straightforward because we just integrate it directly with their workloads. In this case, the implementation is simple.

However, if we are required to protect SAP HANA or some Oracle cluster, for instance, that requires a lot more work. It's much more complicated because it's not based on a user interface, and we need to have a high level of perspective and understanding. So, ultimately, it depends on what needs to be protected.

Installing Veritas is okay and I find it easy. It can be deployed by one engineer.

Deploying Veritas will take longer than other products, such as Veeam. The length of time it takes depends on how big the environment is, and how many servers there are.

The initial setup is straightforward.

The initial setup and deployment can be done in one day and one night.

The setup was straightforward, it is easy to configure and user-friendly to administer.

Deployment was fine, though there is an issue with seeing skills certificates.

The initial setup is simple, it doesn't take a lot of time. It's less than 30 minutes to set up if you have the cloud.

The initial setup was very straightforward and quick. We used a consultant for the initial implementation and for minor upgrades or minor changes, our internal team is responsible. If it's something major, our partner deals with it.  

Easy in terms of setting up the three tier NetBackup domain. Challenges were encountered though while setting up other aspects like network, resiliency, firewalls, etc.

I've implemented several NetBackup installations and all of them run smoothly. However, if you are going to implement it for the first time, I really recommend you run some tests before doing so.

The initial setup for Veritas NetBackup wasn't straightforward, but because I had some experience setting it up, it was fine. Because I knew what to do in terms of the initial setup of this product, that helped me a lot.

The initial setup is pretty straightforward.

The deployment is fats. It took us about three to four hours to do a basic installation with our client.

We have 25 to 30 admins that can handle maintenance and deployment within our organization. 

It is very easy and straightforward to set up. The length of time required for deployment depends on the implementation and the number of servers. I would say that the average is between three and four days.

The initial setup was very easy. It has a lot of "next, next, next," and basic functions that just work. Setting up advanced features can be complex, but the documentation is readily available. If you read and follow the steps in the documentation, you will be fine.

The initial setup seemed straightforward. It took maybe a couple of hours. 

While the initial setup is not complex, and, in fact, pretty straightforward, the planning is not that easy. The planning needs a lot of time. It often takes days just for that one part.

Veritas should come up with some sort of a standardized checklist that everyone can use to simplify the implementation process.

Typically, for a deployment, you need one or two people. That's the maximum to do the deployment, in theory, however, it depends on the environment. If it's a very large or complex one, we will need more. Most of the time it's one to two persons for deployment and maintenance.

Deployment was completed in less than a week. We used a third party and they were quite good. They took us through the installation, the configuration, and they trained me as well.

It's pretty straightforward for a simple configuration but much more complex for a large environment, with many features and tuning required.

It's somewhat complex. It wasn't very easy but it's fixable. It takes about one or two hours to deploy.

We run into issues now and again, but essentially the initial setup is pretty straightforward.

The team who was working on the initial setup was well aware of what they needed to do, so it was straightforward.

We have two people who do the maintenance.

The initial setup is very simple.

The installation of the software for one who is familiar with the process takes around an hour. Otherwise, it can take two to three hours to complete the setup. 

Setting up NetBackup is easy, but the documentation is a bit complex. Veritas used to have consolidated documentation, so it was easy to navigate the documents. The implementation guidelines were contained in a single document, so you didn't need to switch between multiple documents. Configuration should be the clearest documentation.

The initial setup isn't complex; I would say that it's moderately easy to implement this solution. We need to have some machines. It's a resource-centric server. If we're using it for enterprises, we need some dedicated physical servers to install this, like master and media servers. It's not very simple, but it's not very complex. I found it in-between.

The setup was complex, considering that we have never worked on an Unix-based OS before.

The initial setup was complex.

Its initial setup is not very complex. It took us one or two months to deploy it. We have a team of five IT people for deployment.

The product is easy to set up in small environments, but it would be more complex in larger ones.

I have been involved in upgrades. They have not been straightforward. Some of them have required us to make changes to our architecture and production environment.

I don't have any information regarding the installation.

The installation requires some knowledge, but the procedure is easy and there is a lot of clear detailed documentation you can follow available.

The installation time can vary depending on the size of the environment. On average it can take between five to seven days.

Based on my experience of using enterprise-grade backup solutions for a long time, easy management and deployment generally don't happen for enterprises. You generally can't scale an enterprise-grade solution. You usually combine different solutions. 

When we create a full solution, there is some complexity in installation management. In the end, we are able to get features, such as easy management and combined centralized management, with Veritas.

In my opinion, I would say the initial setup is a complex process.

We require a specialized team to maintain this solution.

Unfortunately, I don't implement the solution. I just evaluate different products, including this one, for my clients. Since I'm not involved in the process, I wouldn't be able to evaluate how difficult or straightforward it is to accomplish.

The initial setup is not complex. We implement from the Veritas site and we use the knowledge base.

It can take several months to implement this solution. We had to prepare the architecture, the guides, and documentation for several data centers. It was not a fast implementation.

I personally have a lot of experience with this product, but someone without a whole lot of knowledge about it would have to partner up with a vendor. I would say overall deployment is at a medium level of difficulty. 

Setup of FC (Fiber) backup is complex.

I did not handle the initial setup. Therefore, I cannot speak to how easy or difficult the setup process is, or how long the deployment takes 

The setup, installation, and configuration is not complex. Once the product is configured, it is very easy to use.

Complex, as was unsure how the product worked at the beginning. But after several months of using, became very simple to use as everything is within the single agent install and understood what was required.

I am familiar with the installation and it is simple.

Straightforward, both on Solaris, Linux, and windows servers. Easy client installation (local or remote)

The initial setup is easy. Deployment is quick, but some systems can have issues.

The initial setup varies from customer to customer. Most setups are straightforward, but they tend to be complex over time, due to adding DR sites, alternative media, and tuning backup times.

The initial setup of Veritas NetBackup could be easier.

The initial setup was complex. The networking was very complex; there are a lot of firewall ports.

It takes a few days to deploy and we do it with somebody in-house. 

Both our side and the vendor's side are required for maintenance.