Understand, Plan and Rehearse Ransomware Resilience series - Access and Improve
Ransomware uses stolen credentials to gain access to backup systems and then delete, encrypt or expire the backup data. For more details on how to enable these features, here are the ten steps to increase your security posture.Neutralize threat of cyber-attacks with NetBackup Flex Appliances
89% of all organizations have fallen victim to a successful ransomware attack resulting in unrecoverable data events. See how to significantly reduce the risk of a cyber--attack and recover confidently with an air-gapped turn-key appliance.
IDC Technology Spotlight on the Importance and Value of the Flex Appliance
Access the full IDC Technology Spotlight here: Simplifying Data Protection with Next-Generation Converged Infrastructure. KEY TAKEAWAYS Flex Appliance may be the most important product announcement by Veritas since the company split from Symantec some years ago. Flex Appliance is a new architecture designed specifically for modern data protection workloads. It also offers an important bridge back to NetBackup environments that should provide this large group of users a logical and simple path forward. Veritas is among the first major vendors to move into this rapidly emerging and growing product category. It does so with the clear advantage of a large, receptive installed base and with credibility built on its successful NetBackup appliance. Flex Appliance's microservices architecture is also built to address the diverse data protection and management needs of specific business units and applications. Thus, as a single system, it can simultaneously provide consolidated data protection operations with the ability to deliver microservices on a best-in-class basis for specific workloads. We believe that Flex Appliance may be the key to Veritas retaining its market-leading position in the data protection and recovery market. More on the Flex Appliance here: Veritas Flex ApplianceVeritas Appliances receive ENERGY STAR certification
Combining Corporate Responsibility with innovative data management solutions, the Veritas Manufacturing and Supply Chain team worked closely with the U.S. Environmental Protection Agency (EPA) and partners to attain ENERGY STAR certification for NetBackup 5340, Access 3340, and Flex 5340 appliances.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.Veritas Appliances Inspire at Microsoft Partner Event
Just recently back from Las Vegas and an inspiring week meeting with numerous Microsoft and Veritas partners and forging new business partnership relationships for Veritas' data protection and Long-Term Data Retention Appliances. Some of the conversations I had here started with question on how Veritas hardware-based solutions align with Microsoft’s offerings, particularly Azure, and as an MS partner, how does it benefit my customers’? Interestingly enough, Microsoft has apparently started their own hardware division. I’d speculate it’s a consolidation of resources to develop hardware to power their Azure services. Back to the question at hand on Veritas Appliances. The answer is really pretty simple the Veritas family of data protection and LTR solutions all seamlessly integrate with Azure, protecting an organizations most critical assets on premises and in the cloud. Rather than spilling more ink on the value of Veritas Appliances here in the VOXosphere, you can watch my Wikibon TheCube interview on this topic and more. Then and come back to VOX to continue the conversation.
FLEX Appliance - Changing the SSH/WebConsole IP Address
Hi all, Had to start playing around with these little Nbu Docker/Container mutants, with their all new CLISH-ish shell. Managed to get the Web Console, a tenant and a Master Server instance running no problem. We're now trying to change the port-host0 management IP (basically the SSH/WebConsole IP) but found that the Web Console does not allow you to change it (you can only change tenant network, bonds, IPs in the Web Console). Basically port-host0 is missing in the Web Console, and the FLEX shell is missing build-in commands to change this IP also. FYI, you get to configure this IP when you first initialize the FLEX Appliance by running "setup configure-network". But after that there doesn't seem to be an easy way to change this IP. Please let me know I'm just overlooking a page or two in the guides. I'm starting to think the only way to do this is to sudo root powers and just use native linux commands, but I'd rather there is a "FLEX-supported" way. Thanks!
