How long isinteg exchange 2003




















We'll send a magic link to your inbox. Email Address. All Sign in options. Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox. Newsletter Topics Select minimum 1 topic. Team Collaboration. Sean Wright October 28, 0 Comments. Mike Walker Posted November 1, 0 Comments. Sean Wright Posted November 2, 0 Comments.

Mike Walker Posted November 2, 0 Comments. Sean Wright Posted November 12, 0 Comments. Good outcome as we had a new server on order and is now up and running. Register or Login. Welcome back! Reset Your Password We'll send an email with a link to reset your password. Stay ahead! Get the latest news, expert insights and market research, tailored to your interests. Sign in with email Enter the email address associated with your account. You auth link is expired or incorrect, please try again.

URL Name. Database Integrity Check. Product Area. Primary Product. Arcserve Backup. Content Article Body. System Information. KB Status. KB Published Externally. Properties Article Created Date. Created By. Last Modified By. All Arcserve Backup.

Follow Following Unfollow. Microsoft Exchange Server Best Answer. Microsoft Exchange expert. Robin Matthews wrote: Thanks I did think it would be a "how long is a piece of string" type of question. No need to install Exchange on another server. View this "Best Answer" in the replies below ». Popular Topics in Microsoft Exchange. Which of the following retains the information it's storing when the system power is turned off?

Submit ». Pure Capsaicin. Gary D Williams This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.

Cheers Sorry but the answer is "as long as it takes". It's impossible to say because it'll have to scan the whole db and that could take minutes, hours or yes, days.

As your database close to GB, I would allocate close to hours for the downtime. That's in case everything goes good. In case of issues I would suggest allocating additional hours to revert things back, just in case. That said it's very much depends on the amount of errors in the DB, as well as the speed of the machine.



0コメント

  • 1000 / 1000