Avamar: ADMe-Exchange BU-gendannelse ved hjælp af -exchvssavtar (avtar)

Summary: ADMe kan gendanne Exchange-sikkerhedskopier til en generisk Windows-midlertidig server uden behov for Exchange S/W eller Avamar Exchange-plugin. Transaktionslogfiler i dette tilfælde skal afspilles manuelt mod edb-filerne ved hjælp af Eseutil for at få det i en ren nedlukningstilstand. Følgende procedurer dokumenterer de Eseutil-trin, der kræves for at afspille transaktionslogfilerne igen. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Instructions

En typisk ADMe-jobpolitik, der bruges til at arrangere Exchange-sikkerhedskopiering til en generisk Windows-midlertidig server uden behov for Microsoft Exchange S/W eller Avamar Exchange-plug-in, bør ligne følgende eksempel.
Den ADMe-indstilling, der kræves for at aktivere denne proces, er "-exchvssavtar", som skal tildeles linjen eller feltet Migration Flags som vist.

================< Job Policy Contents >=================
Environment_Number::   1
Base_Group_Name::      exch01
Sub_Group_Numbers::    0
Select_Flags::         -d -last -exchvss
View_Flags::           -d
Migration_Flags::      -d -stageonly -D -m -exchvssavtar   (include -stageonly only if you plan to confirm the eseutil steps)

=====================================================================================================

PRØVNING-1:

I denne laboratorietest blev Exchange-sikkerhedskopiering #293 iscenesat til en målmappe med navnet C:\ADME3\exch01 ved hjælp af ADMe-indstillingen "-exchvssavtar."
Naviger ned ad stinavnet , hvor edb-, logfilerne og kontrolfilerne findes, som i dette eksempel ser fremhævet sti.
I dette eksempel var edb- og logfilerne i en fælles mappe, men i et kundemiljø er edb og logfiler næsten altid i separate mapper på separate drevbogstaver.

C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox>cd DB1

Fra en kommandoprompt med administratorrettigheder skal du gå til den mappe, der indeholder edb- og logfilerne.
Angiv mappeindhold for både edb- og logfilplaceringer, og kopier og indsæt indhold i notesblok til reference, især for tidsstempler og tilgængelige logfilnavne.

C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1>  dir
 Directory of C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1

11-01-2023 17:22 142.671.872 DB1.edb<========bemærk, at edb-filens tidsstempel er fra 11. januar 2023, tidspunktet for VSS Exchange-sikkerhedskopien.

01/12/2023  03:22 AM             8,192 E01.chk
01/12/2023  03:13 AM         1,048,576 E0100016666.log
01/12/2023  03:22 AM         1,048,576 E0100016667.log
01/12/2023  03:22 AM         1,048,576 E0100016668.log
01/12/2023  05:23 PM         1,048,576 E0100016669.log
01/13/2023  03:01 AM         1,048,576 E010001666A.log
01/13/2023  03:02 AM         1,048,576 E010001666B.log
01/13/2023  03:12 AM         1,048,576 E010001666C.log
01/14/2023  03:01 AM         1,048,576 E010001666D.log
01/14/2023  03:01 AM         1,048,576 E010001666E.log
01/14/2023  03:16 AM         1,048,576 E010001666F.log
01/16/2023  03:01 AM         1,048,576 E0100016670.log
01/16/2023  03:01 AM         1,048,576 E0100016671.log
01/16/2023  03:27 AM         1,048,576 E0100016672.log
01/17/2023  03:02 AM         1,048,576 E0100016673.log
01/17/2023  03:10 AM         1,048,576 E0100016674.log
01/17/2023  03:11 AM         1,048,576 E0100016675.log
01/18/2023  03:01 AM         1,048,576 E0100016676.log
01/18/2023  03:02 AM         1,048,576 E0100016677.log
01/18/2023  03:18 AM         1,048,576 E0100016678.log
01/18/2023  08:52 AM         1,048,576 E0100016679.log
01/18/2023  08:53 AM         1,048,576 E010001667A.log
01/18/2023  08:55 AM         1,048,576 E010001667B.log
01/18/2023  09:23 AM         1,048,576 E010001667C.log
01/18/2023  09:23 AM         1,048,576 E01tmp.log

