Home / server / Questions / 985949
Accepted
confoundr
Asked: 2019-09-28 12:39:15 +0800 CST

LOG Space Issues -- Figuring Out the Disk Space needed for DAG CopyQueueLength

  • 772

I have a DAG Database, DAG1, with 300000 CopyQueueLength. The Status for the copy is Failed and Suspended. In researching the problem I found that a reseed is needed for the database to get exchange copy up and running-- However I'm concerned about the space on that DAG database needs to copy over to the EXCH2 server.

Does CopyQueueLength denote the items to be copied or the size in kb?

What should I take into account for the space required before running a reseed?

background

  • EXCH1, and EXCH2 are in a DAG
  • EXCH1, and EXCH2 are VMware Servers
exchange-2016

1 Answers

  1. Best Answer

    Ultimately, I set the corresponding disk from EXCH1 to EXCH2 to the same size. When running the reseed process the logs were consolidated between the servers. I ran the copy via the https://localhost/ecp

    1. Selected Servers> Databases> Database
    2. Selected Update in the right hand side
    3. Selected EXCH1 as the server to reseed from
    4. let the reseed run

    At the start of the copy, I saw the Used Disk space reduce within a couple minutes-- I assume this was do to whatever consolidation process that the reseed process runs.

    • 1