Quiescing fails after Update to latest vmProtect 8

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Beiträge: 1
Kommentare: 0

After upgrading vmProtect 8 to the latest Version (8.0.8184), I'm getting an error on backing up one of our virtual servers.

When trying to make a snapshot of the virtual machine manually from vSphere client, i'm getting similar errors if choosing "quiesce filesystem" but no memory snapshot.
When performing a snapshot with both options (memory and filsystem quiesce) selected, the snapshot creation succeeds.

Operating System is Windows Server 2008 R2 SP1.

The error messages in the vmProtect log are:

Warnmeldung von localhost.localdomain: Das
Gastbetriebssystem hat während der Stilllegung
einen Fehler gemeldet. Der Fehlercode lautet: 3
Die Fehlermeldung lautet: Error when notifying
the sync provider.
Warnung
17.01.2013 08:12:53
Automatix
root

Warnmeldung von localhost.localdomain: Das
Gastbetriebssystem hat während der Stilllegung
einen Fehler gemeldet. Der Fehlercode lautet: 3
Die Fehlermeldung lautet: Quiesce operation
aborted
Warnung
17.01.2013 08:12:54
Automatix
root

Warnmeldung von localhost.localdomain: Das
Gastbetriebssystem hat während der Stilllegung
einen Fehler gemeldet. Der Fehlercode lautet: 5
Die Fehlermeldung lautet: 'VssSyncStart'
operation failed: IDispatch error #8454
(0x80042306)
Warnung
17.01.2013 08:12:55
Automatix
root

I attached a file listing the Vss writers installed on the machine (output from vssadmin list writers).

I used to have Errors on the TermServLicensing writer and disabled it in vmbackup.conf File. But the Error on vmProtect backup remained the same.

Thanks for help or hints on how to proceed.

Regards
Samuel

Anhang Größe
vsswriters.txt 2.55 KB
Do, 01/17/2013 - 07:43
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

Hi Samuel,

The snapshot failures are not in fact related to update of vmProtect, since the snapshot creation process (quiesced=on, memory=off) is always performed on behalf of vSphere itself. Most likely something changed in configuration of the problem VM since there are VSS writers failures:

Verfassername: "System Writer"
Verfasserkennung: {e8132975-6f93-4464-a53e-1050253ae220}
Verfasserinstanzkennung: {e6a9a0e2-936f-496f-98d4-0feff8e1040e}
Status: [10] Fehler
Letzter Fehler: Zeit�berschreitung

Verfassername: "IIS Config Writer"
Verfasserkennung: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Verfasserinstanzkennung: {32dc4c03-2647-4c37-a8a5-3c38523e9112}
Status: [10] Fehler
Letzter Fehler: Zeit�berschreitung

Verfassername: "WMI Writer"
Verfasserkennung: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Verfasserinstanzkennung: {f8d855e6-a7c5-4a30-9a0d-1cdf9d985342}
Status: [10] Fehler
Letzter Fehler: Zeit�berschreitung

The additional details should be found in Windows Event log after trying to create the snapshot from vSphere client. Note that snapshot with memory is always created (reported as successful by vSphere) even despite the failure of VSS inside the guest OS, and this snapshot is practically useless for backup purposes, which require that the filesystem and applications are brought into consistent state after the snapshot.

You should check the Windows Event Log inside the guest OS VM and check for errors. Some times this might be a temporary error which resolves itself after guest OS reboot, though it's hard to say definitely since in each case the situation is different.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Do, 01/17/2013 - 09:56
  • Anmelden, um Kommentare verfassen zu können
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Beiträge: 0
Kommentare: 61

Hi Sam, sorry to bump this up but can you please share on how you were able to fix this yet? Or was it a work around perhaps?

So, 01/05/2014 - 18:24
  • Anmelden, um Kommentare verfassen zu können