Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Wed, 3 May 2006 03:56:01 -0700,    group: microsoft.public.exchange.clustering        back       


Move EVS to new disks   
I've successfully moved most of my EVS to new disks. I now have two remaining 
problems:

1 - The Search service still writes to the old disks, and I can't find where 
to change this. Even hacked the Registry and it still went back to M:....

2 - Once I've done this, I need to remove the SA dependency on the old 
disks. I've tried this before, but it insists on deleting the SA itself and 
all its dependent resources. Anyone seen a definitive guide to removing disks 
from an EVS?

Thanks
date: Wed, 3 May 2006 03:56:01 -0700   author:   Simon

Re: Move EVS to new disks   
I have used these steps many times.  I partially automated the process with 
a batch file as well.

  1.. Move the Exchange Group to Active Node.
  2.. Offline System Attendant in Exchange Cluster Group.
  3.. Run Following Script on the active node.  syntax:  RebuildMSsearch 
[virtual server name]


RebuildMSsearch.bat



echo delete MS Search Resource

cluster . res "Exchange MS Search Instance (%1)" /DELETE



echo delete Search Registry Keys

reg delete HKLM\Software\Microsoft\search\1.0\applications\ExchangeServer_%1 
/f

reg delete HKLM\Software\Microsoft\search\1.0\catalognames\ExchangeServer_%1 
/f

reg delete HKLM\Software\Microsoft\search\1.0\gather\ExchangeServer_%1 /f

reg delete "HKLM\Software\Microsoft\search\1.0\gathering 
manager\applications\ExchangeServer_%1" /f

reg delete HKLM\Software\Microsoft\search\1.0\indexer\ExchangeServer_%1 /f

reg delete HKLM\Software\Microsoft\Search\1.0\Databases\ExchangeServer_%1 /f



echo restart ms search service

net stop mssearch

net start mssearch



    4.  Delete System Attendant Resource from Cluster Admin GUI.

    5.  Confirm you have access to Domain Controller.



Using ADSIEDIT.MSC, redirect the path to New LUN.

Configuration 
[DC]\CN=Configuration,DC=domainname,DC=com\CN=Services\CN=Microsoft 
Exchange\CN=Exchange Domain name\CN=Administrator 
Groups\CN=Servers\CN=clustername.



Right Click on CN=clustername; "Properties".



Edit "MSExchDataPath"



Data Path should point to new first database drive

 6.  Created New SA w/ out picking Old LUN as Dependencies LUN.  Use the 
same virtual server name.

 7.  Online SA, Online MS Search.

 8.  Online Exchange Group.

 9.  Move Exchange Cluster Group from Node A to Node B.

10. Move Exchange Cluster Group back to Active Node.









"Simon"  wrote in message 
news:A1D7A915-2485-4B88-ADB0-B256A0511B14@microsoft.com...
> I've successfully moved most of my EVS to new disks. I now have two 
> remaining
> problems:
>
> 1 - The Search service still writes to the old disks, and I can't find 
> where
> to change this. Even hacked the Registry and it still went back to M:....
>
> 2 - Once I've done this, I need to remove the SA dependency on the old
> disks. I've tried this before, but it insists on deleting the SA itself 
> and
> all its dependent resources. Anyone seen a definitive guide to removing 
> disks
> from an EVS?
>
> Thanks
>
date: Wed, 3 May 2006 06:04:59 -0700   author:   John Fullbright [MVP]

Re: Move EVS to new disks   
Hi John,

I'll give this a go at the weekend. The bit I didn't know about was ADSIEdit 
- I'd tracked down the registry entries, but without the final bit it clearly 
won't work.

Thanks

Simon

"John Fullbright [MVP]" wrote:

