IBM E16RMLL-I Implementation Guide - Page 77
Image disk sizing
![]() |
View all IBM E16RMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 77 highlights
To additionally increase the storage pool to hold archive data as well, follow these steps: 1. Using Table 2-1 on page 18 and the GB copied per archive field, group all machines that require simultaneous archive operations during one common time frame (for example, every month). Select the biggest group, giving peak archive size. 2. Take 10% of the peak archive size, giving the archive storage size. For example, using the sample figures in Table 2-1 on page 18: 1. Assuming a monthly/month-end time frame as our baseline, we have the workstations (200 GB) and database servers (80 GB), which equals 280 GB. 2. Taking 10% from all archive storage required during the time frame, 280 GB * 0.10 = 28 GB for archive disk storage. 2.8.11 Image disk sizing If you are planning to use image backups, you should consider sizing the disk storage pool to hold the file spaces you want to back up. This is because image backups are single objects and therefore the server will require that size for storing data (or at least part of it, assuming compression is enabled). For example, assuming that the client file spaces eligible for image backup are /oralog (200 MB), /finsys (1.5 GB), /oradata (1 GB), and /findata (1 GB), then the disk image requirements should be at least 3.7 GB to hold those file spaces in disk without having to use tape immediately. This is especially true if you are running parallel backup operations (that is, executing multiple concurrent backup image commands). Alternatively, since the disk storage requirements are so high for this operation, you could consider sending these backups straight to tape, provided that you have enough tape drives and the backup window is longe enough to coexist with normal backup and archive operations as well. Note: You must sum up all disk storage requirements (backup, archive, image) to have your final disk storage size. You can, of course, start with smaller numbers and evaluate future growth. We recommend that the disk storage pools be allocated on fault-tolerant hardware devices such as RAID 5 devices. If you are using hardware or operating system mirroring, you need to plan for the mirror copy by doubling the amount of disk for the primary storage pool. Various file systems have different maximum capacities, so the primary storage pool may have to be split across numerous volumes to make up your total primary storage pool size. We recommend that the disk storage pools be placed Chapter 2. Implementation planning 47
![](/manual_guide/products/ibm-e16rmlli-implementation-guide-3588123/77.png)