Understand about the global reserved LUN pool in CLARiiON

By WireINPUT -
The global reserved LUN pool works with replication software, such as SnapView, SAN Copy, and MirrorView/A to store data or information required to complete a replication task. The reserved LUN pool consists of one or more private LUNs. The LUN becomes private when you add it to the reserved LUN pool. Since the LUNs in the reserved LUN pool are private LUNs, they cannot belong to storage groups and a server cannot perform I/O to them.

Before starting a replication task, the reserved LUN pool must contain at least one LUN for each source LUN that will participate in the task. You can add any available LUNs to the reserved LUN pool. Each storage system manages its own LUN pool space and assigns a separate reserved LUN (or multiple LUNs) to each source LUN.
All replication software that uses the reserved LUN pool shares the resources of the reserved LUN pool. For example, if you are running an incremental SAN Copy session on a LUN and a snapshot session on another LUN, the reserved LUN pool must contain at least two LUNs - one for each source LUN. If both sessions are running on the same source LUN, the sessions will share a reserved LUN.

Estimating a suitable reserved LUN pool size
Each reserved LUN can vary in size. However, using the same size for each LUN in the pool is easier to manage because the LUNs are assigned without regard to size; that is, the first available free LUN in the global reserved LUN pool is assigned. Since you cannot control which reserved LUNs are being used for a particular replication session, EMC recommends that you use a standard size for all reserved LUNs. The size of these LUNs are dependent on If you want to optimize space utilization, the recommendation would be to create many small reserved LUNs, which allows for sessions requiring minimal reserved LUN space to use one or a few reserved LUNs, and sessions requiring more reserved LUN space to use multiple reserved LUNs. On the other hand, if you want to optimize the total number of source LUNs, the recommendation would be to create many large reserved LUNs, so that even those sessions which require more reserved LUN space only consume a single reserved LUN.

The following considerations should assist in estimating a suitable reserved LUN pool size for the storage system.
 
If you wish to optimize space utilization , use the size of the smallest source LUN as the basis of your calculations. If you wish to optimize the total number of source LUNs , use the size of the largest source LUN as the basis of your calculations. If you have a standard online transaction processing configuration (OLTP), use reserved LUNs sized at 10-20%. This tends to be an appropriate size to accommodate the copy-on-first-write activity.

If you plan on if you plan on creating multiple sessions per source LUN, anticipate a large number of writes to the source LUN, or anticipate a long duration time for the session, you may also need to allocate additional reserved LUNs. With any of these cases, you should increase the calculation accordingly. For instance, if you plan to have 4 concurrent sessions running for a given source LUN, you might want to increase the estimated size by 4 – raising the typical size to 40-80%.

Comments

Post a Comment

Popular posts from this blog

VMware PSOD Purple Screen of Death - Debugger waiting (world 2078) -- no port for remote debugger. "Escape" for local debugger

By WireINPUT -
Image
How to deal with PSOD - VMware PSOD Purple Screen of Death - Debugger waiting (world 2078) -- no port for remote debugger. "Escape" for local debugger - Easy troubleshooting steps and how to identify or determine exact root cause of the PSOD issue Host is down with PSOD with the above said error. Verified BIOS settings, worked with on site engineer, contacted the IBM server support (since this is IBM server, have contacted IBM, if it is IBM or some other hardware, you may need to reach out the respective vendor) Sometimes it could be server hardware issue like DIMMs, CPU, Processor related or may be a chance of network related. Please have a through check on the above said and come to a conclusion what could the issue. Based on that, need to troubleshoot the issue.
Read more

The Windows Time Service terminated with the following error - Event ID 7023 & 46

By nag -
After you upgrade a Microsoft Windows Server 2003-based domain controller to Windows Server 2003 Service Pack 1 (SP1), the Windows Time service may not start. In this scenario, the following events may be logged in the Windows System log. Message 1 Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7023 Description: The Windows Time service terminated with the following error: Not all privileges referenced are assigned to the caller. For more information, see Help and Support Center at http://support.microsoft.com. Message 2 Event Type: Error Event Source: W32Time Event Category: None Event ID: 46 Description: The time service encountered an error and was forced to shut down. The error was: 0x80070700: An attempt was made to logon, but the network logon service was not started. Additionally, when you try to start the Windows Time service manually, you may receive one of the following error messages: Error 1083: The executable program that this servic
Read more

IBM x3650 M4 Series Server Model - Activation Keys Backup to be taken for IMM Moduel II, why?

By WireINPUT -
Image
If you are planning to replace the system board (Mother Board) for M4 series of IBM xSeries 3650 model server, you should and must take the activation keys backup, otherwise you will miss the IMM key. IMM key something like iLO Activation key on HP servers. If that  iLO key didn't acivated, then you won't get the 'Remote Access' option. In the same way, IBM series requires a key to be activated to access the IMM console. IMM Activation to be backuped and restore once the new board get replaced. Here is the screenshot there you see more options what we discussed so far -
Read more