Welcome to the Veritas Flex Appliance
The Veritas Flex Appliance is a new concept in delivering enterprise data protection services. It utilizes a modern, containerized architecture to deliver a range of on-demand services including data protection and tiering to public and private clouds. Flex simplifies IT by replacing multiple, dedicated departmental servers with a single, microservices based data protection appliance. With Flex, multiple NetBackup and NetBackup CloudCatalyst microservices are configured and deployed in less than 5 minutes, and on-demand. And, Multiple NetBackup deployments (domains) can be consolidated on a single Flex appliance substantially reducing data center cost and complexity. The Flex Appliance represents a paradigm shift in high availability and SW updates. It’s not only a fully redundant hardware appliance, it’s also H/A in its and containers/services. With Flex, new versions of services are deployed in independent containers making SW patches and updates a thing of the past. Interested in learning more about Flex? Join our Veritas Appliances community and interact with the Engineering and Product Management team that developed this new architecture. Helpful Resources: Flex Appliance Webpage Flex Appliance Data Sheet Flex Appliance Solution BriefBreaking News! Veritas Doubles Appliance Offerings
Its big news! Since March we’ve double our appliances portfolio, launched our first storage system the Access 3340 Appliance, and the Flex Appliance, our first containerized data protection solution. The Access Appliance is a purpose-built storage solution for long term retention of backup and, archive data and other retention-type use cases such as video surveillance and healthcare PACs image data. Not surprisingly, The Access Appliance is built on our popular Veritas Accessscale-out NAS software. The Flex Appliance is a very clever platform for delivering Veritas data protection services including NetBackupand CloudCatalyst. Rather than running these appson dedicated servers, with the Flex Appliance, multiple data protection services are deployed in containers on a single appliance. Turn on a data protection or cloud tiering service as needed, without touching additional hardware. The containerized, microservices architecture of the Flex Appliance even goes a lot further than hyperconverged when it comes to simplifying infrastructure and the speed and ease of deployment as it supports multiple NBU domains and CloudCatalyst instances simultaneously. I can guess what you’re thinking. Why is Veritas offering more and more appliances when everything Veritas has been software defined? The primary reason; many of you in the community have asked us to. Particularly for Access. There’s a unique aspect to our appliances. A secret I'll share with my readers. Shhhhh. They’re still software defined. The software license is decoupled from the hardware we deliver it on. Here’s a couple examples of what I mean. Let’s say you purchase an Access 3340 Appliance, and a year from now you find a shiny, new storage server. You can move the Access software license to that new hardware. It also works the other way around. Maybe you’re running NBU software today on a white box server but want to upgrade to the Flex Appliance. No problem. That license you already have can be used to enable NBU on Flex (assuming minimum supported version, of course). Veritas appliances are really the best of both worlds. All the benefits of a software-based solution with the peace of mind that you’re not locked into Veritas hardware. I’m thinking we should have called them un-appliances. What do you think? Please add your thoughts and comments to the discussion.
UPGRADE NOTE: 3.0 -> 3.1 5230 media server
Just an FYI - I upgraded my non-prod media server this morning, and upon the final reboot, the system came up but *none* of the media mgmt services started: NB Processes ------------ root 98265 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/private/nbatd -c /usr/openv/var/global/vxss/eab/data root 98433 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/vnetd -proxy inbound_proxy -number 0 root 98434 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/vnetd -proxy outbound_proxy -number 0 root 98435 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/vnetd -proxy http_tunnel -number 0 root 98552 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/vnetd -standalone root 98578 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone root 98683 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/nbdisco root 98979 1 0 12:58 ? 00:00:00 /usr/openv/pdde/pdcr/bin/spad root 99237 1 14 12:58 ? 00:04:50 /usr/openv/pdde/pdcr/bin/spoold MM Processes ------------ Shared Veritas Processes ------------------------- root 64397 1 0 12:56 ? 00:00:00 /opt/VRTSpbx/bin/pbx_exchange I ran "netbackup start" from the init dir and everything came up then... but not on reboot. Just an FYI.
