HP P6000 Replication Solutions Manager Administrator Guide Abstract This document describes replication concepts, licensing, configuration, maintenance, best practices, and troubleshooting for the replication manager graphical and command-line user interfaces. It also describes the use of the replication manager with Oracle products. HP P6000 Replication Solutions Manager (formerly HP StorageWorks Replication Solutions Manager) supports all HP P6000/EVA models.
© Copyright 2004–2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Replication manager overview.....................................................................8 Replication manager features.....................................................................................................8 Discovery............................................................................................................................9 Changing the discovery and refresh interval.......................................................................9 Jobs................
Configuring disk groups for local replication..............................................................................25 Creating virtual disks..............................................................................................................25 Configuring LAN settings.........................................................................................................25 3 Managing the replication manager............................................................26 Getting started......
Avoiding device pop-ups on Windows hosts..........................................................................39 Avoiding device removal pop-ups on Windows hosts..............................................................40 Mounting host volumes on Windows hosts running VSS software..............................................40 Windows host agent and Microsoft Cluster Server coexistence.................................................40 Windows 2008 dynamic disk considerations.......................
Validation fails after failover................................................................................................54 Replicating host volumes or volume groups on mount points during heavy I/O...........................54 Troubleshooting other problems................................................................................................54 Changing host name affects array manageability...................................................................
Frequently asked questions..................................................................................................74 Glossary....................................................................................................75 Index.........................................................................................................
1 Replication manager overview HP P6000 Replication Solutions Manager (the replication manager) is a graphical and command-line user interface for managing data replication on HP storage arrays. It is provided with licensed replication features, including HP P6000 Business Copy, HP P6000 Continuous Access, HP P6000 DC-Management, and thin provisioning. IMPORTANT: HP P6000 Replication Solutions Manager (formerly HP StorageWorks Replication Solutions Manager) supports all HP P6000/EVA models.
Discovery The replication manager automatically discovers storage resources and refreshes its database at regular intervals. You can adjust the interval to meet specific needs. After discovering a new resource, the replication manager needs additional time to collect all the information and add the resource to the database. In the interval between discoveries, it can appear that a new snapclone, for example, is in a constructing state longer than it actually is.
Managed sets A managed set is a named collection of resources, carrying the same characteristics and banded together for convenient management. For example, the managed set Sales_Disks includes two virtual disks, West_Sales and East_Sales. Performing an action on a managed set performs the action on all of its members. For example, if you perform the New Snapshot action on the managed set Sales_Disks, the replication manager creates a snapshot of West_Sales and a snapshot of East_Sales.
Snapshot types Snapshot types are defined by how the array allocates space for the snapshot. • Demand allocated. The array allocates only enough space to store metadata and pointers to the source data. As the source is overwritten, the array allocates more space and copies the original data to the snapshot. Use demand-allocated snapshots when less than 10–25% of the capacity of the source will change over the life of the snapshot. • Fully allocated.
Snapclones cannot be created when the disk to be replicated is: • A snapshot • A disk that has a snapshot or mirrorclone • In the process of normalizing (snapclone in progress) or being deleted Mirrorclones Mirrorclone replication establishes and maintains a copy of an original virtual disk via a local replication link. When first created (and whenever resynchronized by an action or command), a mirrorclone is said to be synchronized.
Synchronized mirrorclone guidelines The following table describes the tasks that you can and cannot perform when the mirrorclone is in a normalized/synchronized state. Deleting No. The disk must first be fractured and detached, then deleted. Detaching No. The disk must first be fractured, then detached. Fracturing Yes. Migrating Yes. Presenting No. The disk must first be fractured, then presented. Replicating No. The disk must first be fractured, then replicated. Restoring No.
Mirrorclone state Remarks mirrorclone. It becomes a normal virtual disk. Instant restore The instant restore feature is available only with certain controller software versions. Restore operations are instantaneous because the restored data is available within seconds for host reads/writes (the actual data transfer occurs in the background). The following types of instant restore are available: • Instant restore from mirrorclones.
Using instant restore when a virtual disk is mounted To use instant restore when a virtual disk is mounted: 1. Stop host I/O to the disk that you want to restore. 2. Unmount the disk. This forces the disk's write cache to be flushed (emptied). 3. Select Actions→Instant Restore for the host volume or the virtual disk in the replication manager to perform an instant restore to the disk. When the restore completes, you can mount the disk.
Follow these guidelines for using containers: • The array must have an HP P6000 Business Copy license installed. • When used for mirrorclones and preallocated snapclones, the container may be in a different disk group than the source virtual disk. When used for preallocated snapshots, the container must be in the same disk group as the source virtual disk. • A container must be the same size as the source of the preallocated snapclone or snapshot.
• A suspended DR group cannot be failed over and its members cannot be removed. The exception is that if the intersite links are broken, a suspended DR group can be failed over. • A DR group cannot be deleted if a member of the destination DR group is presented.
Select the Replicate option on the GUI to launch the Wizard. A window opens that allows you to select the host volumes to replicate and the replication type: snapshot, snapclone, preallocated snapshot, preallocated snapclone, or fractured mirrorclone. Starting the replication manager GUI You can start the replication manager GUI from: • A desktop icon Use this method if you logged on to the management server directly or through Terminal Services. Do not browse to the software from the management server.
From a browser (applet mode) You can browse to the replication manager from a supported browser on a remote computer. • If you are running HP Replication Solutions Manager 3.0 or later, you can download and install the JRE from the Java website at http://java.com/en/download/index.jsp. • If you are running HP Replication Solutions Manager 2.0 or earlier, use the HP JRE Server supplied on a CD with the replication manager. On a general-purpose server or dedicated management server 1. 2. 3.
2 Setting up the replication manager This chapter describes replication manager setup and configuration. For installation information, see the HP P6000 Replication Solutions Manager Installation Guide. HP P6000 Replication Solutions Manager environment HP P6000 Replication Solutions Manager supports communication with one local HP P6000 Command View server-based management system and one or more HP P6000 Command View array-based management systems.
Figure 2 Replication manager environment 1. LAN 4. Remote PC 2. SAN fabric 5. Hosts 3. Management server 6.
Array Compatibility Reference. For instructions on upgrading controller software, see the Updating Product Software Guide for your array model and controller software version. If needed, upgrade HP P6000 Command View to a compatible version (see the HP P6000 Enterprise Virtual Array Compatibility Reference). Initial replication manager setup The replication manager requires little setup beyond the array and array management software (HP P6000 Command View).
Configuring account credentials Configuring HP SMI-S EVA credentials for server-based management systems Consider the following scenarios: • HP P6000 Replication Solutions Manager automatically detects the presence of an HP P6000 Command View server-based management system. If the HP P6000 Command View server-based management system is detected, no configuration changes are needed.
2. Open the following file: {HP Replication Solutions Manager install} \JBoss\server\default\data\xmbean-attrs\hp.storage@3Aservice@3DReplicationServerService.xml. a. Locate the following line: 852 b. 3. Replace 852 with the same port number you entered for the SERVER_PORT. If the host agent is running, shut it down and restart it.
Table 1 Default port assignments (continued) Port Service 4096 WebServer 4444 Java Remote Method Protocol (JRMP) 5510 HP Replication Solutions Manager RMI 5511 HP Replication Solutions Manager RMI 5514 JNDI 9000 HP Replication Solutions Manager CLUI 9001 HP Replication Solutions Manager CLUI 2008 HP Replication Solutions Manager SMI-S/SAL RMI Synchronizing management servers and arrays The replication manager server and host agents generate log files for job events.
3 Managing the replication manager This chapter explains how to perform common management tasks. Getting started It is important that you understand the replication manager environment, and that you properly plan the hardware and software installation. The replication manager environment consists of a central server and several interacting host agent computers.
Performing tasks In a replication manager environment, you can perform tasks in three ways: • GUI—The GUI window provides a menu bar, toolbar, navigation pane, content pane, event pane, and status bar. • CLUI—The replication manager includes a CLUI server and client in the server software, and a CLUI remote client in the host agent software. • Create a job—You can use the GUI to create a job.
Table 2 Virtual disk actions (continued) Task GUI action Job command Virtual Disks→Preallocated-Snapclone ConvertStorageVolumeIntoContainer Virtual Disks→Instant Restore MigrateMirrorclone Virtual Disks→Migrate Mirrorclone Replicate storage volumes (template) CLUI command Set Mirrorclone Replicate storage volumes via preallocated snapclones (template) Instant restore storage volumes to other storage volumes (template) Validate ValidateSnapcloneStorageVolume ValidateSnapshotStorageVolume Minimizing
On enabled hosts, user authentication is an option when you install the host agent. If user authentication is enabled, replication manager users must be members of the following host agent administrator group created on the host: • On Windows hosts, HP Host Agent Admins, or the domain group configured during installation • On other hosts, hphaadm To add or remove users, follow the instructions in your operating system manual. Licensing applications To license application resources for replication: 1.
Table 3 Tasks requiring a license (continued) Task HP P6000 Command View HP P6000 Business Copy HP P6000 Continuous license license Access license Extending the size of a host volume X Shrinking the size of a host volume X 1 2 3 Requires valid HP P6000 Command View and HP P6000 Continuous Access licenses at both the source and destination if the virtual disk is a member of a DR group.
For export and import procedures, see the online help or the HP P6000 Replication Solutions Manager CLUI Reference. NOTE: If the replication manager database is lost or reinstalled, or if the management server is moved, the Instant Restore for Host Volumes will fail. You must export and import the database using the GUI, CLUI, or job engine. Exporting one or more jobs You can export a single job or multiple jobs.
The import process will only update the database with HP P6000 Replication Solutions Manager objects such as: • Jobs and job schedules • Replica repositories • Managed sets • HP P6000 DC-Management policies The import process will filter out objects with dependent objects that are missing from the database on which the import is being performed.
Ensuring job success To ensure job success and optimize performance: • Minimize the number of simultaneous jobs, even if they involve separate arrays. • Avoid unnecessary use of HP P6000 Command View when jobs are running. • Avoid configuring storage and hosts while jobs are running. For example, do not change an array configuration using HP P6000 Command View while replication manager jobs are running.
• Minimize the number of virtual disks with active snapshot copies. Use fewer virtual disks; it is better to have a few large virtual disks than many small virtual disks. • Minimize the number of snapshot copies for a virtual disk. Do not keep extra snapshot copies unless you have a plan for their use. • Minimize the life of a snapshot copy. If snapshot copies are used for backup, consider deleting the snapshot virtual disk at the completion of the copy to tape.
4 Working with operating systems This chapter describes replication manager setup and management procedures that are specific to operating systems. For supported operating systems, see the HP P6000 Enterprise Virtual Array Compatibility Reference. NOTE: If you upgrade the OS version of a server on which the replication manager host agent or replication manager server is running, you must reinstall the affected replication manager component after the upgrade is complete.
Cross-operating-system mounting Cross-operating-system mounting is supported on Windows 2003 x86 64-bit, Windows 2003 x86 32-bit, Windows 2008 x86 64-bit, and Windows 2008 x86 32-bit systems. Cross-operating-system mounting requires the systems run the same operating system version. For example, mounting across Windows 2008 x86 64-bit to Windows 2008 x86 32-bit systems or mounting across Windows 2003 x86 64-bit to Windows 2003 x86 32-bit.
HP P6000 DC-Management VxVM requirements and considerations • Shrink is not supported on VxVM volumes. • Expand is supported on VxVM of CONCAT layout only. Grow is not supported on other layouts, such as mirrored, striped, and layered. • Online extend is supported on VxVM volumes with VxFS, provided that Online-JFS is also available (no offline extend support). • Extend is supported on VxVM volumes on HP-UX 11.23 and 11.31, with supported VxVM versions for each operating system.
4. 5. Count the number of /dev/sg files that end in numeric values. (The /dev/sg files that end in alphabetic characters are links to the numeric versions and are not used.) If there are fewer /dev/sg files (from Step 4) than devices (from Step 2), run makesg.sh, specifying the total number of devices. You need one /dev/sg device file for each SCSI device, including direct-attached SCSI devices, SAN arrays, and each LUN presented to the host. The makesg.
Tru64 UNIX This section describes special procedures for Tru64 UNIX hosts. Running mount jobs on Tru64 UNIX hosts When running mount jobs (such as MountHostVolume) on a Tru64 UNIX host, ensure that the mount point is not placed in a subdirectory of /tmp. Otherwise, the job will hang.
You can avoid the pop-up windows by not logging in to the Windows host desktop. The replication manager host agent runs as a Windows service and does not require that a user be logged in to the desktop. Avoiding device removal pop-ups on Windows hosts When the replication manager unmounts a host volume, a Windows host may display a pop-up window indicating that a device has been removed unsafely. The pop-up does not indicate a problem; click OK to close it.
Windows 2008 dynamic disk considerations HP P6000 Business Copy jobs for a dynamic volume with the same host as the source host and the mount host is not supported. Dynamic disk replication across different Windows 2008 hosts is supported. If you have other dynamic disks at the mount host, after an HP P6000 Business Copy job completes, missing disks will remain at the end of the job on the mount host. The replication manager does not remove these entries automatically.
5 Troubleshooting replication problems This chapter offers suggestions for troubleshooting and resolving problems that can occur while using the replication manager.
To resolve an offline state condition for a dynamic disk in Windows 2008, run diskpart, and then issue the san policy=OnlineAll command on the host. Then, reboot the host and run the instant restore job. Instant restore host volume name changes Replication is performed by specifying the host name and host volume name. If a host volume name changes, the replica repositories will not be available on the host volume's Instant Restore wizard.
Invalid user defined log size. Adjust the log size before you transition to enhanced asynchronous replication: • For XCS 6.000 or later, the log size must be a minimum of 1,624 MB. • For XCS 09000000 or later, the log size must be a minimum of 5,120 MB. DR group log is not resized You can expand the size of a DR group member (virtual disk), regardless of whether the DR group is in synchronous mode or asynchronous mode.
Resolution: Close the GUI and then restart it. The correct number of event logs appears in the event pane. Server trace log The server trace log (Storage.trace) contains all events and is intended for HP personnel. Storage.trace is located in the following directory: HP Replication Solutions Manager install location\RSM\JBoss\server\default\log Storage.trace contains the replication manager server logging for the communication with HP P6000 Command View and the host agent activities.
You can configure the replication manager event log by changing the following parameter values in the hprsmha.cfg file, located in the directory HP Replication Solutions Manager_install_directory\RSMHostSW\RSMHA. • #LOG_MAXTOTALSIZE—Defines the total size of all current and historical host agent trace log files in the logs directory (default is 500 MB). When this value is reached, the oldest log is purged. • #LOG_LEVEL—Controls the trace messages that the host agent logs.
#NS_HOST_SERVICES_PRIVILEGES true #NS_APP_SERVICES_AUTHENTICATION true #NS_APP_SERVICES_PRIVILEGES true When authentication is disabled, the following sample output is uncommented and the modified values are set to false: # --Namespace items NS_SERVER_CONTROL_AUTHENTICATION false #NS_SERVER_CONTROL_PRIVILEGES true NS_HOST_SERVICES_AUTHENTICATION false #NS_HOST_SERVICES_PRIVILEGES true NS_APP_SERVICES_AUTHENTICATION false #NS_APP_SERVICES_PRIVILEGES true Operating system logs If you need to collect native
HP RSM HA INSTALLDIR/hprsmha.cfg /var/adm/errlog Linux logs The operating system log files are: HP RSM HA INSTALLDIR/core HP RSM HA INSTALLDIR/hprsmha.cfg /var/log/messages /var/log/messages.1 Sun Solaris logs The operating system log files are: HP RSM HA INSTALLDIR/core HP RSM HA INSTALLDIR/hprsmha.cfg /var/adm/messages /var/adm/messages.1 Windows logs The operating system log files are: HP RSM HA INSTALLDIR/hprsmha.
1. 2. 3. On the DNS server, insert an A record (host record) and a pointer (PTR) record or reverse lookup record for the management server. For Dynamic Host Configuration Protocol (DHCP) environments, set a permanent lease and reservation for the management server. Ensure that the DNS is configured for DHCP Auto Registration. An alternative solution is to modify the Hosts file on each browsing computer and the management server. 1. Locate the Hosts file in the following directory: 2.
Clearing Java cache If you cannot log in to the replication manager after installing a new JRE, clear the Java plug-in cache as follows: 1. Open the JRE control panel. This step varies based on the operating system. • On Windows: a. Select Start→Settings→Control Panel. b. Double-click Java Plug-in. • On HP-UX, Linux, and Solaris: a. Open a browser and select File→Open. b. Navigate to: ◦ usr/j2se/jre (HP-UX and Solaris) ◦ usr/java/j2rel.version/bin/ControlPanel (Linux) c. Double-click ControlPanel.
Unsupported use with Terminal Services Do not use the browser to access the replication manager when using Terminal Services on an HP OpenView Storage Management Appliance. Hidden SSL window Before the replication manager GUI appears, a Secure Socket Layer (SSL) window requires you to accept the security certificate. If the SSL window is hidden behind the browser window and you do not respond, the replication manager cannot continue.
7. On the Privacy tab, ensure that the Accept All Cookies slider is set no higher than Medium-High. If the slider is missing, restore it by clicking Default Level. A minimum level of cookie acceptance is required. 8. On the Security tab, ensure that the slider for Internet security for this zone is set no higher than Medium. If the slider is missing, restore it by clicking Default Level. Troubleshooting job events The following information can help you resolve job errors and failures.
This error can result from disrupted communication between the replication manager and its host agent. For example, a host may have rebooted during the job. Look for host and host agent issues and resolve the problem as instructed. No presentation target found for host You run a job and receive the following event: No presentation target found for enabled Host name. HP P6000 Command View did not recognize the specified host.
Failure to mount snaps After ensuring the latest driver components and HBAnywhere were installed on the hosts involved (one cluster), the GUI indicated a good status (green checkmark) on the enabled hosts, but attempts to run a job resulted in failure to mount the snapshots or snapclones. Check the Internet binding order and ensure that the first item is the network on which the replication manager server resides. See “Configuring Windows and Linux systems with multiple network interface cards” (page 39).
To regain manageability of the array: 1. Log on to HP P6000 Command View and take the control of the array. 2. Log on to HP P6000 Replication Solutions Manager, and select Tools→Configure. 3. Select P6000 EVA Management Servers in the navigation pane. 4. Click Add, and enter the new server IP address. Suspending source before replication Suspending source before replication explicitly adds a Launch command before and after the replication manager snap command.
2. If the following error message appears, proceed to Step 3. Operation failed! Target Object Does Not Exist 3. On the HP P6000 Command View navigation pane, Settings view, select P6000 CV on hostname. The HP P6000 Command View Management Properties window opens. 4. Click Discover Storage Systems. A discovery of storage resources in HP P6000 Command View is performed. Wait for the discovery to complete before performing the next step (this can take several minutes). 5.
0c1e5f0c: Severity: Critical – failure or failure imminent. The members of the specified Source Data Replication Group have not been presented to the host because the remote Storage System is not accessible. One instance of application mode is supported If you are using the replication manager in application mode, you can open only one instance of the replication manager GUI.
1. 2. Remove the extend and shrink policy for the host volume. Add the extend and shrink policy back to the host volume. The inconsistent state of the policy is cleared.
6 Support and other resources Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
• HP Software Downloads: http://www.hp.com/support/downloads • HP Software Depot: http://www.software.hp.com • HP Support Center: http://h20566.www2.hp.com/portal/site/hpsc/public/ • HP Single Point of Connectivity Knowledge (SPOCK) http://www.hp.com/storage/spock • HP SAN manuals: http://www.hp.com/go/sdgmanuals Typographical conventions Table 4 Document conventions Convention Element Blue text: Table 4 (page 60) Cross-reference links Blue, underlined text: http://www.hp.
Table 4 Document conventions (continued) Convention Element NOTE: An alert that calls attention to additional or supplementary information. TIP: An alert that calls attention to helpful hints and shortcuts.
A Using the replication manager with Oracle tools Starting with HP Replication Solutions Manager 5.1, Oracle integration is not supported. Customers with an Oracle application integration license wanting to upgrade to HP Replication Solutions Manager 5.1 must migrate their Oracle jobs using the replication manager. For instructions, see “Migrating Oracle jobs” (page 62). This appendix contains procedures for using HP Replication Solutions Manager with Oracle products, including sample SQL scripts.
// NOTE: Please remove the archive logfile Switch, Add, and Snap commands below if this job is not backing up archive log files // // Force a log switch to get the most current archive logs. SwitchOracleArchiveLogFilesUsingRepository ( $repository ) onerror pauseat E3: // OPTION: Add the archive logs AddOracleArchiveLogFilesToRepository ( $repository ) onerror pauseat E3: // Replicate the items in the repository.
ValidateSnapshotHostVolume ( $source_hostvol_unc3 ) ValidateSnapshotHostVolume ( $source_hostvol_unc2 ) ValidateSnapshotHostVolume ( $source_hostvol_unc1 ) // // Suspend the host application. Launch ( "15.146.153.141", "suspend_oracle_database.
Example 1 Suspend Oracle database batch file You must create a batch file to suspend the Oracle database before the snapshot starts. In the following example, SQLPlus.exe is located in the C:\oracle\product\10.2.0\db_1\BIN folder on host 15.146.153.141, and suspend_oracle_database.sql is located on C:\oraclescripts. suspend_oracle_database.bat C:\oracle\product\10.2.0\db_1\BIN\sqlplus "@C:\oraclescripts \suspend_oracle_database" > C:\oraclescripts \pre.log suspend_oracle_database.
In addition to facilitating backup, the replication manager allows you to create instant, independent copies of one or more database volumes. You can mount these copies on a separate host for batch processing, data mining, application testing, data warehousing, or other processes that could benefit from having an independent copy of the database. For a point-in-time backup to be valid, you must ensure that the replicas contain an application-consistent copy of the database.
Archived redo logs The online backup function requires that the database is run in ARCHIVELOG mode. In this mode, as each online redo log fills up, Oracle copies it to the location specified by the ARCHIVE_LOG_DEST parameter and begins filling the next online redo log. The online redo logs are recycled and a sequential trail of redo is maintained; therefore, any changes that are lost can be rolled forward.
Using the replication manager to back up an Oracle database The general sequence of steps for implementing snapshot- or snapclone-based backups of an Oracle database using the replication manager is as follows: 1. Determine which tablespaces need to be backed up. 2. Create the batch and script files to suspend and resume the desired tablespaces. 3. Determine which volumes need to be replicated. 4. Construct the replication manager job to replicate the volumes identified in step 3. 5. Test the process.
A description of each command follows: • connect internal/letmein; Connects to the database with the specified user name and password. In this case, the user is internal and the password is letmein. • archive log list; Issues the archive log command with the list parameter.
• archive log list; Issues the archive log command with the list parameter. The command output looks similar to this: Database log mode Archive Mode Automatic archival Enabled Archive destination H:\archive Oldest online log sequence 312 Next log sequence to archive 313 Current log sequence 313 Identify the current log sequence number (313 in this exapmple), which shows the output from SQL *Plus being redirected to a log file. • alter system switch logfile; Forces a log file switch.
WEBorc2.ora Data file #2 for WEB WEBorc3.ora Data file #3 for WEB Volume G: WEBorc4.ora Data file #4 for WEB WEBorc5.ora Data file #5 for WEB Volume H: Archived redo logs only To capture all data files for the WEB tablespace, a replication manager job would need to create replicas for E:, F:, and G:. This is because the WEB tablespace has data files located on all three volumes.
E2: DeleteStorageVolumes ( $Rep1 ) onerror pauseat E2: Exit ( SUCCESS ) E1: Exit ( FAILURE ) Testing the process If used correctly, the replication manager can greatly improve the efficiency of your Oracle backup, restore, and migration operations. As with any change to your database configuration or backup plan, it is important that you understand all aspects of your backup and restore operations and test them thoroughly before implementing them in a production environment.
Volume replacement The volume replacement method completely removes the existing source volume and replaces it with a backup copy. This method is preferred when a physical failure of the source volume has occurred, or if the combined size of the files that need to be restored is large enough that a selective file replacement would take too long to complete.
methods for performing data file recovery, tablespace recovery, and database recovery. See the Oracle documentation for more information. Frequently asked questions This section answers frequently asked questions regarding the migration of HP P6000 Replicaton Solutions Manager/Oracle users to alternative solutions. Will I have to purchase a new license to use Oracle products with HP Replication Solutions Manager 5.1 or later? No.
Glossary This glossary defines terms that are used in this guide or are related to the software. A allocation policy Storage system rules that govern how virtual disks are created. Demand allocated and Fully allocated are the two rules used in creating virtual disks. • Fully allocated–The space a virtual disk requires on the physical disks is reserved, even if the virtual disk is not currently using the space.
G general-purpose server A server that runs customer applications such as file and print services. H host A computer that runs user applications and uses the information stored on an array. HP P6000 DC-Management Dynamic capacity management feature that enables you to extend (increase) or shrink (decrease) the size of a host volume without disrupting host I/O. J JNDI Java Naming and Directory Interface. job A repeatable custom script that automates replication tasks.
server-based management Management from a server. See also management server. snapclone A copy that begins as a fully allocated snapshot and becomes an independent virtual disk. Applies only to the HP EVA. snapshot A nearly instantaneous copy of the contents of a virtual disk created without interruption of operations on the source virtual disk. Snapshots are typically used for short-term tasks such as backups. SPOCK Single Point of Connectivity Knowledge website.
Index A application licensing process, 29 replication manager setup, 22 array initializing, 25 troubleshooting, 55 B backing up the database, 30 best practices jobs, 33 using log files for troubleshooting, 43 browser cache settings, 50 configuring, 49 security setting, 51 troubleshooting, 48 C cache browser settings, 50 flushing before DR group failover, 39 Cannot find LUN, 53 CLUI overview, 19 codes event, 9 configuring browser, 49 Domain Name Server, 48 HBA ports, 53 host with multiple NICs, 39 hosts, 5
contents, 9 exporting the database, 30 F failover controller, 17 definition, 17 fabric or path, 17 troubleshooting, 54 firewall opening the host agent port, 23 fully-allocated snapshot definition, 11 H host user group, 28 host agent description, 10 replication manager setup, 22 security log, 46 trace log, 45 host agent software, 26 HP OpenVMS system log, 47 HP P6000 Business Copy license, 30 licensing, 22 requirements, 30 HP P6000 Command View adding port name, 53 changing the password, 23 defining hosts,
long delays on HP-UX, 36 M managed set definition, 10 management server synchronizing, 25 mirrorclones description, 12 guidelines, 12 Mozilla browsing to the replication manager, 19 clearing cache, 50 multipath configuring Solaris hosts, 38 N Netscape, 51 NICs configuring Windows or Linux, 39 no presentation target found, 53 null exception, 52 O online help description, 10 online redo logs, 67 operating system logs, 47 Oracle database back up, 68 database, resuming, 65 database, suspending, 65 migrating
browser problems, 48 cannot browse to management server, 48 cannot detect destination LUN, 56 email notification, 52 HP P6000 Command View, 48 job fails at CreateHostVolume, 37 jobs, 52 jobs on Solaris hosts, 38 Linux responsiveness, 38 long delays or time-outs on HP-UX, 36 loss of access to source array, 56 missing information for Linux hosts, 37 no GUI window, 51 preallocated snapshot or snapclone, 53 resources in unknown state, 56 sources of information, 42 Terminal Services, 51 unknown objects in databa
