Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
adding disks to a raided exchange 2000 cluster
- Thread starter patrjr
- Start date
Im pretty sure that when you create or break a raid, you lose the data. So the choices would be to do this via backupa dn build a larger raid or to make a new larger raid on the server and then move the DB there and then remove the first raid.
It's really more of a cluster question than an exchange question.
1. Cluster only supports basic disks.
2. Cluster keeps track of the signature for each disk resource.
Given 1 and 2 above, I would:
1. Create a new RAID set.
2. Create a new disk resource from the new RAID set.
3. Add the new disk resource to the MSExchangeSA dependencies.
4. Use ESM to move the database to the new disk.
5. If necessary, move the tracking logs and gatherer logs.
6. Remove the old disk from the MSExchangeSA dependencies.
7. Take the old disk off line.
8. Remove the old disk's disk resource.
9. Remove the old disks.
If you want to use the old members as part of the new disk, it gets quite a bit more complicated. Basically, you record the drive letter and signature of the old disk, back up the data, destroy the old set, create the new set, swap the signatures and drive letters, and restore the data. You'll probably want to bring in a consultant if you decide to go this route.
John
MOSMWNMTK
1. Cluster only supports basic disks.
2. Cluster keeps track of the signature for each disk resource.
Given 1 and 2 above, I would:
1. Create a new RAID set.
2. Create a new disk resource from the new RAID set.
3. Add the new disk resource to the MSExchangeSA dependencies.
4. Use ESM to move the database to the new disk.
5. If necessary, move the tracking logs and gatherer logs.
6. Remove the old disk from the MSExchangeSA dependencies.
7. Take the old disk off line.
8. Remove the old disk's disk resource.
9. Remove the old disks.
If you want to use the old members as part of the new disk, it gets quite a bit more complicated. Basically, you record the drive letter and signature of the old disk, back up the data, destroy the old set, create the new set, swap the signatures and drive letters, and restore the data. You'll probably want to bring in a consultant if you decide to go this route.
John
MOSMWNMTK
There's no optimizer in E2K. You move the database through Exchange System Manager.
On cluster, you have to go through the extra step of creating a disk resource and adding it to the dependency of SA. Dependencies control the order that resource come online and go offline. If you don't add the dependency, the drive could go offline before the information store does. This would cause data loss/corruption.
Cluster tracks the disk signature of disk resources. If you try to move things around behind the scenes, you'll have to make sure you patch up the signatures or the disk resource won't come online.
John
MOSMWNMTK
On cluster, you have to go through the extra step of creating a disk resource and adding it to the dependency of SA. Dependencies control the order that resource come online and go offline. If you don't add the dependency, the drive could go offline before the information store does. This would cause data loss/corruption.
Cluster tracks the disk signature of disk resources. If you try to move things around behind the scenes, you'll have to make sure you patch up the signatures or the disk resource won't come online.
John
MOSMWNMTK
- Status
Similar threads
- Locked
- Question
- Locked
- Helpful tip