Aller au contenu principal

File Exclusion

Thread needs solution

On an upgrade install from VMP8 to VMP9, I am seeing this warning in the logs. The backups are successful.

Is backup Exclusion supported? The options are there in the backup job setup.
If it is supported, any ideas why it would work on vmp8 but not vmp9 in the same job?

Thanks!

File exclusion is not supported.
Additional info:
--------------------
Error code: 47
Module: 7
LineInfo: a5695862aaf8e67e
Fields: PartitionId : 219
Message: File exclusion is not supported.
--------------------

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Jeremy,

The files/folders exclusions are supported for Win XP SP3+ (or higher or Linux) guest operating systems which have valid VMware Tools running inside them. Also another requirement is that the backed up VM is turned On. Can you please send me in PM (or attach here) the backup log so that I can check it out and advise on the exact reason for this message?

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

Hello!

I've similar errors with AVMP9. All VMs - Windows Server 2003, 2008 R2, Windows 7 Prof, SBS2011, etc up to date and run with the latest vmTools.

Here is the log:

File exclusion is not supported.
Additional info:
--------------------
Error code: 47
Module: 7
LineInfo: a5695862aaf8e67e
Fields: PartitionId : 249
Message: File exclusion is not supported.
--------------------

Thanks for your help and best regards,
Gabor

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Gabor,

Can you please send me the full log (View->Show Logs->Save All To File) from the backup task in a private message? One message from the log is not enough for proper analysis unfortunately.

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

Since I updated to vmprotect 9, the file exclusion does not work properly! Please tell me what to do: what have I to write to exclude the drives F:\ and G:\?! Backing up all drives is not needed... I tried it to eclude with F:/* and F:\* too but it does not work! Thanks in advice

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi PN_USER,

In fact there was nothing changed in files/folders exclusion mechanics between 8th and 9th version. In your case the exclusions should work as they did before. How did you notice that they are not working? Are there any events in the backup log? If yes, then can you please send it over to me in a private message?

P.S. The correct exclusions in your case should be F:\* + G:\* . Another way to check the proper drive letters is to go to File Recovery and check the drive letters while browsing through the contents of the backup of this VM.

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

Because acronis should do an incremental Backup of the local drives C:\ and E:\ (normally it takes about 45 minutes), but in fact the task is running since 18 hours and over 1 TB data has been transferred during the backup task. As you said that nothing changed in exlusion mechanics, the exlusion should work like with vmproect 8... I will try do write F:\* + G:\* in the exclusion mask...

It does not work how it should... I wrote in the exlusion mask to exclude drives c:\ and d:\ too for testing purposes, but acronis still ignores is and backups all... i tried some different writings of the drive letters, but it always ignores my exclusions... i will send you a private message vasily...

Hello Vasily,

Have you been able to figure out the problem with the reported below error as I see that in one of my VM backups using vmP9?

Felix.

--------------------
Error code: 47
Module: 7
LineInfo: a5695862aaf8e67e
Fields: PartitionId : 219
Message: File exclusion is not supported.
--------------------

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Felix,

There are different issues actually described by "Gábor Pekárovics" and "PN_USER" - in one case there was a specific partitions configuration inside the VM (including dynamic volumes which seem to be the culprit) and another one is still being investigated. I'd recommended you to send me the log from the backup in a private message so that I can check what's going wrong and advise on further actions.

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

Sorry, but fact you has changed. In VM9 there driveletter is now the we in the guest system. It means, drive c: is now c: also in vmProtect. The system reserved now is the next free drive letter after the last drive.

Sorry, but fact you has changed. In VM9 there driveletter is now the we in the guest system. It means, drive c: is now c: also in vmProtect. The system reserved now is the next free drive letter after the last drive.

I've the same problem after upgrade VM9, have you solution for me? The log as attachments

Fichier attaché Taille
153450-110617.zip 7.95 Ko
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi!

From the log I can see that there is one specific partition (4-0) which seems to be triggering the warning. Can you please send me the following information in a private message:

1) Screen shots of disk management from the guest OS of the backed up problematic VM (ATFFILEDB.vmx in your case)
2) If there are any dynamic disks inside please clarify their type (spanned/RAID-5/stripped/etc.)
3) Please clarify whether there are any RDM disks attached to the backed up VM (if yes then whether they are attached in physical or virtual compatibility mode)?
4) Windows System Information outputs (.nfo) from the guest OS of the backed up VM.

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

I have the same error with the same message and the same codes. I've migrated from vm8 to vm9, too.

Waiting for an answer.

Giacomo

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Giacomo,

Have you submitted a support ticket for this problem? The logs + information listed in my previous comment will be required for proper investigation of the issue.

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