CORRECTLY MANAGING STORAGE GROUPS 151 If you believe

CORRECTLY MANAGING STORAGE GROUPS 151 If you believe your server is experiencing poor performance because of disk-level fragmentation, you should perform a complete backup of the system and do one of the following: . Run the ESEUTIL utility with the /D option to defragment database files; however, if the disk is badly fragmented, this may only make the problem worse. . Move the EDB and STM files off the disk, and then move them back onto the disk. . Run the Windows Disk Defragmenter. NOTE Running ESEUTIL or moving the ESB and STM files off the disk may be partially successful only if there are other files on the disk or if the disk is badly fragmented. Correctly Managing Storage Groups Exchange 2000 or 2003 storage groups are a collection of mailbox or public stores that share a common set of transaction log files, storage group configuration properties, and an instance of the ESE database engine. The first database in a storage group that is mounted causes a new instance of ESE.DLL to be loaded. NOTE The first database mounted requires about 130MB of virtual memory. Subsequent databases mounted within the storage group require only an additional 25MB of virtual memory plus 10MB of RAM. A good practice is to fill out the first storage group with stores before creating additional storage groups. The default storage group created is called First Storage Group. It automatically contains a mailbox store and a public folder store, though either of these can be deleted if necessary. The following list outlines some of the facts surrounding the creation of additional storage groups: . Each storage group has a unique set of transaction log files. For best performance, each storage group s transaction log files should be on a separate physical hard disk. Even if circular logging is required only for a single store in the storage group, all stores in the storage group must share the same configuration. . The first database mounted in a storage group will consume approximately 130MB of additional virtual memory because it starts a separate instance of the ESE database engine. . If any store in a storage group is undergoing an online backup, online maintenance will be suspended on the other stores in the storage group. . If any database in a storage group suffers a catastrophic failure (disk failure or database corruption), the information store will dismount all stores in the storage group, mark the failed store as bad, and then remount the good stores. This can interfere with normal operations for users whose mailbox or public folder is on a good store in the same storage group. . Only one database can be backed up or restored at a time within a single storage group; this is true even if you select the entire storage group. Only a single store is backed up at a time, but you can back up different databases in different storage groups simultaneously. However, multiple backups or restores can occur across storage groups. If you are going to perform simultaneous restores, you cannot perform more than five minus the number of

Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Discount Web Hosting services

Bookmark the permalink.

Comments are closed.