Video - Managing Evacuation Plan in Veritas Resiliency Platform
The following video covers how to evacuate your assets to Azure using Veritas Resiliency Platform. The following Evacuation Plan operations are shown: Generate an evacuation plan Rehearsal Cleanup rehearsal Evacuate to Azure data center The next video covers the following: How and when to regenerate an evacuation plan. How todeal with the errors which occur during the evacuation operation. Evacuation Plan Blog
Enable Deduplication on NetBackup 7.5
Hi, We have got NetBackup 7.5.0.6 running on Windows Server 2008 and currently backing up data on SAN Storage. I want to enable deduplication on it. Couldyou please provide me the best practice procedure to do so ? Where the deduplication should be enabled on client or Server level and how it will be reflected on SAN storage? Please adivse Regards, --Tarek--Veritas Resiliency Platform 1.1: Using virtual business services
Any business service is typically made up of multiple components, databases, applications, and web servers. For a business service to work properly, all of its tiers and components must be up and working together. Tiers represent the logical dependencies between the resiliency groups and determine the relative order in which the resiliency groups start and stop. To ensure business continuity, make sure that not just the individual tiers are up and running but also the entire business service. For example, a payroll business service might include a web server, a database, and a payroll application. The payroll application requires the web server, application, and the database to be up and running to provide payroll service. Even if one component were down, the payroll service would be down. From a business perspective, the payroll service is unavailable without the web server and the database also being available. The logical dependencies between the parts of the business service determine the relative order in which they must start and stop to continue to provide the service. A virtual business service (VBS) is a multi-tier business service. In Veritas Resiliency Platform, a VBS lets you group multiple services as a single unit for visualization, automation, recovery, and controlled start and stop in the desired order. A VBS is composed of resiliency groups, the unit of management and control in Resiliency Platform. You organize related assets into a resiliency group and manage and monitor them as a single entity. Within a VBS, resiliency groups are arranged in tiers. Tiers represent the logical dependencies between the resiliency groups and determine the relative order in which the resiliency groups start and stop. For example, you can group a web server resiliency group, a database resiliency group, and a payroll business logic resiliency group into a VBS called payroll. The database resiliency group must start first, so the database resiliency group must go in the lowest tier. The application server resiliency group must start after the database resiliency group, so it goes in the next tier. The web server resiliency group must start last, so it goes into the top tier. The Resiliency Platform console lets you create a VBS by dragging and dropping resiliency groups into tiers. The console also includes a graphic representation of the order in which they start and stop. Creating a virtual business service Resiliency Platform also lets you customize a VBS to speed up start and stop operations of the resiliency groups within it if some dependencies are not required. Customizing a virtual business service Veritas Resiliency Platform documentation can be found on the SORT website.Veritas InfoScale 7.0: Configuring I/O fencing
I/O fencing protects the data on shared disks when nodes in a cluster detect a change in the cluster membership that indicates a split-brain condition. In a partitioned cluster, a split-brain condition occurs where one side of the partition thinks the other side is down and takes over its resources. When you install Veritas InfoScale Enterprise, the installer installs the I/O fencing driver, which is part of the VRTSvxfen package. After you install and configure the product, you must configure I/O fencing so that it can protect your data on shared disks. You can configure disk-based I/O fencing, server-based I/O fencing, or majority-based I/O fencing. Before you configure I/O fencing, make sure that you meet the I/O fencing requirements. After you meet the requirements, you can refer to About planning to configure I/O fencing to perform the preparatory tasks and then configure I/O fencing. For more details about I/O fencing configuration, see: Cluster Server Configuration and Upgrade Guide InfoScale documentation for other platforms can be found on the SORT website.
Veritas InfoScale 7.0: Configuring I/O fencing
I/O fencing protects the data on shared disks when nodes in a cluster detect a change in the cluster membership that indicates a split-brain condition. In a partitioned cluster, a split-brain condition occurs where one side of the partition thinks the other side is down and takes over its resources. When you install Veritas InfoScale Enterprise, the installer installs the I/O fencing driver, which is part of the VRTSvxfen package. After you install and configure the product, you must configure I/O fencing so that it can protect your data on shared disks. You can configure disk-based I/O fencing, server-based I/O fencing, or majority-based I/O fencing. Before you configure I/O fencing, make sure that you meet the I/O fencing requirements. After you meet the requirements, you can refer to About planning to configure I/O fencing to perform the preparatory tasks and then configure I/O fencing. For more details about I/O fencing configuration, see: Cluster Server Configuration and Upgrade Guide Veritas InfoScale documentation for other releases andplatforms can be found on the SORT website.Veritas Resiliency Platform 1.1 key components
Veritas Resiliency Platform brings separate data centers together in a resiliency domain for managing and monitoring workload automation and disaster recovery (DR). Resiliency Platform provides two types of servers, which are deployed as virtual appliances on the data centers. Resiliency Manager The main interface for managing the resiliency domain. A Resiliency Manager is deployed at each data center. After you complete a simple configuration on the virtual appliance, you do all further configuration and operations from an easy-to-use browser-based console. Since the built-in replication between Resiliency Managers keeps the data at each Resiliency Manager synchronized, it does not matter which Resiliency Manager you connect to in the resiliency domain – you see the same information on the browser. Resiliency Manager Infrastructure Management Server (IMS) The server that collects data from the customer assets at the data center. The IMS orchestrates with the APIs of the various platforms that Resiliency Platform integrates with, for example virtualization platforms, such as VMware vSphere and Microsoft Hyper-V, as well as array-based replication and replication appliances. Once you have added the assets that you want to monitor and protect to the IMS, the IMS continues to automatically discover their status. Infrastructure Management Server (IMS) Resiliency Platform release 1.1 adds support for using the Veritas InfoScale Operations Manager server for discovery and management of Veritas InfoScale applications. Veritas Resiliency Platform support for InfoScale applications You can find other versions of Veritas Resiliency Platform on the SORT documentation page.Veritas Resiliency Platform 1.1 disaster recovery
You can use Resiliency Platform for automated disaster recovery of replicated virtual machines and applications. Replication in a Resiliency Platform deployment You use the browser-based console to create resiliency groups of assets (virtual machines or applications) to manage together. You apply DR configuration to resiliency groups to prepare for disaster recovery operations. Once DR is configured, you can use automated one-click DR operations, such as Migrate or Takeover, on the resiliency groups. Resiliency Platform also provides DR testing, called Rehearsal, to ensure that the remote site is functioning properly. For more information on DR in Resiliency Platform, see the following topics: VMware virtual machines VMware virtual machines disaster recovery - an overview of key steps Hyper-V virtual machines Hyper-V virtual machines disaster recovery - an overview of key steps Applications An overview of key steps required for disaster recovery of applications For details on supported replication platforms, virtualization platforms, and applications, refer to: Veritas Resiliency Platform 1.1 Hardware and Software Compatibility List You can find other versions of Veritas Resiliency Platform on the SORT documentation page.
Veritas Resiliency Platform 1.1 disaster recovery
You can use Resiliency Platform for automated disaster recovery of replicated virtual machines and applications. Replication in a Resiliency Platform deployment You use the browser-based console to create resiliency groups of assets (virtual machines or applications) to manage together. You apply DR configuration to resiliency groups to prepare for disaster recovery operations. Once DR is configured, you can use automated one-click DR operations, such as Migrate or Takeover, on the resiliency groups. Resiliency Platform also provides DR testing, called Rehearsal, to ensure that the remote site is functioning properly. For more information on DR in Resiliency Platform, see the following topics: VMware virtual machines VMware virtual machines disaster recovery - an overview of key steps Hyper-V virtual machines Hyper-V virtual machines disaster recovery - an overview of key steps Applications An overview of key steps required for disaster recovery of applications For details on supported replication platforms, virtualization platforms, and applications, refer to: Veritas Resiliency Platform 1.1 Hardware and Software Compatibility List You can find other versions of Veritas Resiliency Platform on the SORT documentation page.Veritas Resiliency Platform 1.1 key components
Veritas Resiliency Platform brings separate data centers together in a resiliency domain for managing and monitoring workload automation and disaster recovery (DR). Resiliency Platform provides two types of servers, which are deployed as virtual appliances on the data centers. Resiliency Manager The main interface for managing the resiliency domain. A Resiliency Manager is deployed at each data center. After you complete a simple configuration on the virtual appliance, you do all further configuration and operations from an easy-to-use browser-based console. Since the built-in replication between Resiliency Managers keeps the data at each Resiliency Manager synchronized, it does not matter which Resiliency Manager you connect to in the resiliency domain – you see the same information on the browser. Resiliency Manager Infrastructure Management Server (IMS) The server that collects data from the customer assets at the data center. The IMS orchestrates with the APIs of the various platforms that Resiliency Platform integrates with, for example virtualization platforms, such as VMware vSphere and Microsoft Hyper-V, as well as array-based replication and replication appliances. Once you have added the assets that you want to monitor and protect to the IMS, the IMS continues to automatically discover their status. Infrastructure Management Server (IMS) Resiliency Platform release 1.1 adds support for using the Veritas InfoScale Operations Manager server for discovery and management of Veritas InfoScale applications. Veritas Resiliency Platform support for InfoScale applications You can find other versions of Veritas Resiliency Platform on the SORT documentation page.