G
gus
Guest
My advice is: put everything except for after-image extents onto one big filesystem that is striped and mirrored Feel free to use variable-size extents. Always use only type ii data areas. For after-image extents, best practice is to put them on a separate filesystem from the data and before-image extents. About 8 variable size extents is a good practice rule of thumb. Never use less than 4 ai extents. Always use the archiver daemon to copy ai extents off the system. You can estimate the space required for after-imaging by looking at the number of checkpoints over some period of time (say a week) and multiplying by the before-image cluster size. In the same time period you will generate that much after-image data. Note that certain operation like tablemoves, month-end, quarter-end or year-end processing can generate much more after-image data that average and you should take that into account. YMMV, transportation, meals, and accomodations not included.
Continue reading...
Continue reading...