The help given by get-help Start-VBRWindowsFileRestore is wrong, it talks about restoring vm (.vmdk,...) files but not files inside the windows machine.
The help information is correct. The restore procedure is similar to restoring VM files, though there are slight differences. For example if you need to restore readme.txt file located on the drive C on the root folder, you should use the syntax below:
Could you please shoot your log files to our support team as it is not expected bahviour. Besides, I would appreicate if you could send me your ticket number, so I could update this topic with the resolution later on.
Olivier, I haven't seen Michael opening a support case with our technical team, so I cannot update this topic with possible resolution. I would appreciate if you could contact our support guys and investigate this issue together, as we cannot reproduce it in our labs.
Hi,
The virtual disk is visible in the file explorer, the file is correctly copied.
It seems that Stop-VBRWindowsFileRestore does not close the virtual dirves...
System events are (sorry in French):
3/8/2011 11:46:04 2 2 57 VirtualDK N/A HDV-SAUVEGARDE \Device\Virt
3/8/2011 11:46:25 4 0 26 Application Popup N/A HDV-SAUVEGARDE Windows - L'écriture différée a échoué Windows n'a pas pu enregistrer les données du fichier \Device\VirtualDiskVolume1\$MftMirr. Les données ont été perdues. Cette erreur peut être due à une panne de votre matériel ou de votre connexion réseau. Essayez d'enregistrer ce fichier à un autre emplacement.
is there any follow up on this topic ?
we have the exact same issue : veeam transport service keeps a lock on the files and when reviewing the log files, the mount log files says "waiting for next command" as last action.
it seems the stop-VBRWindowsFileRestore does nothing
as a side note, the powershell help for this command suggest you can specify as an optional parameter the mount point to close, but how do one find this mount point reference using powershell commands ?
It seems that the code provided above missed a required line – Stop-VBRWindowsFileRestore command should be pointed to an [FileRestore] object ($Result, in other words). So, the last line should be:
Get-VBRBackup | where {$_.jobname -eq "Name of your job"} | Get-VBRRestorePoint | where {$_.name -eq "Name of your VM"} | Sort-Object creationtime -Descending | Select-Object -First 1
Tx for the much needed update on this thread, your tips solved the issue, I can now see in the logs the post-restore cleanup performed.
Globally the powershell command set lacks examples, if you ask for detailed help that should include samples, you only get the command syntax.
More sample scripts from Veeam would make an even better product !
Glad to hear that you’ve finally nailed your issue down.
As to the script examples, the most commonly used scenarios are covered in Getting Started section of this subforum. Anyway, thanks for the feedback; much appreciated.