Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 8743

What is the -AutoRecovery.avhd suffix in the end of the VHD file names?

$
0
0

I´m doing backup using a simple script in my WIn2012R2

A batch file is combined with a simple set of commands in a diskshadow.txt file (see below)

There´s NO snapshots created (ever) and in the log file The robocopy part of the script) it appears:

What is that?

WHy a single VHD file, creates a bunch of .AVHD files and worst, an -AutoRecovery.avhd file?

80.2 m  maximo-bvs.CORP_D88FDF47-1672-49A5-BCF7-B3695D0D5033.avhd
32.4 m  maximo-bvs.CORP_DATA_8541169F-4C5E-4B9D-8FAD-07091FB9031C.avhd
122.4 m  maximo-bvs.CORP-AutoRecovery.avhd
50.0 g  maximo-bvs.CORP.vhd
56.2 m  maximo-bvs.CORP_8A478680-3331-4A60-BD61-D02063504F28.avhd
10.4 m  maximo-bvs.CORP_DATA-AutoRecovery.avhd
202.0 g  maximo-bvs.CORP_DATA.vhd
62.5 m  maximo-bvs.CORP_DATA_09B5DB15-B9BB-40D1-B372-F72CEFFD5246.avhd

====================diskshadow.txt =========================

delete shadows all

set context persistent

set verbose on

add volume C:\ alias DISCOC

create

expose %DISCOC% I:

exec HyperVBackup_exec.cmd

unexpose I:

delete shadows all

====================diskshadow.txt =========================

The log file of the diskshadow is:

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

Microsoft DiskShadow version 1.0
Copyright (C) 2013 Microsoft Corporation


-> delete shadows all 
No shadow copies found in system.
-> set context persistent 
-> set verbose on 
-> add volume C:\ alias DISCOC
-> create 
Excluding writer "Shadow Copy Optimization Writer", because all of its components have been excluded.
Component "\BCD\BCD" from writer "ASR Writer" is excluded from backup,
because it requires volume  which is not in the shadow copy set.
The writer "ASR Writer" is now entirely excluded from the backup because the top-level
non selectable component "\BCD\BCD" is excluded.

* Including writer "Task Scheduler Writer":
+ Adding component: \TasksStore

* Including writer "VSS Metadata Store Writer":
+ Adding component: \WriterMetadataStore

* Including writer "Performance Counters Writer":
+ Adding component: \PerformanceCounters

* Including writer "System Writer":
+ Adding component: \System Files
+ Adding component: \Win32 Services Files

* Including writer "Microsoft Hyper-V VSS Writer":
+ Adding component: \81A73D21-A9B1-4AA5-AA19-FECC86FD0C9E
+ Adding component: \Host Component

* Including writer "WMI Writer":
+ Adding component: \WMI

* Including writer "COM+ REGDB Writer":
+ Adding component: \COM+ REGDB

* Including writer "Registry Writer":
+ Adding component: \Registry

Alias DISCOC for shadow ID {c333bfe8-df61-4e8a-9389-53642d72ac60} set as environment variable.
Alias VSS_SHADOW_SET for shadow set ID {827cfcb3-4d8c-40a1-90c2-14669e060b0e} set as environment variable.
Inserted file Manifest.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file BCDocument.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM0.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM1.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM2.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM3.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM4.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM5.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM6.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM7.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM8.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM9.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file DisBAA2.tmp into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab

Querying all shadow copies with the shadow copy set ID {827cfcb3-4d8c-40a1-90c2-14669e060b0e}

* Shadow copy ID = {c333bfe8-df61-4e8a-9389-53642d72ac60}%DISCOC%
- Shadow copy set: {827cfcb3-4d8c-40a1-90c2-14669e060b0e}%VSS_SHADOW_SET%
- Original count of shadow copies = 1
- Original volume name: \\?\Volume{74d623a1-e9e5-11e4-80b4-806e6f6e6963}\ [C:\]
- Creation time: sexta-feira, 08/05/2015 01:02:12
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy19
- Not exposed
- Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes:  No_Auto_Release Persistent Differential

Number of shadow copies listed: 1
-> expose %DISCOC% I:
-> %DISCOC% = {c333bfe8-df61-4e8a-9389-53642d72ac60}
The shadow copy was successfully exposed as I:\.
-> exec HyperVBackup_exec.cmd 
Copiando VHDs Versao 3.2fb



 Log File : c:\dados\backup\hypervbackup_exec_08.log
-> unexpose I:
Shadow copy ID {c333bfe8-df61-4e8a-9389-53642d72ac60} is no longer exposed.
-> delete shadows all
Deleting shadow copy {c333bfe8-df61-4e8a-9389-53642d72ac60} on volume \\?\Volume{74d623a1-e9e5-11e4-80b4-806e6f6e6963}\ from provider {b5946137-7b9f-4925-af80-51abd60b20d5} [Attributes: 0x00420009]...

Number of shadow copies deleted: 1
-> 

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


Viewing all articles
Browse latest Browse all 8743

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>