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: Tue, 13 May 2008 13:19:04 -0700,    group: microsoft.public.exchange.admin        back       


Original CCR storage group folders shared - Why?   
In a lab I setup a 2007 SP1 CCR cluster on WS2008, which went really well. 
However, I wanted to move the two storage groups and databases to another 
drive. I followed the MS procedures for moving them in a CCR cluster and that 
went fine as well.

However, as I was going to delete the old storage group folders on the C 
drive, I noticed on the active and passive nodes that they were shared out 
with some very long GUID looking share name. 

This is not the file share witness, which I have configured on my CAS/HTS 
server. I blew away one storage group folder and share on my active node and 
Exchange doesn't seem to be complaing.

No where in the storage group and database moving instructions for a CCR 
cluster did it say I needed to share out the new folders. 

Why were the original folders shared with a very long and complex share 
name, and can I safely blow them away once they are properly relocated to 
another drive?
date: Tue, 13 May 2008 13:19:04 -0700   author:   IT Guy

Re: Original CCR storage group folders shared - Why?   
Cluster Continuous Replication ->Transaction Log Replication and Replay
http://technet.microsoft.com/en-us/library/bb124521.aspx

In a CCR environment, the transaction log file folder on the active node is 
shared using a standard Windows file share. The object globally unique 
identifier (GUID) for the storage group is used for the share name, and a 
dollar sign ($) is added to the end of the share. The Microsoft Exchange 
Replication service on the passive node connects to the share on the active 
node and copies, or pulls, the log files using the Server Message Block 
(SMB) protocol. The passive node then verifies the log file and replays it 
into the copy of the database on the passive node.

-- 
Bharat Suneja
Microsoft Corporation
blog: exchangepedia.com/blog

This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
----------------------------

"IT Guy"  wrote in message 
news:DCAFE2B9-5B9D-4E9D-A980-4950303BF384@microsoft.com...
> In a lab I setup a 2007 SP1 CCR cluster on WS2008, which went really well.
> However, I wanted to move the two storage groups and databases to another
> drive. I followed the MS procedures for moving them in a CCR cluster and 
> that
> went fine as well.
>
> However, as I was going to delete the old storage group folders on the C
> drive, I noticed on the active and passive nodes that they were shared out
> with some very long GUID looking share name.
>
> This is not the file share witness, which I have configured on my CAS/HTS
> server. I blew away one storage group folder and share on my active node 
> and
> Exchange doesn't seem to be complaing.
>
> No where in the storage group and database moving instructions for a CCR
> cluster did it say I needed to share out the new folders.
>
> Why were the original folders shared with a very long and complex share
> name, and can I safely blow them away once they are properly relocated to
> another drive?
date: Tue, 13 May 2008 14:24:15 -0700   author:   Bharat Suneja [MSFT]

Re: Original CCR storage group folders shared - Why?   
Also note, you don't need to manually share the folders if you move 
transaction logs.

-- 
Bharat Suneja
Microsoft Corporation
blog: exchangepedia.com/blog

This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
----------------------------


"Bharat Suneja [MSFT]"  wrote in message 
news:%23uflz%23TtIHA.2208@TK2MSFTNGP04.phx.gbl...
> Cluster Continuous Replication ->Transaction Log Replication and Replay
> http://technet.microsoft.com/en-us/library/bb124521.aspx
>
> In a CCR environment, the transaction log file folder on the active node 
> is shared using a standard Windows file share. The object globally unique 
> identifier (GUID) for the storage group is used for the share name, and a 
> dollar sign ($) is added to the end of the share. The Microsoft Exchange 
> Replication service on the passive node connects to the share on the 
> active node and copies, or pulls, the log files using the Server Message 
> Block (SMB) protocol. The passive node then verifies the log file and 
> replays it into the copy of the database on the passive node.
>
> -- 
> Bharat Suneja
> Microsoft Corporation
> blog: exchangepedia.com/blog
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> ----------------------------
>
> "IT Guy"  wrote in message 
> news:DCAFE2B9-5B9D-4E9D-A980-4950303BF384@microsoft.com...
>> In a lab I setup a 2007 SP1 CCR cluster on WS2008, which went really 
>> well.
>> However, I wanted to move the two storage groups and databases to another
>> drive. I followed the MS procedures for moving them in a CCR cluster and 
>> that
>> went fine as well.
>>
>> However, as I was going to delete the old storage group folders on the C
>> drive, I noticed on the active and passive nodes that they were shared 
>> out
>> with some very long GUID looking share name.
>>
>> This is not the file share witness, which I have configured on my CAS/HTS
>> server. I blew away one storage group folder and share on my active node 
>> and
>> Exchange doesn't seem to be complaing.
>>
>> No where in the storage group and database moving instructions for a CCR
>> cluster did it say I needed to share out the new folders.
>>
>> Why were the original folders shared with a very long and complex share
>> name, and can I safely blow them away once they are properly relocated to
>> another drive?
>
date: Tue, 13 May 2008 14:29:19 -0700   author:   Bharat Suneja [MSFT]