Bekræft edb's nedlukningstilstand ved hjælp af kommandoen "Eseutil".

C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1>eseutil /mh DB1.edb | findstr State

Stat: Beskidt nedlukning<==== Bemærk, at EDB viser som værende i en beskidt nedlukningstilstand, fordi den blev sikkerhedskopieret ved hjælp af et VSS-øjebliksbillede, dette forventes fuldt ud, medmindre udvekslingsdatabasen var inaktiv på BU-tidspunktet uden udestående logfiler, der skal anvendes.

Skift mappen til logmappen, og brug derefter Eseutil til at bekræfte, at alle nødvendige logfiler er tilgængelige og i god stand, før de afspilles igen mod edb-filen.
E01 i dette eksempel repræsenterer logfilens præfiks eller basisværdi. Dette varierer, især når flere Exchange-edb-databaser er indeholdt i en given Exchange-forekomst.

C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1>eseutil /ml  E01
Verifying log files...
     Base name: E01
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016666.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016667.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016668.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016669.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E010001666A.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E010001666B.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E010001666C.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E010001666D.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E010001666E.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E010001666F.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016670.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016671.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016672.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016673.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016674.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016675.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016676.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016677.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016678.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E0100016679.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E010001667A.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E010001667B.log - OK
      Log file: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1\E010001667C.log - OK
No damaged log files were found.  <============ verification step to ensure all logs are in a ready to use state
Operation completed successfully in 0.984 seconds.

Skift mappen til den mappe, der indeholder edb-filen, der skal repareres.
Brug "Eseutil" til at køre syntaksen som vist på én linje for at afspille logfilerne igen og opdatere edb-filen.
Indstillingerne "/l <points to log path> /d <points to edb path>", omslutter hvert stinavn i dobbelte anførselstegn, da forskellige mappenavne kan indeholde mellemrum.

VIGTIGT:
Hvis du angiver forkerte stinavne til Eseutil, kan det medføre, at filen E01.chk og muligvis andre opdateres (sammenlign med originale filtidsstempler), hvilket forhindrer logfilerne i at blive anvendt korrekt, selv efter at stinavnene er blevet rettet. Det tilrådes at lave en kopi af de involverede mapper for hurtigt at sætte originale filer på plads igen, hvis denne situation opstår.
C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1>
eseutil /r E01 /l  "C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1" /d  "C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.03
Initiating RECOVERY mode...
    Logfile base name: E01
            Log files: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1
         System files: <current directory>
   Database Directory: C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1
Performing soft recovery...   <========= this is the step which will update the edb
                      Restore Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |----|----|----|----|----|----|----|----|----|----|
          ...................................................
Operation completed successfully in 0.812 seconds.

Når logfilerne er blevet afspillet igen, skal du kontrollere edb'ens nedlukningstilstand igen, så den nu bør være i ren nedlukningstilstand.

C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1>eseutil /mh DB1.edb | findstr State

Stat: Ren nedlukning<========= Bemærk, at edb nu viser sig at være i en ren nedlukningstilstand efter vellykket afspilning af logfilerne.

C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1>dir
 Directory of C:\ADME3\exch01\BYDATE\srv2008-exch10.nicktest.local\2023-01-18-08-59-34-293\srv2008-exch10_00000000\C\Program Files\Microsoft\Exchange Server\V14\Mailbox\DB1
01/23/2023  04:03 PM    <DIR>          .
01/23/2023  04:03 PM    <DIR>          ..
01/23/2023  04:03 PM       142,671,872 DB1.edb <========note the edb & chk file timestamps have now been updated to Jan 23, 2023 from Jan 11, 2023 as documented at the start of this process
============================================================================================================================================

Test-2

I dette næste eksempel bruges Avamar UI til at gendanne Exchange-sikkerhedskopien ved hjælp af Exchange-ekstramodulet, men deaktivere genafspilning af logfilerne. Den blev gendannet til mappenavnet C:\ADAM4 og de samme "Eseutil"-kommandosekvenser, der blev brugt som beskrevet ovenfor i Test-01-scenariet.

