The primary use cases are direct appliances. We have held clients using it in some public companies. So, when you have several installations, the most commonly used appliance is BYO. We build and install the software on servers with storage attached to the router through the SAN. We configure all the software needed for the backup to cooperate as a backup-to-disk storage server with duplication.
I connect these Veritas NetBackup Appliance because they are highly stable and stronger. Therefore, we don't require so much maintenance to use these appliances. The integration of these appliances requires some maintenance, but they are known for their strength and stability.
The deployment of the physical appliance in case of a disaster is not smart. When they need to restore clients without adhering to factory default settings, they lose data. The recovery of this appliance is not easy. This applies to both the software-based and MSDP storage. It is not easy because I have worked a lot on the tool, and in case it gets corrupted at any point, it is not easy to restore the data without losing information is not easy.
Adding additional features to the configuration of Veritas NetBackup Appliance is essential. For instance, storing metadata in a safe place is crucial for restoring the configuration. If we need to restore the same appliance with its same configuration, we can avoid manual insertion or retrieving data from files. Another noteworthy feature involves uploading a configuration file, allowing the system to process and rebuild the storage accordingly.
I have been using Veritas NetBackup Appliance for ten years.
I have no stability issues to report.
I rate the solution's stability an eight out of ten.
I rate the solution's scalability an eight out of ten.
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.
On a scale of one to ten, where one is a high price, and ten is a low price, I rate the solution's pricing an eight.
Since my company has a good partnership and a global contract, we can resell licenses at a good discount. We can provide good pricing. Additionally, customers can benefit from discounted reselling directly from the vendor.
Overall, I rate the solution between eight out of ten.