Archive for the 'DS8000' Category
I have today just passed my IBM 000-206 High-End Disk Solutions for Open Systems Version 1. I thought I will post out my tips for what to study to help others pass the exam as well.
1- Make sure you know when to use DS8000, DS6000, DS4000, Nseries & SVC. There are so many scenario questions that will require you to be able to distinguish between the usage of each of the above storage types.
2- Make sure you are aware of the different versions of IBM TotalStorage Productivity Center, when to use which version, & what its used for.
If you have a boot from SAN server, you will be able to easily clone it for a backup or deployment purpose using the native DS8000 FlashCopy. As mentioned earlier FlashCopy is an optional feature for the DS8000, which means it will require an additional license to enable. The SAN administrator can initiate a FlashCopy of Boot from SAN Disk using the DS8000 Storage Manager GUI or using the DSCLI.
Creating a FlashCopy on the DS8000 can be as easy as running the following command on DS8000 DSCLI, where 6100 is the source LUN & 6101 is the target LUN.
mkflash -seqnum 01 6100:6101
The minimum IBM TotalStorage support for Microsoft Volume Shadow Copy and Virtual Disk Service (VDS) supported by IBM Tivoli Flash Copy Manager is Version 4.0.1. You can obtain the latest IBM DS8000 VDS form IBM Website at:
IBM DS8000 VDS is required in order for IBM Tivoli FCM to be able to utilize the DS8000 FlashCopy feature as a hardware provider for its shadow services. If you don’t install IBM DS8000 VDS, then IBM Tivoli FCM will use the default Windows System Provider which has many limitations. The steps below illustrate the steps required to install IBM DS8000 VDS on Windows 2003 SP2.
This section provides an overview of the installation and configuration of the CIM agent on a Windows 2003 operating system. If you have decided to use the CIM agent for HMC & followed the 3.3 section, then you can skip this section directly to chapter 4. If you are not going to the use the CIM agent for HMC and decided to install the CIM agent on a Windows 2003 host then read on.
Ensure that you know how to administer a Windows 2003 operating system before you install the CIM agent. Also be familiar with the commands that you use during installation and configuration of the CIM agent.
Perform the following list of installation and configuration tasks on your Windows operating system:
Beginning with DS8000 Release 2.4, the CIM Agent is pre-installed on the hardware management console (HMC). This section includes an overview of the setup process and instructions for enabling and configuring the CIM agent on the DS8000 HMC. The DS8000 can be managed either by the CIM agent that is bundled with the HMC or with a separately installed CIM agent. The HMC CIM agent has the following limitations:
- The CIM agent is initially disabled on the HMC and must be enabled through the WebSM management console before it can be used.
- The HMC CIM agent can only support DS8000 devices that are managed by that HMC. This CIM agent is not able to manage any ESS 800 or DS6000 devices, or any DS8000 devices that are managed by a different HMC.
CIM agent is a Common Information Model (CIM) agent provides a means by which a device can be managed by common building blocks rather than proprietary software. If a device is CIM-compliant, software that is also CIM-compliant can manage the device.
Vendor applications can benefit from adopting the common information model because they can manage CIM-compliant devices in a common way, rather than using device-specific programming interfaces. Using CIM, you can perform tasks in a consistent manner across devices and vendor applications.
This task creates the free volume pool (VSS_FREE Volume Group) and the reserved volume pool (VSS_RESERVED Volume Group) that are used to assign volumes to the virtual host. Before you can use the IBM System Storage support for Microsoft Volume Shadow Copy Service and Virtual Disk Service software, you must specify the volumes that can be used as FlashCopy target volumes. You specify the volumes after you create a VSS_FREE pool and a VSS_RESERVED pool. These pools are represented by virtual hosts that are created on the storage unit. After the virtual hosts are created, you can add volumes to the free pool by assigning a volume to the virtual host. Perform the following steps using the IBM System Storage DS Storage Manager or DS CLI to create the VSS_FREE and VSS_RESERVED pools:
Before even reaching to your IBM Tivoli Flash Copy Manager installation CDs, there are few preparation steps that must be carried out on the DS8100 & any SQL Server where you will install IBM FCM in our case SQLnode01_POC, SQLnode02_POC, & SQLsrv01_POC. Please note for the integration of IBM Tivoli Storage Manager with IBM Tivoli Flash Copy Manger, IBM TSM has to be separately installed & configured, though TSM installation is out of this book scope. Though if you have an IBM Tivoli Storage Manager already setup in your environment, you will be able to integrate IBM FlashCopy manager with it easily by running through the Wizard illustrated in later chapters. In this chapter we will focus on the DS8100 preparation for IBM Tivoli FlashCopy Manager Installation.
As it takes only a few seconds to establish the FlashCopy relationships for tens to hundreds or more volume pairs. The copy is then immediately available for both read and write access. In a 24×7 environment, the quickness of the FlashCopy operation allows us to use FlashCopy in very large environments and to take multiple FlashCopies of the same volume for use with different applications. Some of the different uses of FlashCopy are shown in Figure 1-2.
FlashCopy is suitable for the following:
_ Production backup system:
The Point-in-Time Copy feature, which includes FlashCopy, enables you to create full volume copies of data in a storage unit. When you set up a FlashCopy operation, a relationship is established between the source and target volumes, and a bitmap of the source volume is created. Once this relationship and bitmap are created, the target volume can be accessed as though all the data had been physically copied. While a relationship between the source and target volume exists, optionally, a background process copies the tracks from the source to the target volume.