Couldn’t open backup file handle while performing Exchange DB seed via Powershell

The error above is the outcome of running Udate-MailboxDatabaseCopyStatus -Identity DB_NAME -DeleteExistingFiles and the DB status went to Failed and Suspended. The reason is that the backup was kicked off and the handle for the DB was no longer available.

You could check the status of the backup on the DB by running Get-MailboxDatabaseCopyStatus -Identity DB_NAME | fl *backup*

Two ways to get over this, either to wait for the backup to finish or to reboot the server and stop the backup and that should fix the issue, the seeding process needs to start from scratch.

Exchange 2010, Powershell, seeding

This entry was posted on 4 November, 2013, 12:59 pm and is filed under DAG, Exchange 2010, Poweshell. You can follow any responses to this entry through RSS 2.0. You can leave a response, or trackback from your own site.

Tweets

@Steve_Sherry I can't believe you had the whole cenima to yourself 😳 4 weeks ago

@seeedstudio I am doing an internal project at MSFT using Wio Terminal, but I am having issues calling Put method o… twitter.com/i/web/status/1… 5 months ago

@jaffathecake Stepping away from the problem sometimes brings a new prospective 1 year ago

In our ongoing work to help DoD meet compliance needs and accelerate the path to cloud adoption, we’ve recently rel… twitter.com/i/web/status/1… 1 year ago

Only 4 weeks left to join our Microsoft Retail Innovation Club! Don't miss your chance to watch these amazing pre… twitter.com/i/web/status/1… 1 year ago

Follow @samiko_uk

#1 by AneeshS on 18 March, 2018 - 8:25 pm

The issue could also come up in case you have tried to rename the Database (scenarios where Database back in not in question). Refer Blog – https://social.technet.microsoft.com/Forums/office/en-US/b96c78f0-a0b3-4656-be21-80eb3d8001ac/unable-to-add-exchange-mailbox-database-passive-copy?forum=exchange2010&prof=required

SysCloud.dev