How to Use New-PublicFolderDatabaseRepairRequest Cmdlet To Detect & Repair Public Folder Database? Get Solution
Summary: Are you facing problem to repair the Exchange public folder database? If yes, then this write-up is only for you. Here we will guide users to detect and repair the public folder via PowerShell New-PublicFolderDatabaseRepairRequest command.
Exchange Public folder is used widely in the IT organizations and other industry verticals. Same as mailbox database the Public folder can also get corrupted due to various reasons such as: sudden power failure, hardware or software failure, hard disk bad sector error, virus or malware attack that corrupted the Exchange database file (private and public), etc… These are some of the reasons because of which corruption occurs in public folder database.
When this issue arises users are unable to access the Exchange data and after checking the Exchange Management Console they will find that the database isn’t mounted. Users can use the PowerShell New-PublicFolderDatabaseRepairRequest cmdlet to detect & repair the replication issue in the EDB public folder.
Before running this cmdlet there are certain things that you should know. Users cannot stop the repair request unless they dismount the public folder database. You can’t access the public folder that is currently being repaired.
How to Execute New-PublicFolderDatabaseRepairRequest Command In Exchange Server 2010?
Before running this PowerShell cmdlet user have to assign permission. After that you can use the command.
-CorruptionType <publicfolderdatabasecorruptiontype> </publicfolderdatabasecorruptiontype>
[-DetectOnly ] [-DomainController ]
Command to Detect & Fix Public Folder Database
New-PublicFolderDatabaseRepairRequest -Database “PublicFolderDB1” -CorruptionType ReplState
This command detect and repair the replication issue in the Exchange public foler database.
There are various parameters given below that users can use with this PowerShell cmdlet.
While running the new- public folder database repair request command it is necessary to use this parameter in it. This help users to specify the type of corruption which they want to detect & repair.
This parameter specifies which public folder DB that users want to repair. They can use any values (Name, Distinguished name, GUID) which uniquely identify the database.
This switch specifies whether to hide or show the confirmation prompt.
This switch is used in the command to report the error but not to fix it and you need not to specify any value with the cmdlet.
All you need to add this -DetectOnly in the New-PublicFolderDatabaseRepairRequest command.
Users can use this parameter to specify the domain controller which is used by the command to read or write data from the Active Directory. You can identify the DC (Domain Controller) by it’s FQDN.
This parameter stimulates the action of the cmdlet. Users can use this switch to view the changes without applying the changes. You does not need to specify to use this -WhatIf parameter.
Note: This New-PublicFolderDatabaseRepairRequest cmdlet only applies in the Exchange Server 2010.
You cannot use this command in any other version of Exchange like 2013, 2016 etc… So, to repair corrupt or damaged Exchange public folder database, you can use the alternative solution provided by SysTools i.e. Exchange Server Recovery Software which supports offline / dismounted pub.edb file & priv.edb file. Users can easily load the public folder and recover & repair the EDB public folder of any Exchange Server version (2003 to 2019) with no data loss.
This recovery manager for Exchange database provides scan mode option i.e. Quick and Advance scan that recovers & repair Public folder database without any loss of data. To remove minimal corruption use the Quick scan and to recover highly corrupted EDB file select the advance scan. With this option, users can also recover deleted public folder Exchange 2016/2013/2010.
Any users (technical and non-technical) can use this software to recover & repair the Exchange database file as it provides the graphical user interface which eases the workload and saves their time as well as effort too.
After recovery, users can extract mailbox from EDB file Exchange 2016/2013 and export directly to the Live Exchange Server, Office 365 and different file formats (PST, EML, HTML, MBOX, MSG, PDF). This utility supports all versions of Exchange Server, Microsoft Outlook and Windows OS.
Bringing It All Together
Now users have complete information on how to use the New-PublicFolderDatabaseRepairRequest PowerShell command to detect and repair the public folder database replication issue. But users can only use this cmdlet in Exchange Server 2010. In order to repair the severely damaged / corrupted / unhealthy public folder DB of Exchange 2019/2016/2013/2010 and below version users can use the advanced software mentioned in the above section that easily recover and repair EDB file and mailboxes without any data loss in a hassle freeway.