Configuring Amazon S3 in China (Blog)
(This isn't a question, just documentation of how we fixed an issue I couldn't find an answer to online. I have no doubt all of this is in the Cloud Admin Guide, I just decided to take the long route and skip that part :manembarrassed: ) My company has a handfulof remoteofficesaround the world, with two of themin different sitesin China.In each of those China offices we run a 7.7.3NetBackup Master Server, (Windows 2008), to back up local data to disk, and use SLP to replicate those images across the WAN to the other office for offsite protection. This has been working successfully for 3 years, but we've slowly been adding more data to these offices and can no longer do local backups ANDcrosssite replication without filling up the disk targets. We're using "borrowed storage"from another server to protect our offsite copies at the moment while we decide where to go next. One of our new initiativetests was to replicate to S3, but AmazonAWS has a separateChina environment different from the amazonaws.com that the rest of the world can access, amazonaws.com.cn. Our Cloud Admin set up a new S3 instance in China without an issue, but the problem is the default Amazon cloud instance in NetBackup 7.7.3 is not customizable, and does not include the China Amazon region. The problem is the cloudprovider.xml file (C:\Program Files\Veritas\NetBackup\db\cloud) is locked and there are no commands available to add the China region to the Amazon plugin. I was able to get a new cloudprovider.xml from NetBackup support, but that was only because the tech working my case had one on his desktop from helping another customer. The actualsolution to this, and any other provider that isn't a default Cloud option, is to contact the vendor and request the plugin directly from them. (You may need help combining customized instances with the new .xml but I didn't experience that so I don't know the procedure). Also, my device mappings were about a year old so I had to update that file as well. (https://sort.veritas.com/checklist/install/nbu_device_mapping) After replacing the cloudprovider.xml and upgrading the device mappings I was able to see the amazonaws.com.cn instance and, (having already opened the firewall), connected the very first attempt. Firewall: source tos3-cn-north-1.amazonaws.com.cn Bidirectional TCP: (5637,80,443)Thoughts and takeaways from Vision 2017
Wow. The second Veritas Vision conference is over. And what a week it was. Press conferences, technology announcements, great keynotes, surprising demos, valuable breakout sessions, and a list of sponsors that any conference would be lucky to have. To name a few: Microsoft, Google, IBM, and Oracle. So, what was the takeaway? -that Veritas is maniacally focused on helping organizations better utilize this asset that exists in each of their environments known as secondary data. As Veritas CPO, Mike Palmer iterated on stage, “secondary data is not only the most under-utilized asset in the enterprise, it’s also the biggest opportunity.” For more than two decades Veritas has lead the market in the areas of enterprise backup and recovery, software-defined storage, and eDiscovery/archiving. However, as the world continues to both create and depend on more and more data, a better way to harness the power of their information is clearly needed. The largest data estate in our customers' environments is their secondary data. By eliminating complexity from point products,making storage smarter and more scalable, and by giving customers unprecedented levels of visibility into their data, they can not only protect it better, reduce risk more effectively and lower the total costs of managing it all, but they can unlock the value that lies therein to uncover new insights that drive business forward. And as our customers continue to embrace new architectures like cloud, OpenStack, and containers, or new workloads likeNoSQL, or Big Data, the continued commitment to support them with the kind of industry leading technology, innovation, and engineering prowess was also clear. I’m proud of what I both saw and helped create this year at Veritas vision. There was a lot of excitement and optimism regarding Veritas’ outlook and vision for the future. The Cube was onsite hosting a number of interesting conversations, one with me and Ian below on what we aim to solve for customers with 360 data management for the multi-cloud: The Challenges We Aim To Solve: As part of a community give-back, we got to make Capes for Heros: http://capes4heroes.com, which was very special. And we got some great coverage on our announcements as well: CRN:Veritas Vision: Veritas Enhances Multi-Cloud Data Management, Strengthens Ties With Microsoft Azure Cloud TechTarget:Veritas 360 data management embraces cloud, dedupe, NoSQL Also great to see the positive comments on social from our AR/PR community as well: The simple truth about public cloud: In the end, it is still your responsibility for the app and data, not the provider.#vtasvision—@edwinyuen Kudos@Lylucason very smart keynote - strong narrative, clear news, competitive digs clever/tasteful, showed momentum#VTASvision—jbuff Most clever monologue on#dataprotectionever by Mike Palmer#VTASvision—jbuff Still a good crowd at day 2#vtasvision.—@krmarko Veritas senior execs take questions. Useful perspectives on selling the new strategy: focused on particular biz data problems.#vtasvision—@krmarko With#Veritasin#LasVegasto resolve the '#Information'#Techconundrum to drive value and avert risk.#MultiCloud#GDPR#DX#VtasVision—@sabhari_idc Yes, we're closer to#Hollywoodand it had a part it the dramatic#BackToTheFuturetheme intro into#datamanagement.#NoFate#VtasVision—@sabhari_idc The modern#dataprotection capability matrix demonstrated by#Veritasat#VtasVision.#BaaS#DRaaS#Containers#MultiCloud#BigData#DX—@sabhari_idc Veritas can reach APAC customers via GDPR zd.net/2fBezbU by@eileenscyu— @ZDNet Vision was a success. But now it’s back to the grind in helping customers solve real challenges with comprehensive solutions, and a vision to help them better utilize their secondary data. Keep a pulse on what’s going on with Veritas by following us on twitter at: @veritastechllc. AlexNetBackup 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
Evacuating your assets using Veritas Resiliency Platform
The Evacuation Plan feature of Veritas Resiliency Platform lets you evacuate all the assets from your production data center to your recovery data center. Instead of individually moving your assets to the recovery center, you can save your time by adding these assets to the evacuation plan and then execute the plan with a single click operation. Resiliency Platform supports evacuation to various recovery data centers namely Azure, Amazon Web Services, vCloud Director, and even to your on-premises data center. Use the evacuation plan template to define the sequence in which the virtual business services (VBS) should be migrated from the production data center to the recovery data center. Resiliency groups that do not belong to any VBSs, are appended at the end of the evacuation plan workflow after the VBS. If you have not configured any VBSs, then the evacuation plan is created using only the resiliency groups. Having a VBS is not compulsory. An evacuation plan has Priorities. You can add the VBSs to different priority levels but the ordering of resiliency groups is done by the Resiliency Platform. You can also define the VBS priority within the priority group. When you have a large number of VBSs, then up to 5 VBSs within a priority group are migrated in parallel to the recovery data center. Similarly, if you have a large number of resiliency groups, up to 10 resiliency groups are migrated in parallel. Continue on failures is another functionality of an evacuation plan. If an asset within a VBS or a resiliency group fails to recover, the evacuation plan skips the asset and continues the process for the remaining assets. You have the option to select this checkbox while creating the evacuation plan. If you choose not to select the checkbox, then the evacuation process stops till you have fixed the problem. For a VBS or a resiliency group to successfully evacuate to the target data center, it should meet the following criteria: ■ VBS or resiliency group that belong to the evacuation plan must be configured for disaster recovery ■ VBS can contain resiliency groups some of which are configured for disaster recovery and some using the service objective with data availability as Copy. ■ Resiliency group must belong to only one VBS. After successfully creating an evacuation plan, you can perform operations such as Rehearse evacuation, Cleanup rehearse evacuation, Evacuate or Regenerate the plan. It is recommended that you perform a rehearsal to ensure that the assets are evacuated properly. After rehearsal you can run the cleanup rehearse operation to delete all the temporary objects that were created during rehearsal. At a later point in time if you make some changes to the VBSs or the resiliency groups, an alert is raised asking you to regenerate the plan. Refer to About evacuation plan for more information on the situations when an alert is raised. To create and run an evacuation plan, you need Manage Evacuation Plans permission. You can also watch the videoshere.Video - Migrating your assets to different availability zones of AWS
Using Veritas Resiliency Platform you can migrate your assets to Amazon Web Services (AWS) cloud. The following video covers how to migrate your assets to the different availability zones of AWS. Some of the reasons for migrating to different availability zones are: high availability and load balancing, or to retain your VMware cluster configuration of the source data center on the target data center. The video shows how to club your assets to form a resiliency group and configure this resiliency group for disaster recovery. While configuring, you need to choose the replication technology, select the Replication Gateways that are mapped to different availability zones, map the networks to successfully protect the assets or virtual machines.
