Backup Host SSL issue in Flex Appliance
Hi Folks, We got a Flex Appliance in which we set up 1 Primary and 1 Media, as want to back up some Nutanix VMs through the Cluster. We decided to go with the MediaServer instance as our backup host. The issue is when trying to add the Nutanix Cluster through the NBU Web UI, below the displayed error : "Credential validation failed. Provide correct AHV credentials, ensure that the backup host has Linux/Windows OS, verify that the backup host can access the AHV cluster, or the external CA is configured correctly." After some troubleshooting, we found the "nb_nutanix-ahv.conf" in the Media instance with the parameter "enable_ssl_validations" which is enabled by default. When disabling it, the Cluster is added successfully. Enabling it back, the integration of the Cluster failed again. So, we confirmed that the issue is related to SSL certificate. We tried to set the SSL communication following the NBU documentation, but it did not work, maybe we missed something (Below doc link) : https://www.veritas.com/support/en_US/doc/150073865-163074231-0/v147708883-163074231 Any idea how to fix this SSL issue with Nutanix ? Flex v 5.0 and NBU v 10.5. Regards.
Check out the new capabilities in the NetBackup Flex Appliance 3.0 Release
NetBackup Flex Appliance 3.0 Software was released in December 2022. Check out these two blogs for more details. What's New With Veritas NetBackup Flex Appliance 3.0 by Rachelxhu https://vox.veritas.com/t5/Protection/What-s-New-with-Veritas-NetBackup-Flex-Appliance-3-0/ba-p/898501 Neutralize threat of cyber-attacks with NetBackup Flex Appliances by Sid_Doeker https://vox.veritas.com/t5/Protection/Neutralize-threat-of-cyber-attacks-with-NetBackup-Flex/ba-p/898643
Flex Appliance 5250 LAN/SAN cards upgrade
Hello, Please your help with this scenario, we have a Flex Appliance 5250 B type, and we need to upgrade a D type for FTMS support, the upgrade cards SKU's are defined and the installation cards are supported by the Veritas Appliances Team, BUT we don´t know if, as part of procedure, we need to execute an appliance factory reset or the installation is transparent, only install the cards in the respective slots and reboot de appliance. Thank you and waiting your comments. RegardsvSphere vmware plugin installation from primary on FlexHA
Hello, i'm trying to install the vSphere plugin from a NBU 10.0.0.1 primary server on a 5250Flex but in can't in anyway start the vwcp_manage command. It always notifies me about missing packages (for example librender1). How can i solve this? I've looked for a specific guide but i've found nothing. Thank you!The Veritas Flex Appliance and the Game of Leapfrog
It’s my firm belief that we don’t see much that is actually “new” in IT very often. Mostly what we see is either the clever application of existing technologies or the re-application of pre-existing technologies with the understanding that the tradeoffs are different. I include server virtualization and containerization in the “not new” category with both actually being quite old in terms of invention, but in more recent history, containers having more interesting applications. The reason I’m going down this path is I frequently get questions regarding the Flex appliance as to why we chose to implement with a containerized architecture instead of using a hypervisor for an HCI data protection appliance like [insert company name here]? And, are your sure there’s no hypervisor? Yes, I’m sure there’s no hypervisor in Flex, it uses containers. Fundamentally there are good applications for both, and for entirely different types of workloads, so let’s look at why chose containers for the Flex Appliance instead of a hypervisor. Containers has its roots in FreeBSD “jails”. Jails enabled FreeBSD clusters to be hardened and for deploying of “microservices” (to use a more modern turn of phrase) onto the systems. The big advantage here being very high levels of isolation for the microservices, each running in its own jail. Containers then versus now are fairly different. FreeBSD jails were relatively primitive compared to something like Docker, but for their time they were state of the art, and they worked quite well. Which brings us to hypervisors. VMware started largely in test/dev. About the time it was entering into production environments, we were also seeing significant uptake of widely adopted 64-bit x86 processors. Most applications were running on a single box and were 32-bit, single-threaded, single-core, and didn’t need more than 4GB of RAM. Rapidly, the default server was 4 cores and had 8GB of RAM, and those numbers were increasing quickly. The hypervisor improved the extremely poor utilization rates for many sets of applications. Today, most new applications are multi-core, multi-threaded, and RAM hungry, by design. 16-32 cores per box is normal as-is is 128+ GB of RAM, and modern applications can suck that all up effortlessly, making hypervisors less useful. Since 2004 Google has adopted running containers at scale. In fact, they were the ones who contributed back “cgroups”, a key foundational part of Linux containers and hence Docker. This is interesting because: Google values performance over convenience Google was writing multi-core, multi-threaded, “massive” apps sooner than others Google’s apps required relatively large memory footprints before others Googles infrastructure requires application fault isolation So, although virtualization existed, Google chose a lighter weight route more in line with their philosophical approach and bleeding edge needs. Essentially “leapfrogging” virtualization. Here we are today, with the Veritas Flex Appliance and containers. Containers allow us to deliver an HCI platform with “multi-application containerization” on top of “lightweight virtualization” - essentially leapfrogging HCI appliances built on a hypervisor for virtualization. A comprehensive comparison of virtualization vs. containers is beyond the scope of this blog, but I thought I would briefly touch on some differences that I think are key and that help to highlight why containers are probably the best fit for modern, hyper-converged appliances: Virtualization Containers Operating system isolation (run different kernels) Application isolation (same OS kernel) Requires emulated or “virtual hardware” and associated “PV drivers” inside guest OS Uses host’s hardware resources and drivers (in the shared kernel) Standardized “packaging” of virtual machine (mostly; variance between hypervisors) Standardized packaging requiring Docker or one of the other container technologies Optimized for groups of heterogeneous operating systems Optimized for homogeneous operating system clusters Here’s another way to look at it: Enterprise Cloud Hardware Custom/Proprietary Commodity HA Type Hardware Software SLAs Five 9s Always on Scaling Vertical Horizontal Software Decentralized Distributed Consumption Model Shared Service Self Service What you see here is a fundamentally different approach to solving what might be considered a similar problem. In a world with lots of different 32-bit operating systems running on 64-bit hardware, virtualization is a fantastic solution. In a hyper-converged appliance environment that is homogeneous and running a relatively standardized 64-bit operating systems (Linux) with 64-bit applications, only containers will do. The application services in the hyper-converged Flex Appliance are deployed, added or changed in a self-service consumption model. They’re isolated from a potential bad actor. The containers and their software services are redundant and highly available. Application services scale horizontally, on demand. One of the best party tricks of the Flex Appliance that I didn’t touch on above is that containers fundamentally change how data protection services are delivered and updated. With the Flex Appliance, gone are the days of lengthy and risky software updates and patches. Instead, quickly and safely deploy the last version in its own container in the same appliance. Put the service into production immediately or simultaneously run old and new versions until you’re satisfied with its functionality. We couldn’t do any of this with a hypervisor. And, this is why the Flex Appliance has leapfrogged other hyper-converged data protection appliances. I also refer you to this brief blog by Roger Stein for another view on Flex.