Re: Original CCR storage group folders shared - Why?   
Thanks, that makes sense. I did just realize my new log directories were 
shared out with a GUID. So I'll safely delete the first shares and not wonder 
why my database only folders are not shared. 

"Bharat Suneja [MSFT]" wrote:

> Cluster Continuous Replication ->Transaction Log Replication and Replay
> http://technet.microsoft.com/en-us/library/bb124521.aspx
> 
> In a CCR environment, the transaction log file folder on the active node is 
> shared using a standard Windows file share. The object globally unique 
> identifier (GUID) for the storage group is used for the share name, and a 
> dollar sign ($) is added to the end of the share. The Microsoft Exchange 
> Replication service on the passive node connects to the share on the active 
> node and copies, or pulls, the log files using the Server Message Block 
> (SMB) protocol. The passive node then verifies the log file and replays it 
> into the copy of the database on the passive node.
> 
> -- 
> Bharat Suneja
> Microsoft Corporation
> blog: exchangepedia.com/blog
> 
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> ----------------------------
> 
> "IT Guy"  wrote in message 
> news:DCAFE2B9-5B9D-4E9D-A980-4950303BF384@microsoft.com...
> > In a lab I setup a 2007 SP1 CCR cluster on WS2008, which went really well.
> > However, I wanted to move the two storage groups and databases to another
> > drive. I followed the MS procedures for moving them in a CCR cluster and 
> > that
> > went fine as well.
> >
> > However, as I was going to delete the old storage group folders on the C
> > drive, I noticed on the active and passive nodes that they were shared out
> > with some very long GUID looking share name.
> >
> > This is not the file share witness, which I have configured on my CAS/HTS
> > server. I blew away one storage group folder and share on my active node 
> > and
> > Exchange doesn't seem to be complaing.
> >
> > No where in the storage group and database moving instructions for a CCR
> > cluster did it say I needed to share out the new folders.
> >
> > Why were the original folders shared with a very long and complex share
> > name, and can I safely blow them away once they are properly relocated to
> > another drive? 
> 
>
date: Tue, 13 May 2008 14:31:01 -0700   author:   IT Guy

Re: Original CCR storage group folders shared - Why?   
Yup, I saw that Exchange created the GUID and shared them for me. 

"Bharat Suneja [MSFT]" wrote:

> Also note, you don't need to manually share the folders if you move 
> transaction logs.
> 
> -- 
> Bharat Suneja
> Microsoft Corporation
> blog: exchangepedia.com/blog
> 
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> ----------------------------
> 
> 
> "Bharat Suneja [MSFT]"  wrote in message 
> news:%23uflz%23TtIHA.2208@TK2MSFTNGP04.phx.gbl...
> > Cluster Continuous Replication ->Transaction Log Replication and Replay
> > http://technet.microsoft.com/en-us/library/bb124521.aspx
> >
> > In a CCR environment, the transaction log file folder on the active node 
> > is shared using a standard Windows file share. The object globally unique 
> > identifier (GUID) for the storage group is used for the share name, and a 
> > dollar sign ($) is added to the end of the share. The Microsoft Exchange 
> > Replication service on the passive node connects to the share on the 
> > active node and copies, or pulls, the log files using the Server Message 
> > Block (SMB) protocol. The passive node then verifies the log file and 
> > replays it into the copy of the database on the passive node.
> >
> > -- 
> > Bharat Suneja
> > Microsoft Corporation
> > blog: exchangepedia.com/blog
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights. Please do not send email directly to this alias. This alias is for
> > newsgroup purposes only.
> > ----------------------------
> >
> > "IT Guy"  wrote in message 
> > news:DCAFE2B9-5B9D-4E9D-A980-4950303BF384@microsoft.com...
> >> In a lab I setup a 2007 SP1 CCR cluster on WS2008, which went really 
> >> well.
> >> However, I wanted to move the two storage groups and databases to another
> >> drive. I followed the MS procedures for moving them in a CCR cluster and 
> >> that
> >> went fine as well.
> >>
> >> However, as I was going to delete the old storage group folders on the C
> >> drive, I noticed on the active and passive nodes that they were shared 
> >> out
> >> with some very long GUID looking share name.
> >>
> >> This is not the file share witness, which I have configured on my CAS/HTS
> >> server. I blew away one storage group folder and share on my active node 
> >> and
> >> Exchange doesn't seem to be complaing.
> >>
> >> No where in the storage group and database moving instructions for a CCR
> >> cluster did it say I needed to share out the new folders.
> >>
> >> Why were the original folders shared with a very long and complex share
> >> name, and can I safely blow them away once they are properly relocated to
> >> another drive?
> > 
> 
>
date: Tue, 13 May 2008 14:35:01 -0700   author:   IT Guy

Google
 
Web ureader.com


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