Ibm spectrum virtualize Accelerate with ibm storage ibm spectrum virtualize hyper swap deep dive dee Ibm spectrum scale fundamentals workshop for americas part 1 components archi Ibm spectrum scale fundamentals workshop for americas part 3 Information Life Related Books Free with a 30 day trial from Scribd. Related Audiobooks Free with a 30 day trial from Scribd. Elizabeth Howell. Sun storage tek technical presentation 1. Your business is really taking off - your data is growing even faster You need greater Enterprise-level Data Protection 14 Heterogeneous Operating System Support 21 Grow Without Disruption Dynamically scale the volume as the application needs dictate.
Reduce System Downtime Performance degradation is often a precursor to component or system downtime, performance tracking enables predictive, preemptive maintenance. Link to Sun Download Center to easily download, install, and track patches as needed.
What's HOT about this new array? Fail-over drive MPxIO. Licensing key for purchase. Licenses are keyed to the array serial number. A remote mirror bitmap tracks differences between the master volume on the primary disk and the master volume on the secondary disk.
The remote mirror software continually replicates the data to remote sites while your applications are accessing the data volumes. You can also manually update the data on the secondary site volume by issuing a command to synchronize the primary and secondary site volumes. You can also restore data from the secondary volume to the primary volume by issuing a command to reverse-synchronize the volumes. For more information about Sun StorageTek Availability Suite software, see the product documentation.
Sun ZFS Storage appliances support snapshot-based replication of projects and shares from a source appliance to any number of target appliances manually, on a schedule or continuously. The replication includes both data and metadata.
Remote replication, or just replication, is a general-purpose feature optimized for disaster recovery, data distribution, disk-to-disk backup and data migration. Resource groups and replication components enable the Geographic Edition software to manage data replication and takeover between clusters.
You can also configure a protection group to replicate data from a primary cluster to a secondary cluster. For more information about configuring data replication, see the guide for the data replication product you are using:. The Geographic Edition software extends Oracle Solaris Cluster resource management features to integrate the data replication products. When you configure a protection group, the Geographic Edition software creates replication resource groups for monitoring and controlling data replication.
A replication component is an entity that is being replicated. CLI command r eference. Installation and initial configuration instructions. Installation and configuration instructions. User Guide for the J Array Family. Complete details of the hardware components, rail and tray installation, and cabling. Late-breaking information not included in the information set. Installation and use of the management software using a GUI. Installation and use of the management software using a CLI.
Power supply and fan replacement procedures. Listing of late-breaking information, known issues and workarounds. Graphical depicting initial setup and configuration. Installing the array enclosure into a rack using the XJ slide rail system. Configure and learn about your Sun Storage J array.
Install, replace and troubleshoot hardware components. Troubleshoot and isolate system problems with available diagnostic tools and logs. CAM software supports the following Sun storage systems:. Installing the minimum Solaris operating system package as listed in TABLE 7 will install all but the last four packages. Those packages are required by Java, but are not used by the management software.
The bit versions of the packages and files are required. Windows with SP Service Pack 4 or higher. If needed, download the files from the Microsoft Download site. You must be logged in to the Windows system as an administrative user.
The array installation files and installers are provided in a compressed file on the CD. The process unpacks the contents of the file on the host and then proceeds with the installation. After the installation on a Windows platform, you will need to configure the Windows firewall on each host to allow an exception for port Open the following incoming and outgoing ports for secure-by-default Solaris, Linux, and Windows platforms:.
If a proxy agent is used, then ann open port is required, in addition to the above ports. This allows for TCP protocol traffic. Use open port only if a proxy agent is used. For Windows, refer to the documentation for instructions on how to open a port through the firew all. The remote scripting command-line interface client sends commands to a management host, which in turn sends the commands to the array. For best web browser performance while using CAM, do the following:.
To avoid DNS-lookup delays, be sure arrays are connected. Otherwise, Windows might take a long time looking up information for arrays that are not being managed by CAM, if you have them listed in the system as being connected to the system.
The command-line interface is available in:. This section describes release-specific steps for firmware and management software patch upgrades that you must perform:. Before you perform an installation procedure, do the following:. If supported by your array types, verify that you have license certificates for all premium features, including storage domains. See Licensing Optional Premium Features. Log in as root Solaris and Linux or as a user with administrator privilege Windows on the management host.
Note that before starting the installation script, the CD verifies host requirements, such as the following:. If the script detects that there is no earlier version installed, it will perform a complete new installation. For more information, contact Sun Microsystems Support Services. Service Contact Information. Solaris: Upgrades from CAM 5. You are not required to uninstall the existing CAM version before installing this release.
Windows: Upgrade to this build is not supported in bit Windows Uninstall of previous CAM version is required before installing this build in bit Windows In other Windows platforms, upgrade to this build is supported.
If installation failure occurs, check the available disk space. If you are installing the management software on a new host, check the installation requirements and follow the entire installation and configuration procedure described in the Sun StorageTek Common Array Manager User Guide for the J Array Family part number or the Sun StorageTek Common Array Manager Software Installation Guide part number You can install CAM on a local management host or on a central management server.
Before installing the management software, do the following:. After initial installation and configuration, you can upgrade the management software and firmware with each release. During installation, the firmware update bundle is installed on the host server. You can perform a minimal installation that enables one of two options: a command-line interface only or a command-line interface with firmware.
Minimal installation does not require the web server to be running in order to function and is limited to calls on the management host where the management software is installed. This light-weight management solution is installed on a data host attached to the array.
The data host can also serve as a management host using the CLI only installation option and provides:. This option is also used to load the proxy agent that allows communication between the full management software on a central management server and the array.
Minimal Installation can stand alone, whereas Remote Client installation requires a fully installed image on a separate host. From the Common Array Manager Installation page, select one of these options in the Select a feature bundle list:. Click Next and follow the prompts by pressing 1 for Next, 3 to Cancel, or 5 to Redisplay.
The software will notify you as it checks your system and does any or all of the following:. From the host software installer, select Uninstall. The system will notify you that the un-installation has been successful. Navigate to the appropriate directory for your operating system:. For the Suse 9 platform, CLI uninstall requires the following rpm packages:. Enter the command uninstall -f. If you still have problems, enter the command uninstall -f -s.
The command will remove the current installation. CAM firmware is installed in the following locations:. Within the directory where you installed the firmware, a README file for each array type define the firmware baseline. Sun Storage J Sun StorageTek , , and Arrays. Sun StorageTek Flexline , , and Arrays. Check the build notes file distributed with the software for the exact firmware build.
CAM will support one prior version of the firmware for legacy features on previous ly supported arrays. For information about how to install firmware, see Installing the Firmware Baseline. In the following tables, the paths listed in the Firmware File column is relative to the images subdirectory where firmware files are located. In the following tables, the path listed in the Firmware File column is relative to the images subdirectory where firmware files are located. For optimal performance, Sun Microsystems recommends that the firmware on all arrays be at the level of the current firmware baseline.
New features are not supported with non-baseline firmware. As part of the CAM installation, the script puts the array firmware files in a directory on the management host. When you upgrade the firmware, the software analyzes the firmware installed on the array.
If the baseline firmware on the host is newer, and you choose to install, the software installs the baseline firmware on the array. Click Install Firmware Baseline, and follow the prompts. To add trays with data already on them, contact your service representative for assistance to avoid data loss. Refer to Upgrading Firmware for Additional Expansion Trays for the procedure to upgrade trays without data.
Controller firmware After installing the firmware, controllers can use CSM expansion modules and CSM expansion modules can be used with and controllers. When you add a new CSM expansion module to an existing array in a production or active environment, you must cable and add the trays while the RAID controller module is powered on. Before connecting any replacement drive or additional expansion module to an existing functioning array, it is best practice to contact Sun Microsystems Support Services see Service Contact Information.
One reason for this is to avoid issues related to DACstore, the configuration and status database maintained by the array firmware, that stores its information on each of the disk drives. Because corrective actions for a DACstore issue may require a configuration restoration, it is important to maintain a current image of the configuration.
And, as always, it is best practice to maintain recoverable backups of your data. The following tables list the supported expansion modules:. Supported Expansion Modules with Controller Firmware After the initial installation, you can install future changes to the 07 baseline firmware using the procedure that follows.
This follo wing does not apply to J arrays: After an upgrade to the 7. In previous firmware levels, the default size was 16K. After you register the arrays with CAM, you can upgrade to the current baseline firmware. Before cabling the newly supported expansion module, upgrade the existing controller and trays.
For adding trays to arrays managed by CAM:. Do not cable the additional expansion tray. Install the Common Array Manager release following the standard installation procedure. Use Service Advisor to cable the additional expansion tray and add it to the array. Upgrade the array again to update the firmware on the new tray.
Support has been added for a third expansion tray and 48 drives. The following sections provide information about known issues and recommended workarounds, as well as operational information not found elsewhere in the documentation:.
Workaround -Use the sscs CLI service command to manage data channels 3 and 4. Bug -When you select the device name link from the Alarm Summary page, you might get an exception or an error. For instance, a java stack trace might display in the main UI window. Workaround -Select the device from the main window. When an array is out of compliance, a number of operations might not occur, such as:.
Workaround - Use valid values. Bug -Some jobs, like volume creation jobs, cannot be cancelled on the array once they have started. However, if multiple jobs are queued up for an array, any job in the queue can be cancelled before the array actually starts the job. Bug -List devices can show multiple unlabeled entries.
List storage systems can show multiple unlabeld entries as well. The CLI user is unable to differentiate between unlabeled entries. Workaround -Rename each unlabeled device to a unique Temporary Name.
0コメント