SFHA Solutions/InfoScale: How to clean up the operating system device tree
A device tree is a data structure that describes the LUNs in your environment. When you remove LUNs dynamically from an existing target ID, the operating system SCSI device tree must be cleaned up. This is to release the SCSI target ID for reuse if a new LUN is added to the host later. In Storage Foundation/InfoScale, there are two ways to do this: one if you are using Storage Foundation and High Availability (SFHA) version 6.0 or earlier you must clean up the device tree manually. In SFHA 6.0.1 and later, the device tree is cleaned up dynamically. For SFHA 6.0 and earlier For SFHA 6.0 and earlier, you need to clean up the operation system device tree manually after you remove LUNs from an existing target ID. To completely remove LUNs from an existing target ID, you need to perform the following steps: Remove LUNs. Clean up the operating system device tree. Scan the operating system device tree. The following diagram shows the process of removing LUNs dynamically from an existing target ID. For SFHA 6.0.1 and later, and InfoScale Since SFHA 6.0.1, the Dynamic Reconfiguration operations option (DR tool) is introduced in the vxdiskadm menu to simplify the removal of LUNs from an existing target ID. It saves the manual work of device scanning and cleaning up. Through the DR tool, Dynamic Multi-pathing (DMP) updates and cleans up the operating system device tree automatically. For more information about using DR tool to remove LUNs, please see: Removing LUNs dynamically from an existing target ID. The following diagram shows the process of using DR tool to remove LUNs dynamically from an existing target ID. The process is simplified by using this tool. Related links: Reconfiguring a LUN online that is under DMP control. (SFHA 6.0.1 and later) Reconfiguring a LUN online that is under DMP control. (SFHA 6.0 and earlier) The links in this article are specific to Linux platform. You can find SFHA Solutions/InfoScale documents for other versions and platforms on the SORT documents page.
Oracle 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?
Replication and Failover Product for SQL 2008 server
Hello All, I do not really know much about Clustering, Replication and Failover. I know the concepts from a hardware firewall and some discussions. I have a client that requires Replication of data on an SQL server from one location to the other SQL server at the remote site. I think Replication Exec may work from the name. What are the things I need to put in place and what Symantec product do I need to use in order to achieve this request. The client initially wanted Backup Exec 2014. But his request is more than just backup and restore. All the help will be appreciated. Thank you.ApplicationHA (for VMware) and Symantec High Availability Solution: Product Selection panel does not list any products when installing through vSphere Client integrated menu
During the installation of ApplicationHA (for VMware) or Symantec High Availability guest components through the vSphere Client, the Product Selection panel may fail to list any products. This issue occurs if you install the ApplicationHA or the Symantec High Availability Console using platform-specific installation media and install the guest components on a virtual machine on another platform. To resolve the issue, you must copy the platform-specific guest installation package on the Console host. For more information, refer to the following topics: For ApplicationHA Copying the platform-specific guest components installation package For Symantec High Availability guest components Copying the platform-specific guest components installation package Symantec ApplicationHA and Symantec High Availability Solutions documentation for other platforms and releases can be found on the SORT website.Symantec Cluster Server (VCS) 6.1 for Windows: Encrypting VCS agent passwords and user passwords
When you edit the VCS "main.cf" configuration file to perform any of the following tasks, you must encrypt the user passwords and the VCS agent passwords: Add VCS users Configure agents that require user passwords You can use the vcsencrypt utility to encrypt the passwords. To encrypt the user passwords, type the following command: vcsencrypt –vcs To encrypt the VCS agent passwords, type the following command: vcsencrypt –agent The VCS 6.1 for Windows release introduces a mode to generate a security key to create more secure passwords, for VCS agents. By default, security key-based encryption is not enabled. To generate a security key, you must add the "SecInfo" cluster attribute to the main.cf file, with a security key as the attribute value. By default, only administrators can generate security keys. Note: You can perform security key-based encryption only using the CLI. The service group configuration wizards do not use security keys to encrypt the agent passwords. For more information about encrypting the agent passwords using security keys, see: Encrypting agent passwords using security keys Generating a security key Encrypting the agent password VCS documentation for other releases and platforms can be found on the SORT website.