Mount failed on file level restore

[cicero]

Hi,

I'm trying to do a filelevel restore on a RedHat EL 5.3 Guest running Lotus Domino in Vmware ESX 3.5u3 with ext3 Filesystem
backed up by Veeam Backup 3.0.1 on my WinXP Client without warnings on a Network Drive Y:\....

Installing the FLR Plugin failes because of the already installed Veeam Backup 3.0.1

"Mount failed
Client error: Der angegebene Dienst wurde zum löschen markiert
CreateService failed
VeeamFSR driver cannot be started. Agent path: [C:\....]
The filesystem cannout be mounted. Mount point [C:\...]
Filesystem description: [FSR filesystem. Backuptype: Local backup. Full backup path: Y:\...]
Cannot mount filesystem for the FSR reestore. Full backup path: y:\...]
Extracted files: [0c2....vmdk]
Cannot start file level restore"

Is this a known issue, or do I have to open a call?

Thanks, David

[cicero]

after reinstalling and reboot, the is a new error message:

"No disks have been mounted. Either disks of this type aren't supported or some error occured. See log file for details."

I'll send the logfiles to support@veeam.com

David

[Gostev]

David, first error is clearly an upgrade issue (reboot is needed because driver is used), this is why re-install and reboot helped.
Second error needs to be troubleshooted with logs which can be retrieved from the Logs node in the FLR plug-in backup browser window.

[cicero]

in FLR Plugin direct executet, i get following errer messages.
Log are not able to export after this messages:

Error stream: Killed
Chanenl has been closed

maybe interessting logs, directly in Player:

Hard Disk: srv77domino.vmdk
sda1(ext3fs)
sda3(ext3fs)
sda5(ext3fs)

less sd_error:
sda\tUnsupported filesystem
sda2\tnoerror
sda4\tnoerrot

less sd.log
sda1\text3fs
sda3\text3fs
sda5\text3fs

dmesg
...
Out of memory: kill process 308 (perl) score 723 or a child
...
Kille process 208 (perl)

[Gostev]

David, I don't know if you heard back from support yet, but I see out of memory error there. And I know Perl does have memory management issues on low-memory configurations in some scenarios. So please try to do the following - I know that this workaround has helped once in another situation where Linux FLR was also failing due to Perl memory issue.

1. On your Veeam Backup server, locate the following file in the Veeam Backup installation folder: LiveCD\LiveCD.tpl
2. Open it and locate the following line: memsize = “64”
3. Update 64 to 256, and save the file

If it does not help, then please wait until support hears back from development.

[cicero]

GREAT! Now works perfectly!
Thanks a lot for the support!!

David

[Gostev]

Cool - we will make it a standard setting in the next update then.

The other scenario when this fix helped was connected with performing restore of a folder containing hundreds of files - the copy was failing on random files with default FLR appliance memory settings.