Copy a 11GB MDF-file gets Access denied to path

[roberi]

Hi

I have two files I want to copy (restore) from a full backup to a local drive. Permissions are set. Free space is OK.
One file is a .ldf file 4.6GB and the other is a .mdf file at 11GB.
The ldf file can be copied with no problem.
However the mdf file copies to aprox half the file then a pop-up says Access to path denied.
If I open Explorer and try to copy from there it says after half the file, You require permission from DOMAIN\ADMIN to make Changes to this file. Try again or Cancel.

Veeam version 6.5.0.109 (64bit)
Windows 2008R2

Please advice!

Best regards
Robert

[veremin]

Are there any security/antivirus application running that might lock the required file?

Thanks.

[roberi]

Hi

I disable my antivirus protection. But the problem remains.
The VeeamFLR folder is on my C-drive, with 9.5GB free space... could that be the problem? I read someware that the FLR-folder dont take any space?!

[veremin]

The VeeamFLR folder is on my C-drive, with 9.5GB free space... could that be the problem?

Yep, it doesn’t take any space on your disk. So, there should be any issue with it, unless you're restoring 11 GB file to C: drive (with only 9.5 GB free).

I assume you’re utilizing "Windows FLR" option, aren’t? If so, can you put into use "Other OS" one, and see whether the corresponding files can be restored successfully or not.

Thanks.

[roberi]

no its going to the D-drive.. So space there are...
I tried the Other OS one... and it doesn't give an error but the progress bar and time indicators freezes at aprox the same time as the Windows FLR.
Other files restores OK.. so .. Murphys law… the only file I need back is corrupt or something?!

[veremin]

The only file I need back is corrupt or something?!

As the last workaround I can propose to you to use Instant VM Recovery in order to start your VM directly from a backup, connect to it, and try to download required files from there.

If even this doesn’t help, feel free to contact our support team, since deep log investigation seems to be required.

Thanks.