> I have used these steps many times.  I partially automated the process with 
> a batch file as well.
> 
>   1.. Move the Exchange Group to Active Node.
>   2.. Offline System Attendant in Exchange Cluster Group.
>   3.. Run Following Script on the active node.  syntax:  RebuildMSsearch 
> [virtual server name]
> 
> 
> RebuildMSsearch.bat
> 
> 
> 
> echo delete MS Search Resource
> 
> cluster . res "Exchange MS Search Instance (%1)" /DELETE
> 
> 
> 
> echo delete Search Registry Keys
> 
> reg delete HKLM\Software\Microsoft\search\1.0\applications\ExchangeServer_%1 
> /f
> 
> reg delete HKLM\Software\Microsoft\search\1.0\catalognames\ExchangeServer_%1 
> /f
> 
> reg delete HKLM\Software\Microsoft\search\1.0\gather\ExchangeServer_%1 /f
> 
> reg delete "HKLM\Software\Microsoft\search\1.0\gathering 
> manager\applications\ExchangeServer_%1" /f
> 
> reg delete HKLM\Software\Microsoft\search\1.0\indexer\ExchangeServer_%1 /f
> 
> reg delete HKLM\Software\Microsoft\Search\1.0\Databases\ExchangeServer_%1 /f
> 
> 
> 
> echo restart ms search service
> 
> net stop mssearch
> 
> net start mssearch
> 
> 
> 
>     4.  Delete System Attendant Resource from Cluster Admin GUI.
> 
>     5.  Confirm you have access to Domain Controller.
> 
> 
> 
> Using ADSIEDIT.MSC, redirect the path to New LUN.
> 
> Configuration 
> [DC]\CN=Configuration,DC=domainname,DC=com\CN=Services\CN=Microsoft 
> Exchange\CN=Exchange Domain name\CN=Administrator 
> Groups\CN=Servers\CN=clustername.
> 
> 
> 
> Right Click on CN=clustername; "Properties".
> 
> 
> 
> Edit "MSExchDataPath"
> 
> 
> 
> Data Path should point to new first database drive
> 
>  6.  Created New SA w/ out picking Old LUN as Dependencies LUN.  Use the 
> same virtual server name.
> 
>  7.  Online SA, Online MS Search.
> 
>  8.  Online Exchange Group.
> 
>  9.  Move Exchange Cluster Group from Node A to Node B.
> 
> 10. Move Exchange Cluster Group back to Active Node.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> "Simon"  wrote in message 
> news:A1D7A915-2485-4B88-ADB0-B256A0511B14@microsoft.com...
> > I've successfully moved most of my EVS to new disks. I now have two 
> > remaining
> > problems:
> >
> > 1 - The Search service still writes to the old disks, and I can't find 
> > where
> > to change this. Even hacked the Registry and it still went back to M:....
> >
> > 2 - Once I've done this, I need to remove the SA dependency on the old
> > disks. I've tried this before, but it insists on deleting the SA itself 
> > and
> > all its dependent resources. Anyone seen a definitive guide to removing 
> > disks
> > from an EVS?
> >
> > Thanks
> > 
> 
> 
>
date: Wed, 3 May 2006 06:29:15 -0700   author:   Simon

Re: Move EVS to new disks   
When you recreate the SA, the MSSearch Service instance is recreated in the 
path defined by the msExchDataPath attribute of the virtual server instance. 
You have modify the attribute to point to the location that you want the 
folder containing the gatherer logs to created prior to recreating the SA.

ADSIEdit.msc is a resource kit tool you can use to change the attribute.


