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.1.1KViews0likes0CommentsVeritas 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.1.1KViews0likes0CommentsVeritas 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.487Views0likes0CommentsVeritas 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.556Views1like0CommentsWelcome to the Veritas Relisiency Platform Forum - Join the Conversation!
Welcome to the Veritas Relisiency Platform Forum! Here you can share thoughts, ask questions, and access product experts. Join an existing discussion or start your own.Below you will find some basic informationfor your reading pleasure. Resources: Blog: Transforming IT Service Continuity for the Enterprise with Veritas Resiliency Platform Data Sheet:Veritas Resiliency Platform Video: Simplifying IT Service Continuity with Veritas Resiliency Platform Video: Transforming IT Service Continuity for the Enterprise with Veritas Resiliency Platform Thank you for your interest in the Veritas Resiliency Platformand we look forward to your ongoing questions and discussion.1.3KViews2likes0CommentsCFS Health Check ?
Hi All, We have recently built a 4-node Oracle single-instance CFS cluster, with more to on the way. The cluster will host many databases, and all nodes will be active. The databases will migrate from non-clustered to CFS clustered servers, and we are concerned about what effect CFS may have on performance. Concerns: - Suitability of our LLT links to handle intra-node communication generated by CFS ? - Location of CFS primary, for each filesytem, and how to determine if it is optimal ? - When multiple nodes write to the same filesystem simultaeously, would that be detrimental to performance ? - I am aware of GLM lock/release as one source of CFS intra-node traffic, but wondering if there are other significant sources, such as VxFS cache coherency ? - How to best monitor CFS overhead, intra-node traffic, and overall health ? Thank your for reading ! Ken W ---------------------Configuration--------------------- Red Hat RHEL 6.5 SFCFSHA 6.1.1 with P200 patch 2 x 1 Gbit ethernet as LLT links, on dedicated VLANs Oracle 11.2.0.3 and 12.1.0.2 Oracle code local to each node (outside of cluster control) Oracle data files on CFS filesystem dedicated to only datases running on that node. Oracle Redo on a single shared filesytem for all nodes. -------------------------------------------------------------Solved1.4KViews0likes3CommentsOracle Data Base Replication with VVR under SFCFSHA/DR
Hi All; we are looking for whether VVR can use for the oracle database replication instead of oracle data guard solution. If it is used, do you know veritas gives support for any problem faced. even VVR keeps the write order fidelity, it is not certain the database integrity will ve preserved at the disaster site. do you have any best practices and white papers, experience, anything you suggest for this deploymeny?1.1KViews1like4CommentsUnable to bring the Service Group online.
Hi All, I tried to bring a SG online in a node but it's not comming online. Let me explaing the issue. We did reboot of a node aixprd001 and we found that /etc/filesystem is corrupted so the SG bosinit_SG is in partial state since lot of cluster FS in not mounted. Then we corrected the entry and done the manual mout of all the FS but the SG still show the status partial so we did the bellow command. hagrp -clear bosinit_SG -all Once done the SG is in online state. For safer side we tried to offline the SG and brought it up online again but the SG failed to come online, Bellow is the only error we able find the engine_A.log file. 2014/12/17 06:49:04 VCS NOTICE V-16-1-10166 Initiating manual online of group bosinit_SG on system aixprd001 2014/12/17 06:49:04 VCS NOTICE V-16-1-10233 Clearing Restart attribute for group bosinit_SG on all nodes Please help me by providing suggestion, I will provide the output of logs if needed. Thanks, RufusSolved2KViews0likes4CommentsServer down cases
I am not sure whether I am asking this question to the right place however, A general question,some days earlier I have heard that facebook server has gone down for 15 mins.Some years ago i have heard the same news in some other big company that server has down for 20-25 mins.They have a huge datacentres with DR's available also.So, How their internet sites went down. Kindly assist its reason.Solved741Views0likes1Commentafter mirroring plex, ssh service are not running
hi all, i have some productions server that are using SFHA Cluster. i need to mirroring volume to new storage using. (#vxassist -g DGname mirror VOLname alloc="vxdisk1 vxdisk2 . . . . vxdisk13") after 190 minutes ssh service cannot be access. i aborted the process, because im afraid it will affected another service group and make server get panic and then reboot. if there anyone have some resolve plan like we mirroring in subdisk level?1.1KViews0likes1Comment