c:\ADAM4>dir
Directory of c:\ADAM4
01/23/2023  04:54 PM    <DIR>          .
01/23/2023  04:54 PM    <DIR>          ..
01/11/2023  05:22 PM       142,671,872 DB1.edb <============= note the edb file timestamp is from Jan 11, 2023 the time of the VSS Exch backup
01/23/2023  04:54 PM    <DIR>    _restoredLogs <============ The Avamar plugin recovers all logs to a common folder as shown
Vigtig:
Der har været mindst ét tilfælde, hvor den konsoliderede fælles logmappe til en sikkerhedskopi, der indeholder x4 edb-filer, hvilket resulterede i, at logpræfiksværdien overlapper og overskriver nogle logfiler, som i sidste ende ikke kunne anvendes med succes på edb-filen. Dette var Avamars skyld, da Exchange vedligeholder separate logmapper for hver edb, og sikkerhedskopieringsindholdet afspejler de separate logmapper. Se Esc https://jira.cec.lab.emc.com/browse/AVAMARESC-271 for detaljer og adgang til en plug-in binær opdatering, der gendanner logfiler vedrørende hver edb i deres oprindelige separate mappenavne.
C:\ADAM4> eseutil -mh DB1.edb | findstr State
01/23/2023  04:03 PM             8,192 E01.chk
01/23/2023  04:03 PM         1,048,576 E01.log
01/12/2023  03:13 AM         1,048,576 E0100016666.log
01/12/2023  03:22 AM         1,048,576 E0100016667.log
01/12/2023  03:22 AM         1,048,576 E0100016668.log
01/12/2023  05:23 PM         1,048,576 E0100016669.log
01/13/2023  03:01 AM         1,048,576 E010001666A.log
01/13/2023  03:02 AM         1,048,576 E010001666B.log
01/13/2023  03:12 AM         1,048,576 E010001666C.log
01/14/2023  03:01 AM         1,048,576 E010001666D.log
01/14/2023  03:01 AM         1,048,576 E010001666E.log
01/14/2023  03:16 AM         1,048,576 E010001666F.log
01/16/2023  03:01 AM         1,048,576 E0100016670.log
01/16/2023  03:01 AM         1,048,576 E0100016671.log
01/16/2023  03:27 AM         1,048,576 E0100016672.log
01/17/2023  03:02 AM         1,048,576 E0100016673.log
01/17/2023  03:10 AM         1,048,576 E0100016674.log
01/17/2023  03:11 AM         1,048,576 E0100016675.log
01/18/2023  03:01 AM         1,048,576 E0100016676.log
01/18/2023  03:02 AM         1,048,576 E0100016677.log
01/18/2023  03:18 AM         1,048,576 E0100016678.log
01/18/2023  08:52 AM         1,048,576 E0100016679.log
01/18/2023  08:53 AM         1,048,576 E010001667A.log
01/18/2023  08:55 AM         1,048,576 E010001667B.log
01/18/2023  09:23 AM         1,048,576 E010001667C.log
01/23/2023  04:03 PM         1,048,576 E01res00001.jrs
01/23/2023  04:03 PM         1,048,576 E01res00002.jrs
01/23/2023  04:03 PM         1,048,576 E01tmp.log