"Simon"  wrote in message 
news:9DBD477E-F208-47AA-A5B2-0C38B01BDBCA@microsoft.com...
> Hi John,
>
> I'll give this a go at the weekend. The bit I didn't know about was 
> ADSIEdit
> - I'd tracked down the registry entries, but without the final bit it 
> clearly
> won't work.
>
> Thanks
>
> Simon
>
> "John Fullbright [MVP]" wrote:
>
>> I have used these steps many times.  I partially automated the process 
>> with
>> a batch file as well.
>>
>>   1.. Move the Exchange Group to Active Node.
>>   2.. Offline System Attendant in Exchange Cluster Group.
>>   3.. Run Following Script on the active node.  syntax:  RebuildMSsearch
>> [virtual server name]
>>
>>
>> RebuildMSsearch.bat
>>
>>
>>
>> echo delete MS Search Resource
>>
>> cluster . res "Exchange MS Search Instance (%1)" /DELETE
>>
>>
>>
>> echo delete Search Registry Keys
>>
>> reg delete 
>> HKLM\Software\Microsoft\search\1.0\applications\ExchangeServer_%1
>> /f
>>
>> reg delete 
>> HKLM\Software\Microsoft\search\1.0\catalognames\ExchangeServer_%1
>> /f
>>
>> reg delete HKLM\Software\Microsoft\search\1.0\gather\ExchangeServer_%1 /f
>>
>> reg delete "HKLM\Software\Microsoft\search\1.0\gathering
>> manager\applications\ExchangeServer_%1" /f
>>
>> reg delete HKLM\Software\Microsoft\search\1.0\indexer\ExchangeServer_%1 
>> /f
>>
>> reg delete HKLM\Software\Microsoft\Search\1.0\Databases\ExchangeServer_%1 
>> /f
>>
>>
>>
>> echo restart ms search service
>>
>> net stop mssearch
>>
>> net start mssearch
>>
>>
>>
>>     4.  Delete System Attendant Resource from Cluster Admin GUI.
>>
>>     5.  Confirm you have access to Domain Controller.
>>
>>
>>
>> Using ADSIEDIT.MSC, redirect the path to New LUN.
>>
>> Configuration
>> [DC]\CN=Configuration,DC=domainname,DC=com\CN=Services\CN=Microsoft
>> Exchange\CN=Exchange Domain name\CN=Administrator
>> Groups\CN=Servers\CN=clustername.
>>
>>
>>
>> Right Click on CN=clustername; "Properties".
>>
>>
>>
>> Edit "MSExchDataPath"
>>
>>
>>
>> Data Path should point to new first database drive
>>
>>  6.  Created New SA w/ out picking Old LUN as Dependencies LUN.  Use the
>> same virtual server name.
>>
>>  7.  Online SA, Online MS Search.
>>
>>  8.  Online Exchange Group.
>>
>>  9.  Move Exchange Cluster Group from Node A to Node B.
>>
>> 10. Move Exchange Cluster Group back to Active Node.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> "Simon"  wrote in message
>> news:A1D7A915-2485-4B88-ADB0-B256A0511B14@microsoft.com...
>> > I've successfully moved most of my EVS to new disks. I now have two
>> > remaining
>> > problems:
>> >
>> > 1 - The Search service still writes to the old disks, and I can't find
>> > where
>> > to change this. Even hacked the Registry and it still went back to 
>> > M:....
>> >
>> > 2 - Once I've done this, I need to remove the SA dependency on the old
>> > disks. I've tried this before, but it insists on deleting the SA itself
>> > and
>> > all its dependent resources. Anyone seen a definitive guide to removing
>> > disks
>> > from an EVS?
>> >
>> > Thanks
>> >
>>
>>
>>
date: Wed, 3 May 2006 09:38:26 -0700   author:   John Fullbright [MVP]

Re: Move EVS to new disks   
Hi John

Did the steps at the weekend.. 

Something in the MTA (I think) still looking for M:\ I couldn't find 
anything in ESM, ADSIEdit or local/cluster registry. So I took the course of 
least resistance and created an M: drive on the SAN. 

Thanks for all your tips - I'd never have thought of ADSIedit.

Simon

"John Fullbright [MVP]" wrote:

