Solved

Exchange 2007 fails to reseed

Posted on 2010-08-28
4
499 Views
Last Modified: 2012-05-10
Hello,

I am unable to reseed a storage group. I did an “update-storagegroupcopy” and this game me the erorr that it failed because a backup is in progress. I checked and there is no backup taking place.
I came accross an article from an individual that had the same problem and he resolved it by restrting the "MSExchangeIS".
Question is on a CCR, if the Information Store is restarted will this cause the cluster to failover?

Tacobell2000
0
Comment
Question by:Tacobell2000
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 
LVL 10

Assisted Solution

by:dhruvarajp
dhruvarajp earned 150 total points
ID: 33549967
you might want to suspend the storagegroup copy first and try reseed,
http://technet.microsoft.com/en-us/library/aa998853(EXCHG.80).aspx 

if it still fails

stop
http://technet.microsoft.com/en-us/library/aa996336(EXCHG.80).aspx

and start
http://technet.microsoft.com/en-us/library/aa996355(EXCHG.80).aspx 

the clustered mailbox server

Thank you
Dhruv
0
 
LVL 32

Accepted Solution

by:
endital1097 earned 200 total points
ID: 33549989
you can just dismount the one database that won't update, don't need to stop the entire IS
0
 
LVL 3

Assisted Solution

by:Cyrus9
Cyrus9 earned 150 total points
ID: 33557392
Well instead of restarting the MSexchangeIS service, what you can actually do is take "Exchange Information Store Instance" offline in the Cluster Administrator (Windows 2003 servers) or in the Failover Cluster Management (Winodws 2008), and then bring it online.
"Exchange Information Store Instance" offline and then bringing it online is similar to restarting the MSexchangeIS service and this should not cause the cluster to fail over.
Microsoft never recommends restarting the MSexchangeIS or the MSexchangeSA service using "Services.msc", it is recommended to do it from the Cluster Administrator (Windows 2003 servers) or in the Failover Cluster Management (Winodws 2008).
0
 

Author Closing Comment

by:Tacobell2000
ID: 33560141
I followed enditals instructions and this did not do it. I do not think the IS is the problem since all the other databases are working properly.
The problem I think is that this specific database is just too huge....over 500Gigs and Microsoft Best practices is between 50-200 Gigs per database.
So I'll wait for additional space and move the mailboxes over to new SG and then see if that fixes the problem.

thanks for your help,

Tacobell2000
0

Featured Post

Salesforce Has Never Been Easier

Improve and reinforce salesforce training & adoption using WalkMe's digital adoption platform. Start saving on costly employee training by creating fast intuitive Walk-Thrus for Salesforce. Claim your Free Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question