Backup job of Exchange server FAIL

Hi Bruno,

The problem is most likely that the temp folder for user which is used to log into the VM (for application-aware backup purposes) is located on non-system disk (E:\temp\) - this causes failure to execute a VBS script via cscript.exe. You should change the temp folder location to system disk (C:\) and if this doesn't help then contact our support team for assistance.

(issue for internal reference: TTASK-7352)

Thank you.

Hi Vasily,

thank You for the reply, I've found in the KB that the TEMP variables MUST be in the system drive... so I've changed back to it... the variables was modified by some tries I've made to workaround the issue...

Now I've set the vars back to system drive.

But now I'm experiencing a VERY VERY STRANGE THING... let me try to explain:

- on the exchange vms is defined a user named acronis, member of administrators group

- the task job uses the acronis account in the "app aware" definition

- the check performed WITH USER acronis LOGGED ON (in vm console) = OK

- the check performed WITH USER acronis LOGGED OFF (no session in vm console) = FAIL

Seems that if there is NO SESSION active the check FAIL, but if there is the user LOGGED ON the check SUCCEED...

Any Ideas...?

Thanks, Bruno

Hi Bruno,

The issue you describe looks like a UAC-related one. The UAC may be not disabled for particular "Acronis" user in registry and this causes such behavior. Note that simply putting the UAC slider in control panel to lowest value does not actually disable UAC. It has to be disabled in Windows registry by setting the following value to 0:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -> "EnableLUA"

After that the VM should be rebooted.

If this still doesn't help, please clarify how exactly the check fails (what's the exact error) so that I can advise further.

Thank you.

Hi Vasily,

I checked the registry and the key You indicated is already set to 0

Let me perform the backup this evening, it has gone bad for days, this evening I'll leave the sessions opened on the vms console.

Tomorrow I'll reproduce the error, logging off the sessions and then I'll write here the result.

Thanks,

Bruno

Hello Vasily,

I would like to ask Your help... after a period of successful backups, the problem is still present and we cannot perform application-aware backups of our Exchange 2010 installation.

The environment consist in 2 Exchange Server in cluster (DAG), the size of disks is 2TB on every server, the TIB file is 4TB of size, allocated on a QNAP NAS.

Most of executions terminates with only 1 server backed up, the transaction logs were not truncated and the disks became full.

The check in the job definition is successful, MS Exchange is correctly detected on both VM.

I've just tried a backup of a single node, the job failed after 2 hours of execution with the following error:

Attività 'Backup UC-MAILBOX02' fallita: 'Impossibile creare un backup.
Informazioni aggiuntive:
--------------------
Codice errore: 3
Modulo: 435
LineInfo: 555b5abba0950340
Campi:
Messaggio: Impossibile creare un backup.
--------------------
Codice errore: 32786
Modulo: 114
LineInfo: 28314c961de7d337
Campi:
Messaggio: Impossibile preparare per il backup.
--------------------
Codice errore: 353
Modulo: 149
LineInfo: a71592046cb2c5f6
Campi:
Messaggio: Impossibile eseguire il backup del gruppo.
--------------------
Codice errore: 2
Modulo: 218
LineInfo: 338a407ad20e0987
Campi:
Messaggio: Si è verificato un errore durante l'esecuzione del motore di backup e ripristino.
--------------------'.

Waiting for Your Kind reply,

Best Regards.

Bruno

Bruno,

The error you quote is too common one and typically indicates backup engine crash. It definitely makes sense to contact our support team for assistance with the issue. It may be caused by various reasons which need to be revealed. I'd first of all started with creation of new backup archive file, since 4TB size is close to theoretical limit supported for archive size in default build of Acronis Backup for VMware which is 32-bit (we have custom 64-bit build which overcomes this limitation) and it may be the root cause. Still contacting our support team for initial investigation is definitely required.

Thank you.

Vasily,

thanks for Your quick response, as usual. I'll try to perform a backup with a new file, as You suggested.

How can we obtain the 64-bit build ?

Is it available on the website?

Thank You so much.

Bruno

Bruno,

The 64-bit build (#10558) is not available from the web site and it can be obtained only from our support team.

Thank you.