NetBackup 10.1 - New PaaS Workload Protection
Starting with NetBackup 10, Veritas began expanding the support for PaaS workloads. In NetBackup 10.1, Veritas built an extensive framework designed to promote accelerated adoption of PaaS workloads protection. As a testament to that framework, NetBackup 10.1 adds support for the following 13 new PaaS workloads: Azure Workloads AWS Workloads GCP Workloads Azure PostgreSQL Amazon RDS Postgres Google MySQL Azure MySQL Amazon RDS MySQL Google PostgreSQL Azure Managed SQL Amazon RDS MariaDB Azure SQL Amazon Aurora SQL Azure MariaDB Amazon Aurora PostgreSQL Amazon DynamoDB The process of protecting and recovering PaaS workloads is easy and streamlined via NetBackup Web UI. NetBackup Snapshot Manager needs to be configured to facilitate the discovery of the supported PaaS workloads. Media Server with MSDP Universal Share configuration is also a requirement. After NetBackup Snapshot Manager and cloud provider credentials are configured, discovery process will be triggered automatically or can be started manually. Once the discovery runs successfully, supported workloads will be populated on the Web UI PaaS tab: Add PaaS credentials as required for the workloads to be protected. Credentials can be created previously and leveraged later for the workload to be protected or created as new during configuration. On this example, credential is being created previously using Credential Management tab: Add the credential to the PaaS workloads to be protected. Please note the “validation host” is the Media Server hostname that will be utilized to communicate with the cloud provider and PaaS workload. Media Server need to be able to resolve PaaS services to validate credentials: After that, it is just a matter of creating Protection Plan as usual. The following two prompts are specific to PaaS workloads: 1-) Protection Plan is for Cloud, same as the one used to protect virtual machines in the Cloud, for example. Check “Protect PaaS assets only” to be able to call the correct workflow and framework for PaaS: 2-) On step 4 (Backup options), storage path is the previously configured Universal Share mount point: Just complete Protection Plan workflow and that’s it! Protection Plan will run according to the schedule configuration and recoveries will be fully managed by NetBackup Web UI as well. Veritas NetBackup 10.1 now makes it easier to protect PaaS workloads, with a streamlined process guided by Web UI and leveraging benefits of NetBackup deduplication service (MSDP) and RBAC (role-base access control) to empower workload owners and administrators as needed. Here are some good references for more information about PaaS Workload protection with NetBackup 10.1: NetBackup 10.1 Web UI Cloud Administrator's Guide - Protecting PaaS objects NetBackup 10.1 Web UI Cloud Administrator's Guide - Recovering PaaS assets
Cloud Scale with NetBackup 10 and Amazon Web Services
Veritas delivers high-performance data management solutions that drive agility, efficiency, and cost savings for AWS workloads. See how NetBackup 10, powered by Veritas Cloud Scale Technology, is the industry's first cloud-optimized, at-scale data protection solution that delivers a more cost-effective, secure, and sustainable cloud with automated, elastic operations.Virtual Workload Migration to AWS Planning and Execution using APTARE and NetBackup Resiliency
Veritas solutions help you visualize your environment to successfully move to the cloud. Learn from the experts as they demonstrate how to achieve significant savings with a virtual workload migration to AWS.Mind the Gap: How to Solve the Data Protection Problem from Edge to Core to Multicloud
In the age of remote work and more IT infrastructure options than ever before, it is easy to create data management gaps in your IT strategy. Learn about how to automate, protect and recover your cloud native infrastructure across AWS, Azure, GCP and more. Learn how to maximize snapshot orchestrated recovery capabilities across your IaaS deployments including with a live demo running in a truly hybrid environment. Your data has never been more versatile than it is in the Veritas Enterprise Data Services Platform.
How important is it to verify the replication of (already verified) disk-based backup sets to cloud?
My company is a little bit behind on the adoption of cloud technology; there hasn't been a compelling need to change anything. Anyway, I was hoping to at least modify my disk-to-disk-to-tape backup scheme to a disk-to-disk-to-cloud one. Having to change tapes is a pain, especially now since I have to make a special trip into the office to do it. There's no way to "budget" anything until I have some sense of how much this would all cost. Amazon has cost calculators, but they ask for metrics I have no way of getting at. So as a test, I created an AWS S3 bucket and did some test Duplicate jobs from existing backup sets to the bucket. The first ~15.5 GB backup set cost $1.59 to duplicate to 1Z-IA. So a full 3 TB backup would scale up to approximately $320 every week. Plus, with a 4-week retention period, 12 TB of data storage would be another $120/mo. That would be a nonstarter with management. Then I dug into the Amazon Cost Explorer and found that most of this ($1.38) was Data Transfer out. The cost appeared because the duplicate job did a Verify, and to do that, the Backup Exec server had to read all that data back in from AWS. I verify the duplicate to tape because there's no cost to that. If I skip the Verify, the weekly cost for AWS backups would drop a lot. A subsequent 70 GB Duplicate, without the verify, cost about 25 cents. What would I lose if I skipped the verify? The backups to local disk would still be verified as part of the job that creates them. There's some error correction built into Ethernet, would that remove the need? Getting rid of tapes, I could restructure the backups to do incremental forever, so I wouldn't need to keep 4 full backups in local storage or in the cloud. But I'd like to first estimate costs using the closest structure to existing practice.