> When you recreate the SA, the MSSearch Service instance is recreated in the 
> path defined by the msExchDataPath attribute of the virtual server instance. 
> You have modify the attribute to point to the location that you want the 
> folder containing the gatherer logs to created prior to recreating the SA.
> 
> ADSIEdit.msc is a resource kit tool you can use to change the attribute.
> 
> 
> "Simon"  wrote in message 
> news:9DBD477E-F208-47AA-A5B2-0C38B01BDBCA@microsoft.com...
> > Hi John,
> >
> > I'll give this a go at the weekend. The bit I didn't know about was 
> > ADSIEdit
> > - I'd tracked down the registry entries, but without the final bit it 
> > clearly
> > won't work.
> >
> > Thanks
> >
> > Simon
> >
> > "John Fullbright [MVP]" wrote:
> >
> >> I have used these steps many times.  I partially automated the process 
> >> with
> >> a batch file as well.
> >>
> >>   1.. Move the Exchange Group to Active Node.
> >>   2.. Offline System Attendant in Exchange Cluster Group.
> >>   3.. Run Following Script on the active node.  syntax:  RebuildMSsearch
> >> [virtual server name]
> >>
> >>
> >> RebuildMSsearch.bat
> >>
> >>
> >>
> >> echo delete MS Search Resource
> >>
> >> cluster . res "Exchange MS Search Instance (%1)" /DELETE
> >>
> >>
> >>
> >> echo delete Search Registry Keys
> >>
> >> reg delete 
> >> HKLM\Software\Microsoft\search\1.0\applications\ExchangeServer_%1
> >> /f
> >>
> >> reg delete 
> >> HKLM\Software\Microsoft\search\1.0\catalognames\ExchangeServer_%1
> >> /f
> >>
> >> reg delete HKLM\Software\Microsoft\search\1.0\gather\ExchangeServer_%1 /f
> >>
> >> reg delete "HKLM\Software\Microsoft\search\1.0\gathering
> >> manager\applications\ExchangeServer_%1" /f
> >>
> >> reg delete HKLM\Software\Microsoft\search\1.0\indexer\ExchangeServer_%1 
> >> /f
> >>
> >> reg delete HKLM\Software\Microsoft\Search\1.0\Databases\ExchangeServer_%1 
> >> /f
> >>
> >>
> >>
> >> echo restart ms search service
> >>
> >> net stop mssearch
> >>
> >> net start mssearch
> >>
> >>
> >>
> >>     4.  Delete System Attendant Resource from Cluster Admin GUI.
> >>
> >>     5.  Confirm you have access to Domain Controller.
> >>
> >>
> >>
> >> Using ADSIEDIT.MSC, redirect the path to New LUN.
> >>
> >> Configuration
> >> [DC]\CN=Configuration,DC=domainname,DC=com\CN=Services\CN=Microsoft
> >> Exchange\CN=Exchange Domain name\CN=Administrator
> >> Groups\CN=Servers\CN=clustername.
> >>
> >>
> >>
> >> Right Click on CN=clustername; "Properties".
> >>
> >>
> >>
> >> Edit "MSExchDataPath"
> >>
> >>
> >>
> >> Data Path should point to new first database drive
> >>
> >>  6.  Created New SA w/ out picking Old LUN as Dependencies LUN.  Use the
> >> same virtual server name.
> >>
> >>  7.  Online SA, Online MS Search.
> >>
> >>  8.  Online Exchange Group.
> >>
> >>  9.  Move Exchange Cluster Group from Node A to Node B.
> >>
> >> 10. Move Exchange Cluster Group back to Active Node.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> "Simon"  wrote in message
> >> news:A1D7A915-2485-4B88-ADB0-B256A0511B14@microsoft.com...
> >> > I've successfully moved most of my EVS to new disks. I now have two
> >> > remaining
> >> > problems:
> >> >
> >> > 1 - The Search service still writes to the old disks, and I can't find
> >> > where
> >> > to change this. Even hacked the Registry and it still went back to 
> >> > M:....
> >> >
> >> > 2 - Once I've done this, I need to remove the SA dependency on the old
> >> > disks. I've tried this before, but it insists on deleting the SA itself
> >> > and
> >> > all its dependent resources. Anyone seen a definitive guide to removing
> >> > disks
> >> > from an EVS?
> >> >
> >> > Thanks
> >> >
> >>
> >>
> >> 
> 
> 
>
date: Mon, 15 May 2006 02:46:02 -0700   author:   Simon

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us