I'm at a loss. There were quite a few of these issues fixed in sp1.

 

What if you just enter the cmdlet name by itself?

 

Get-StoragegroupCopyStatus

 

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net] 
Sent: Tuesday, March 10, 2009 6:31 PM
To: MS-Exchange Admin Issues
Subject: RE: SCR Zero Dataloss

 

Yes. 

 

 

 

  _____  

From: Michael B. Smith [mailto:mich...@theessentialexchange.com] 
Sent: Tuesday, March 10, 2009 5:28 PM
To: MS-Exchange Admin Issues
Subject: RE: SCR Zero Dataloss

 

Are these servers at sp1?

 

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net] 
Sent: Tuesday, March 10, 2009 6:18 PM
To: MS-Exchange Admin Issues
Subject: RE: SCR Zero Dataloss

 

I ran the last one on the source server.  

 

I've tried it locally on both the source and target servers with the same
results.

 

 

  _____  

From: Michael B. Smith [mailto:mich...@theessentialexchange.com] 
Sent: Tuesday, March 10, 2009 5:15 PM
To: MS-Exchange Admin Issues
Subject: RE: SCR Zero Dataloss

 

Which machine are you running this on?

 

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net] 
Sent: Tuesday, March 10, 2009 6:06 PM
To: MS-Exchange Admin Issues
Subject: RE: SCR Zero Dataloss

 

Same result:

 

[PS] C:\>get-storagegroupcopystatus -standbymachine sdcmail-ve1

Get-StorageGroupCopyStatus : Microsoft Exchange Replication service RPC
failed

: Microsoft.Exchange.Rpc.RpcException: Error e0434f4d from
cli_GetCopyStatusEx

   at Microsoft.Exchange.Rpc.Cluster.ReplayRpcClient.GetCopyStatusEx(Guid[]
sgG

uids, RpcStorageGroupCopyStatus[]& sgStatuses)

   at
Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.InternalGetCopyS

tatus(String serverName, Guid[] sgGuids, RpcStorageGroupCopyStatus[]&
sgStatuse

s, Int32 serverVersion)

At line:1 char:27

+ get-storagegroupcopystatus  <<<< -standbymachine sdcmail-ve1

[PS] C:\>

 

Command was run locally on the source server.

 

  _____  

From: Michael B. Smith [mailto:mich...@theessentialexchange.com] 
Sent: Tuesday, March 10, 2009 5:00 PM
To: MS-Exchange Admin Issues
Subject: RE: SCR Zero Dataloss

 

Lose the first parameter:

 

                Get-StoragegroupCopyStatus -standbymachine sdcmail-ve1

 

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net] 
Sent: Tuesday, March 10, 2009 5:49 PM
To: MS-Exchange Admin Issues
Subject: RE: SCR Zero Dataloss

 

I'm trying to get SCR working right now, and it seems to be replicating, but
I get the following error if I try to check the storage group copy status:

 

[PS] C:\>get-storagegroupcopystatus "006mail-ve1\first storage group"
-standbyma

chine sdcmail-ve1

 

Get-StorageGroupCopyStatus : Microsoft Exchange Replication service RPC
failed

: Microsoft.Exchange.Rpc.RpcException: Error e0434f4d from
cli_GetCopyStatusEx

   at Microsoft.Exchange.Rpc.Cluster.ReplayRpcClient.GetCopyStatusEx(Guid[]
sgG

uids, RpcStorageGroupCopyStatus[]& sgStatuses)

   at
Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.InternalGetCopyS

tatus(String serverName, Guid[] sgGuids, RpcStorageGroupCopyStatus[]&
sgStatuse

s, Int32 serverVersion)

At line:1 char:27

+ get-storagegroupcopystatus  <<<< "006mail-ve1\first storage group"
-standbyma

chine sdcmail-ve1

 

The event logs on the target server say it's happily replicating log files.
Am I not using the right command to check the status?  006mail-ve1 is the
source, and sdcmail-ve1.is the target.

 

  _____  

From: Michael B. Smith [mailto:mich...@theessentialexchange.com] 
Sent: Tuesday, March 10, 2009 1:40 PM
To: MS-Exchange Admin Issues
Subject: RE: SCR Zero Dataloss

 

So, let's think about this..

 

You can set the replaytimeout and the truncationlagtimeout to zero, but the
log shipping of SCR is inherently bursty and generally only starts if you
have 50 logs queued. However, after the first 50 are copied, the rest get
copied "in real time", but not applied in real time. There is always a 50
log file delay.

 

You cannot back up an SCR target copy. You must back up the SCR source copy.
The target copy uses circular logging, more or less.

 

When you activate the SCR copy, it attempts to copy any log files that have
not yet been copied (i.e., that were queued for copy).

 

So..I'm not sure what you mean by "zero data loss".

 

From: Liby Philip Mathew [mailto:lmat...@path-solutions.com] 
Sent: Tuesday, March 10, 2009 2:58 AM
To: MS-Exchange Admin Issues
Subject: SCR Zero Dataloss

 

Hi there,

I am in the midst of deploying SCR.

My environment 2 DC, 1 stand alone Mailbox server on Windows 2003 x64 and 1
Edge server on Windows 2003 x64.

How do I configure the SCR target for 0 data loss?

What are the drawbacks when I opt for 0 data loss?

What are the backup options I have?

Right now I have NTBackup dump the database locally to the disk with log
truncation and backup using Symantec 12 to tape.

Appreciate a your inputs and suggestion

Regards

Liby

 

 

  _____  

Disclaimer
[The information contained in this e-mail message and any attached files are
confidential information and intended solely for the use of the individual
or entity to whom they are addressed. This transmission may contain
information that is privileged, confidential or exempt from disclosure under
applicable law. If you have received this e-mail in error, please notify the
sender immediately and delete all copies. If you are not the intended
recipient, any disclosure, copying, distribution, or use of the information
contained herein is STRICTLY PROHIBITED. Path Solutions accepts no
responsibility for any errors, omissions, computer viruses and other
defects.]

 

 

 

****************************************************************************
**********************
Note: 
The information contained in this message may be privileged and confidential
and 
protected from disclosure.  If the reader of this message is not the
intended  
recipient, or an employee or agent responsible for delivering this message
to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
****************************************************************************
**********************

 

 

 

 

****************************************************************************
**********************
Note: 
The information contained in this message may be privileged and confidential
and 
protected from disclosure.  If the reader of this message is not the
intended  
recipient, or an employee or agent responsible for delivering this message
to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
****************************************************************************
**********************

 

 

 

 

****************************************************************************
**********************
Note: 
The information contained in this message may be privileged and confidential
and 
protected from disclosure.  If the reader of this message is not the
intended  
recipient, or an employee or agent responsible for delivering this message
to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
****************************************************************************
**********************

 

 

 

 

****************************************************************************
**********************
Note: 
The information contained in this message may be privileged and confidential
and 
protected from disclosure.  If the reader of this message is not the
intended  
recipient, or an employee or agent responsible for delivering this message
to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
****************************************************************************
**********************

 

 


~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~

Reply via email to