State: Dirty Shutdown <========= note the EDB shows as in a dirty shutdown state because it was backed up using a VSS snapshot, this is fully expected unless the exchg DB was totally idle at BU time.
C:\ADAM4\_restoredLogs>eseutil /ml E01
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Initiating FILE DUMP mode...
Verifying log files...
     Base name: E01
      Log file: c:\ADAM4\_restoredLogs\E0100016666.log - OK
      Log file: c:\ADAM4\_restoredLogs\E0100016667.log - OK
      Log file: c:\ADAM4\_restoredLogs\E0100016668.log - OK
      Log file: c:\ADAM4\_restoredLogs\E0100016669.log - OK
      Log file: c:\ADAM4\_restoredLogs\E010001666A.log - OK
      Log file: c:\ADAM4\_restoredLogs\E010001666B.log - OK
      Log file: c:\ADAM4\_restoredLogs\E010001666C.log - OK
      Log file: c:\ADAM4\_restoredLogs\E010001666D.log - OK
      Log file: c:\ADAM4\_restoredLogs\E010001666E.log - OK
      Log file: c:\ADAM4\_restoredLogs\E010001666F.log - OK
      Log file: c:\ADAM4\_restoredLogs\E0100016670.log - OK
      Log file: c:\ADAM4\_restoredLogs\E0100016671.log - OK
      Log file: c:\ADAM4\_restoredLogs\E0100016672.log - OK
      Log file: c:\ADAM4\_restoredLogs\E0100016673.log - OK[1][2]
      Log file: c:\ADAM4\_restoredLogs\E0100016674.log - OK
      Log file: c:\ADAM4\_restoredLogs\E0100016675.log - OK
      Log file: c:\ADAM4\_restoredLogs\E0100016676.log - OK
      Log file: c:\ADAM4\_restoredLogs\E0100016677.log - OK
      Log file: c:\ADAM4\_restoredLogs\E0100016678.log - OK
      Log file: c:\ADAM4\_restoredLogs\E0100016679.log - OK
      Log file: c:\ADAM4\_restoredLogs\E010001667A.log - OK
      Log file: c:\ADAM4\_restoredLogs\E010001667B.log - OK
      Log file: c:\ADAM4\_restoredLogs\E010001667C.log - OK
No damaged log files were found. <============ verification step to ensure all logs are in a ready to use state
Operation completed successfully in 1.125 seconds.

Gå tilbage til mappen med edb-filen.
Brug "Eseutil" til at køre følgende syntaks, alle på én linje, for at afspille logfilerne igen og opdatere edb-filen, hvor indstillingen "/l <peger på logstien> /d <peger på edb-stien>."
Sæt hvert stinavn i dobbelte anførselstegn, da forskellige mappenavne kan indeholde mellemrum.

c:\ADAM4>eseutil /r E01 /l "c:\ADAM4\_restoredLogs" /d "c:\ADAM4"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.03
Initiating RECOVERY mode...
    Logfile base name: E01
            Log files: c:\ADAM4\_restoredLogs
         System files: <current directory>
   Database Directory: c:\ADAM4
Performing soft recovery...   <========= this is the step which will update the edb
                      Restore Status (% complete)
          0    10   20   30   40   50   60   70   80   90  100
          |----|----|----|----|----|----|----|----|----|----|
          ...................................................
Operation completed successfully in 0.515 seconds.
c:\ADAM4>dir
 Directory of c:\ADAM4
01/23/2023  05:35 PM    <DIR>          .
01/23/2023  05:35 PM    <DIR>          ..
01/23/2023  05:35 PM       142,671,872 DB1.edb <==note the edb & chk file timestamps have now been updated to Jan 23, 2023 from Jan 11, 2023 as documented at the start of this process
01/23/2023  05:35 PM             8,192 E01.chk
C:\ADAM4>eseutil /mh DB1.edb | findstr State

Stat: Ren nedlukning<========= bemærker, at edb nu viser sig at være i en ren nedlukning.

 

Additional Information

Links
der ikke er fra DellFølgende links er udelukkende til referenceformål. Der er mange links tilgængelige på internettet, der diskuterer brugen af Eseutil til at reparere en edb-fil.

Et link, der dokumenterer brugen af /p-indstillingen , som er en hård reparation, er tilgængelig som en sidste udvej for at reparere en edb.
https://social.technet.microsoft.com/wiki/contents/articles/52087.exchange-extensible-storage-engine-utility-eseutil.aspxDette hyperlink fører dig til et websted uden for Dell Technologies.

Der er også professionelle værktøjer til rådighed til at reparere edb-filer, der ligner den på denne lin.
https://www.systoolsgroup.com/updates/exchange-dirty-shutdown-state/Dette hyperlink fører dig til et websted uden for Dell Technologies.

 

Affected Products

Avamar, Avamar Client
Article Properties
Article Number: 000207859
Article Type: How To
Last Modified: 12 Jun 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.