The initial setup is neither simple nor complicated. When you define backup policies for multiple environments in the same organization, such as a DC-DR environment with various DNS servers, the policy can be complex if you require multiple levels of backups.

The initial setup was relatively easy for me since I took the time to learn about the tasks involved. Even when issues arose, I often resolved them without needing support, thanks to the new tools provided.

The initial setup is straightforward and simple.

The product's deployment was easy. 

We have deployed the product on-premises. The cloud solution is more flexible and provides more stability.

The initial setup is quite simple. We need to input some information. Suppose you make changes to the configuration throughout the year. What is complicated is keeping track of these condition changes. In case of a disaster, it is also important to restore this information. If I needed to recreate the entire setup because all the information is stored in the appliance, it would also involve saving some information in the math. However, it is generally not recommended to save information externally if the object is not integrated into the appliance.

This kind of approach is not considered best practice. But if you need to review the plans, you have to input the same information that the master server expects in order to speed up the service coverage. Otherwise, you will need to repeat from scratch. I can provide you with the name of the business server if you require it.

Yes, I can save some information from the master server, but the issue is that you cannot deploy it in the appliance if it's a storage server. It cannot be deployed directly from the master server. Instead, you would have to redeploy it in case of a disaster. The same appliance needs to be set up again with the same name, information, and configuration since deploying this information cannot be done from the master server. You can deploy it from the virtual appliance or from the configuration management or the plans.

We deploy on-premise but with integration with the cloud to protect data.

The installation and configuration of the solution is easy.

So, every year there is something new.

If you already have backup targets, appliances, or other servers or storage, the first environment will be deployed within a few hours from the beginning. There are only two engineers required to deploy.

We also have maintenance services from Veritas. It works very well.

I did find the Veeam setup easier. 

It took us a day to deploy the product. It did not take long. 

I'd rate the ease of setup at a three out of five due to some general complexity. 

It's a new appliance. Right now, it is working fine. We don't really need to worry about maintenance. 

The initial setup was very simple and easy. I rate the ease of setup a ten out of ten. The appliance is on-premise. We can also utilize any hyperscalers for cloud storage and backup. The time taken for deployment varies depending on the client’s requirements. On average, the deployment can be done within a day. We need one engineer to deploy the product.

Setting up NetBackup is straightforward, but we sometimes get some weird errors while we are trying to configure it. There are so many processes to deal with because all of these products are legacy backup tools. They are a little more complicated than next-generation backup tools like Rubrik or some of the newer ones on the market. It doesn't require many users for maintenance. 

It is quite easy. It is not super easy. We have a lot of different environments. Some of them are quite challenging, but the common environment is quite easy.

The initial setup is okay. It is not very difficult. While the planning stage requires the use of much Veritas material, it's easy. This is because we are talking about an appliance which has everything predefined or preconfigured.

The deployment took a long time. I believe that the process lasted a month-and-a-half. This is because it required us to do many validations, as we were replacing our solution.

Veritas NetBackup Appliance's initial setup is simple. The full implementation took approximately one day.

NetBackup software is embedded into the appliance, so I do not need to worry about installation. The initial setup is very easy.

We have a team that handles the setup and management of the solution. I didn't handle the setup myself. I couldn't say, from experience, if it was difficult or not, however, I don't recall the team running into issues or requiring outside assistance.

With NetBackup, just setting it out to different server times and nothing else is okay. Other things are a bit more complicated.

That said, it’s been eight years since I’ve done a live deployment. We got the appliance and had to set everything up.

The initial setup is straightforward.

It's my understanding that the initial setup is straightforward. I have not seen anything about the solution that would make the process overly complex.

The integration was easy.

The initial setup was easy. The only problem that we had occasionally was, when we installed the software, we had to store a big amount of data to disk, because the package included all the operating systems and sometimes the space on the filesystem was not enough. We needed about one and a half gigabyte to install the software.

Veritas NetBackup Appliance's deployment is easy for me. However, it will be difficult for beginners. The tool's deployment takes one week to complete. 

The initial setup was straightforward.

The initial setup was simple. It was straightforward and there weren't too many complications. In terms of maintenance, one person is always managing the backup infrastructure. It's the operation team data center operator who monitors the backup during the night shift.

The initial setup was easy, and it took a couple of days to onboard all my private cloud work resources that needed to be backed up. 

The steps to deploy Veritas NetBackup Appliance need to be made simpler.

The initial setup is very easy, it took around two hours. We used a Veritas consultant. We deal with the maintenance ourselves.

The initial setup was straightforward. I found it very quick and easy. For maintenance, we just need two people.

The setup was not complex, it was straightforward. We had a delivery team very specialized in it, so it was not at all difficult. 

The deployment took about two to three weeks from the shipment of the hardware to the release of the solution in the production system. We are currently phasing another project stream in September. We were supposed to plan two weeks of activity to set up and configure the solution. I am currently the project manager of the project.

The initial setup was straightforward. 

Installing this solution is very simple and takes perhaps five or ten minutes. It takes a little longer to purchase the license and register the product.

The initial setup wasn't complex. It was pretty straightforward. 

First of all, we have done it already a couple of times. That helps. You get used to it. Also, in one of our latest projects, we received assistance as well, from Veritas NetBackup. They were on hand to configure it correctly.

If you know what you're doing, it's a very easy initial setup. First-timers always find it difficult. That said, if you're using a GUI, it's very straightforward. You can just photo screen. However, if you're an experienced user, you'ld probably prefer to do it on the command line, for which you need to know what you're doing. 

The initial setup of this solution is not simple. It is complex, and you really need a professional technician to assist. In the end, however, you have a really stable solution.

The deployment took place over time, where we have been improving things over the years.

We have perhaps twenty administrators and operators who manage this solution. It is not used by the end-users.

The initial setup was quite straightforward. We use a Linux based backup, and we chose the solution because we are using Veritas appliances as well; it was recommended by Veritas.

It's quite easy for someone who is experienced with backup administration. It might not be as easy for someone implementing for the first time, but for someone who is already experienced, it's very easy.

There is only one server you have to prepare. The configuration is very easy and the integration with VMware was a piece of cake. It's not a complex ATI that you need to strip down, connect, stream, send, etc. It's very, very easy.

Thre are initially only four or five policies that NetBackup uses with Microsoft Windows, SQL, Oracle, VMware and Check Point. That means that you don't have to deploy agents everywhere.

When it comes to the initial setup, this solution is not as easy as others when you are implementing it for the first time. You need to have experience with solutions such as Oracle, Linux, Exchange Server and the Malware Agent, otherwise, you will not be able to implement this solution at all.

This solution is easier to implement and configure than the software versions of NetBackup. You need to connect the channels, and then install the agents on your operating systems.

The initial setup of this solution is very difficult because we have a complex environment. With more than one thousand systems, the migration of the systems is not easy.

The installation is easy and took approximately one week.

The setup of Veritas NetBackup Appliance could be made easier.

I was not involved in the initial setup.

Our system engineers maintain this solution.