Forum Discussion

MartenT's avatar
MartenT
Copper Contributor
Jan 15, 2026
Solved

Autoreseed, now what?

Have had a disk failure in a four server Exchange SE DAG with autoreseed enabled. New disk inserted, but now what? What I can google and AI myself to is something like this: Bring the new disk onli...
Exchange Server
  • Scott_Schnoll's avatar
    Scott_Schnoll
    Jan 15, 2026

    Yes, you'll need to configure your spare using the same configuration as the failed drive. 

    So, bring the new disk online (e.g., 

    Get-Disk | Where IsOffline -eq $true | Set-Disk -IsOffline $false

    Then, delete the empty mount point.

    Then, create a new simple volume formatted as ReFS with a 64k allocation unit, and label the drive using the failed drive's label.

    Next, verify the disk is recognized as a spare. Start with the server AutoDAG properties (e.g.,

    Get-MailboxServer <Server> | FL *Auto*

    Examine the output for accuracy, especially AutoDagVolumesRootFolderPath, AutoDagDatabaseCopiesPerVolume, and AutoDagTotalNumberOfDatabases.

    Confirm that Exchange sees the new volume.

    Get-Volume | Where FileSystem -eq ReFS

    Make sure the mount point is under the AutoDAG root (e.g., C:\ExchangeVolumes\).

    Then, resume the copies that were affected.  This will cause them to be in the FailedandSuspended state and then AutoReseed should do its thing.

    If that doesn't work, then manually reseed the copies:

    Update-MailboxDatabaseCopy <DB\Server> -DeleteExistingFiles

    Hope this helps!

MartenT's avatar
MartenT
Copper Contributor
Jan 15, 2026

Thank you very much for your explanation!

So in a post event, when this has happend, is that action to take to remove the old mount point and create a new one?

"For a disk to be automatically formatted, the volume must have a mount point in the root volumes path (by default, C:\ExchangeVolumes) and must not have any mount points in the database volumes path (by default, C:\ExchangeDatabases) "

Scott_Schnoll's avatar
Scott_Schnoll
Brass Contributor
Jan 15, 2026

Yes, you'll need to configure your spare using the same configuration as the failed drive. 

So, bring the new disk online (e.g., 

Get-Disk | Where IsOffline -eq $true | Set-Disk -IsOffline $false

Then, delete the empty mount point.

Then, create a new simple volume formatted as ReFS with a 64k allocation unit, and label the drive using the failed drive's label.

Next, verify the disk is recognized as a spare. Start with the server AutoDAG properties (e.g.,

Get-MailboxServer <Server> | FL *Auto*

Examine the output for accuracy, especially AutoDagVolumesRootFolderPath, AutoDagDatabaseCopiesPerVolume, and AutoDagTotalNumberOfDatabases.

Confirm that Exchange sees the new volume.

Get-Volume | Where FileSystem -eq ReFS

Make sure the mount point is under the AutoDAG root (e.g., C:\ExchangeVolumes\).

Then, resume the copies that were affected.  This will cause them to be in the FailedandSuspended state and then AutoReseed should do its thing.

If that doesn't work, then manually reseed the copies:

Update-MailboxDatabaseCopy <DB\Server> -DeleteExistingFiles

Hope this helps!

  • MartenT's avatar
    MartenT
    Copper Contributor
    Jan 16, 2026

    Many thanks for your assistance in this matter, really appreciate it!

    Regards,

    Marten