Re: SCR and Replay Queue length

One more thing,

I have my source mailbox server configured on a SAN with the TX logs on the
D:\ drive and the databases on a seperate SAN slice named e:\.

My target mailbox server has a system drive (c:\) and the second physical
local drive partitioned with D:\ and E:\ for the TX logs and databases. I am
not sure if this is the issue or not.

"Maverick" wrote:

Hi Scott,

The error message that I recieve when I do an updatestoragegroupcopy
-identity 'mailserver\storage group1' -standbymachine backupmailserver:

"Update-StorageGroupCopy : Seeding failed: Database seeding error:
Continuous Replication seeding was provided a database path that does not
identify viable storage"

When I run a getstoragegroupcopystatus on the storage group that is failing
to seed the database, I get:

SummaryCopyStatus : suspended
CopyQueuelength: 18826
Replayqueuelenght: 0
LastLogInspectedLogTime: blank

I have checked to ensure the replication service is running. The other
storage group copies are working fine.

Thanks for your help and great job on the SCR videos on your blog.

Maverick





"Scott Schnoll [MSFT]" wrote:

Well, you don't want replay to get too far behind either. What does
Get-StorageGroupCopyStatus (with the -StandbyMachine option) show for the
storage group? Also, can you verify that the Replication service is running
on the SCR target computer?

When you tried to seed with Update-SGC, what error message did you get?
--
Regards,

Scott Schnoll
Microsoft Corporation
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.


"Maverick" <maverick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:41AE5BA9-3897-4DA2-9481-A6EA4AED93CE@xxxxxxxxxxxxxxxx
Hi all,

I am running into something interesting with SCR. I have enabled it on
about 10 databases without any issues. However, they were mostly small (2
gigs or less). I am trying to seed a 4 gig database and it keeps failing
to
seed when using the suspend-storagegroupcopy/update storagegroupcopy.

So, I followed another way of doing it by dismounting the production
database and then copying the edb file to the target server. I have no
path
conflicts. After the copying is complete, I remount the production
database
and do a resume-storagegroupcopy.

My problem is that the replay queue length stays at about 18000 logs and
keeps growing. I thought that there was a delay of 50 log files and 24
hours
before replaying the logs on the target. When I do a
get-storagegroupcopystatus on the group, it comes back as healthy and the
copy queue length is 0. Should I be worried about the replay queue
length?


.

Relevant Pages

  • Re: SCR and Replay Queue length
    ... Transaction logs which hold the tx logs and the E:\ drive has a folder ... the replay queue length is stuck at around 18000 a day ... Continuous Replication seeding was provided a database path that does not ... When I run a getstoragegroupcopystatus on the storage group that is failing ...
    (microsoft.public.exchange.admin)
  • Re: SCR and Replay Queue length
    ... "My target mailbox server has a system drive and the second physical ... I have my source mailbox server configured on a SAN with the TX logs on ... Continuous Replication seeding was provided a database path that does not ...
    (microsoft.public.exchange.admin)
  • Re: changing the exchange structure
    ... My idea was to create 4 storage groups and create new stores ... the goal being to reduce the size of the database store and ... storage group for each region and move the corresponding mailboxes to the ... and the amount of contention for the logs remains about the same. ...
    (microsoft.public.exchange.design)
  • Re: SCR and Replay Queue length
    ... The partitions are also formatted as NTFS. ... partitioned into D: and E: for logs and database? ... I have my source mailbox server configured on a SAN with the TX logs on ... When I run a getstoragegroupcopystatus on the storage group that is ...
    (microsoft.public.exchange.admin)
  • Re: Dynamic Firewall/IDS System
    ... some thoughts about event handling software. ... > is almost impossible to handle manually just reading logs. ... > This is how we fill our database. ... this is logging, way like acid does with snort logs. ...
    (FreeBSD-Security)