I search a script using Start-VBRWindowsFileRestore.
I want to copy a file, in fact my exchange files priv1.edb from my Veeam backup to a nas.
Any example ?
-
omorin
- Enthusiast
- Posts: 37
- Liked: 4 times
- Joined: Oct 19, 2010 1:37 pm
- Full Name: olivier morin
- Location: Bergerac, France
- Contact:
Start-VBRWindowsFileRestore
Bonjour,
I search a script using Start-VBRWindowsFileRestore.
I want to copy a file, in fact my exchange files priv1.edb from my Veeam backup to a nas.
Any example ?
I search a script using Start-VBRWindowsFileRestore.
I want to copy a file, in fact my exchange files priv1.edb from my Veeam backup to a nas.
Any example ?
-
omorin
- Enthusiast
- Posts: 37
- Liked: 4 times
- Joined: Oct 19, 2010 1:37 pm
- Full Name: olivier morin
- Location: Bergerac, France
- Contact:
Re: Start-VBRWindowsFileRestore
Bonsoir,
The help given by get-help Start-VBRWindowsFileRestore is wrong, it talks about restoring vm (.vmdk,...) files but not files inside the windows machine.
Confusing...
I think the help file is not correct.
The help given by get-help Start-VBRWindowsFileRestore is wrong, it talks about restoring vm (.vmdk,...) files but not files inside the windows machine.
Confusing...
I think the help file is not correct.
-
Vitaliy S.
- VP, Product Management
- Posts: 27105
- Liked: 2717 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Start-VBRWindowsFileRestore
Hello Olivier,
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:
Hope it helps!
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:
Code: Select all
$result = Get-VBRBackup | where {$_.JobName -eq "Backup Job 1"} | Get-VBRRestorePoint | sort CreationTime -Descending | select -First 1 | Start-VBRWindowsFileRestore
$file = $result.FirstDrive + “:\readme.txt”
Copy $file c:\
Stop-VBRWindowsFileRestore-
omorin
- Enthusiast
- Posts: 37
- Liked: 4 times
- Joined: Oct 19, 2010 1:37 pm
- Full Name: olivier morin
- Location: Bergerac, France
- Contact:
Re: Start-VBRWindowsFileRestore
This script is OK, a ":" is missing in $file = $result.FirstDrive + “\readme.txt”, the good yntax is $file = $result.FirstDrive + “:\readme.txt”
And you have to close the job with Stop-VBRWindowsFileRestore
And you have to close the job with Stop-VBRWindowsFileRestore
-
Vitaliy S.
- VP, Product Management
- Posts: 27105
- Liked: 2717 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Start-VBRWindowsFileRestore
Olivier, thanks for getting back and posting an update, much appreciated. I've adjusted the script above with your comments.
-
omorin
- Enthusiast
- Posts: 37
- Liked: 4 times
- Joined: Oct 19, 2010 1:37 pm
- Full Name: olivier morin
- Location: Bergerac, France
- Contact:
Re: Start-VBRWindowsFileRestore
Ouh !
I had to reboot my Veeam server because of virtual-disk error...
I think that Stop-VBRWindowsFileRestore is not enough, or needs parameters...
I had to reboot my Veeam server because of virtual-disk error...
I think that Stop-VBRWindowsFileRestore is not enough, or needs parameters...
-
michaelschad
- Lurker
- Posts: 1
- Liked: never
- Joined: Jul 10, 2009 4:37 pm
- Full Name: MIchael Schad
- Contact:
Re: Start-VBRWindowsFileRestore
Hello,
I have the same problem as omorin, the backup file is not closed after dismounting with Stop-VBRWindowsFileRestore. Have anyone a solution ?
I have the same problem as omorin, the backup file is not closed after dismounting with Stop-VBRWindowsFileRestore. Have anyone a solution ?
-
Vitaliy S.
- VP, Product Management
- Posts: 27105
- Liked: 2717 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Start-VBRWindowsFileRestore
Hello Michael,
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.
Thank you!
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.
Thank you!
-
omorin
- Enthusiast
- Posts: 37
- Liked: 4 times
- Joined: Oct 19, 2010 1:37 pm
- Full Name: olivier morin
- Location: Bergerac, France
- Contact:
Re: Start-VBRWindowsFileRestore
Still no solution ?
-
Vitaliy S.
- VP, Product Management
- Posts: 27105
- Liked: 2717 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Start-VBRWindowsFileRestore
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.
-
omorin
- Enthusiast
- Posts: 37
- Liked: 4 times
- Joined: Oct 19, 2010 1:37 pm
- Full Name: olivier morin
- Location: Bergerac, France
- Contact:
Re: Start-VBRWindowsFileRestore
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.
I have to reboot teh machine.
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.
I have to reboot teh machine.
-
Gostev
- Chief Product Officer
- Posts: 31513
- Liked: 6691 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Start-VBRWindowsFileRestore
Hello, please open a support case to let us investigate this behavior more closely. Thanks!
-
sccit
- Lurker
- Posts: 2
- Liked: never
- Joined: Jul 29, 2013 12:33 pm
- Contact:
Re: Start-VBRWindowsFileRestore
Dear all,
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 ?
tx
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 ?
tx
-
veremin
- Product Manager
- Posts: 20282
- Liked: 2257 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Start-VBRWindowsFileRestore
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:
As to finding a restore point, it can be done using the following script, that will get a latest restore point of a given VM within a specified job:
Hope this helps.
Thanks.
Code: Select all
Stop-VBRWindowsFileRestore $ResultCode: Select all
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 Hope this helps.
Thanks.
-
sccit
- Lurker
- Posts: 2
- Liked: never
- Joined: Jul 29, 2013 12:33 pm
- Contact:
Re: Start-VBRWindowsFileRestore
Hi Vladimir,
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 !
Many thanks for the swift reply
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 !
Many thanks for the swift reply
-
veremin
- Product Manager
- Posts: 20282
- Liked: 2257 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Start-VBRWindowsFileRestore
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.
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.
-
erzvbrvm
- Novice
- Posts: 5
- Liked: never
- Joined: Jan 23, 2023 5:08 pm
- Full Name: Ed Zielinski
- Contact:
Re: Start-VBRWindowsFileRestore
Sorry! I actually did run the command with the paramater, but I pasted the wrong command line (from a previous run). To provide more accurate details, I started a start-transcript in PowerShell, then ran the script again, with a parameter, but I also enclosed the server name in double quotes as you specified. Here is the content of each of the files. Note: Identifying information such as server names and usernames has been edited, but everything else is untouched.
It looks like there is some error encountered at the beginning of the script according to the transcript it shows "TerminatingError(): "System error." Could this explain why most of the write-output content does not appear in the console or in the log file?
It looks like there is some error encountered at the beginning of the script according to the transcript it shows "TerminatingError(): "System error." Could this explain why most of the write-output content does not appear in the console or in the log file?
Code: Select all
Import-Module Veeam.Backup.Powershell
#Set $servername to value of first command line argument
$servername=$args[0]
#Start windows file restore session
#Try gathering restore point into variable
#This seems to fail unless the server name is explicitly specified. The below command does not work.
$restorepoint = Get-VBRRestorePoint -name $servername | Sort-Object creationtime -Descending | Select-Object -First 1
$Logrestorepoint = "Echo value of restorepoint"
Write-output $Logrestorepoint
Write-output $restorepoint
$Logrestorepoint | out-file -FilePath c:\temp\Test_Script_2.log -append
$restorepoint | out-file -FilePath c:\temp\Test_Script_2.log -append
#Actually start the Windows file restore session
$LogStartrestore = "Starting file restore"
Write-Output $LogStartrestore
$LogStartrestore | out-file -FilePath c:\temp\Test_Script_2.log -append
$result = Get-VBRRestorePoint -name $servername | Sort-Object creationtime -Descending | Select-Object -First 1 | Start-VBRWindowsFileRestore
$RestSession = Get-VBRRestoreSession | select -first 3
#This fails to produce any output
$LogRestSession = "Echo contents of RestSession"
Write-output $LogRestSession
Write-output $RestSession
$LogRestSession | out-file -FilePath c:\temp\Test_Script_2.log -append
$RestSession | out-file -FilePath c:\temp\Test_Script_2.log -append
#Display the contents of $result
Write-output "Echo contents of $result"
$result
$session = Get-VBRRestoreSession
#This fails to produce any output (write-host behaves the same)
$Logservername = "Echo contentes of servername"
Write-output $Logservername
Write-output $servername
$Logservername | out-file -FilePath c:\temp\Test_Script_2.log -append
$servername | out-file -FilePath c:\temp\Test_Script_2.log -append
#Retrieve list of volumes available to restore from
$Volumes = Get-VBRWindowsGuestItem -Session $session[0]
#Show available volumes to restore
$Logvolumes = "Echo available volumes to restore"
Write-output $Logvolumes
Write-output $Volumes
$Logvolumes | out-file -FilePath c:\temp\Test_Script_2.log -append
$Volumes | out-file -FilePath c:\temp\Test_Script_2.log -append
#Stop restore session
Stop-VBRWindowsFileRestore $Result
#Validate restore session is stopped
$RestsessionFinal = Get-VBRRestoreSession | select -first 3
#Show status of restore session - should be stopped
$LogrestessionFinal = "Echo final status of restore session"
Write-Output $LogrestessionFinal
Write-Output $RestsessionFinal
$LogrestessionFinal | out-file -FilePath c:\temp\Test_Script_2.log -append
$RestsessionFinal | out-file -FilePath c:\temp\Test_Script_2.log -append
*************** End - Script contents: Test_Script_2a.ps1 ****************
*************** Start - Log file contents: Test_Script_2.log ****************
Echo value of restorepoint
VM Name Creation Time Type
------- ------------- ----
WebServer1 5/5/2023 12:01:45 AM Increment
Starting file restore
*************** End - Log file contents: Test_Script_2.log ****************
*************** Start - Powershell Transcript file **************************************
Windows PowerShell transcript start
Start time: 20230505093038
Username: Company\usernameA
RunAs User: Company\usernameA
Machine: VeeamServerA (Microsoft Windows NT 6.3.9600.0)
Host Application: C:\Windows\system32\windowspowershell\v1.0\powershell.exe -NoExit . "C:\Program Files\Veeam\Backup and Replication\Console\Initialize-VeeamToolkit.ps1""
Process ID: 3844
PSVersion: 5.1.14409.1018
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.14409.1018
BuildVersion: 10.0.14409.1018
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\Users\usernameA\Documents\PowerShell_transcript.VeeamServerA.NXQ2UlNX.20230505093038.txt
PS C:\scripts> .\Test_Script_2a.ps1 "WebServer1"
WARNING: The names of some imported commands from the module 'Veeam.Backup.PowerShell' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
Echo value of restorepoint
VM Name Creation Time Type
------- ------------- ----
WebServer1 5/5/2023 12:01:45 AM Increment
Starting file restore
PS C:\scripts> TerminatingError(): "System error."
Info : Veeam.Backup.Model.CRestoreSessionInfo
Uid : c1e4b95da2a94bcd950e7e8c9a90dc42
LeaseUid : bcf1cafef9f54bd19a28660be86baccd
Initiator : Veeam.Backup.Model.CBaseSessionInfo+SInitiator
OibId : c8dd103d-7ec6-4893-8625-32e26d7eb310
OibUid : c8dd103d7ec64893862532e26d7eb310
SourcePlatform : EVmware
TargetPlatform : EVmware
Options : <FlrInfo BackupName="WebServer1" OibDT="05/05/2023 00:01:45" MountId="00000000-0000-0000-0000-000000000000"
MountSourceId="00000000-0000-0000-0000-000000000000" IsVbo="False" JobId="00000000-0000-0000-0000-000000000000"
JobType="0"><Data OibId="c8dd103d-7ec6-4893-8625-32e26d7eb310" IsVbrSvcRestoreOwner="False" PermittedExtentions=""
InitiatorName="Company\usernameA" InitiatorSid="S-1-5-21-3771090882-3538679689-3568416434-76188"
ShareCredsId="00000000-0000-0000-0000-000000000000" EsxId="00000000-0000-0000-0000-000000000000" PoolRef=""
FolderRef="" IsWinFlrFromSanSnapshot="False" Reason="Started by Powershell at 5/5/2023 9:31:57 AM." CreatorType="2"
IsEnterpriseRestore="False" CloudConnHostId="00000000-0000-0000-0000-000000000000"
CloudProviderId="00000000-0000-0000-0000-000000000000" GuestCredsId="00000000-0000-0000-0000-000000000000"
IsGuiFlrRequest="False" ComlpeteTaskSessionOnFinished="False" CancelExistingRestoreTask="False"
AppliencePlatform="0" MountHostId="00000000-0000-0000-0000-000000000000" UseHostApiForOriginalVm="False"
OverwriteItems="False"><AppliancePlatform PlatformId="00000000-0000-0000-0000-000000000000" Platform="0"
/></Data></FlrInfo>
StateXml : <StateXml />
RestoreSessionAudit : Veeam.Backup.Core.CRestoreSessionAudit
ItemsRestoreAudit :
ParentIdOrNull :
FileLogger : Veeam.Backup.Core.FileCommanderLogger
RestoreType : SingleRestore
MultiRestoreId : c4d4eee5-c4a9-472d-a43b-6da0a78e20c6
IsPermanent : False
SessionInfo : Veeam.Backup.Model.CRestoreSessionInfo
Id : c1e4b95d-a2a9-4bcd-950e-7e8c9a90dc42
LeaseId : bcf1cafe-f9f5-4bd1-9a28-660be86baccd
JobType : FileLevelRestore
JobName : FLR_[WebServer1]
Name : FLR_[WebServer1]
JobSpec :
JobTypeString : Guest File Restore (Windows)
CreationTime : 5/5/2023 9:32:27 AM
TrackedByVbr : True
CreationTimeUTC : 5/5/2023 9:32:27 AM
Operation :
Description :
BaseProgress : 0
IsCompleted : False
IsWorking : True
IsStarting : False
IsPostprocessing : False
JobId : 9eca9e49-dc55-46a3-974c-32c9d26688bc
JobUid : 9eca9e49-dc55-46a3-974c-32c9d26688bc
Result : None
State : Working
EndTime : 1/1/1900 12:00:00 AM
EndTimeUTC : 1/1/1900 12:00:00 AM
AuxData : <AuxData><SessionStarterInfo Version="1" UserName="usernameA" UserDomainName="META" RunManually="True"
LoginType="4" LoginName="veeamAccount" /></AuxData>
IsLowerAgentPriority : False
LogName : FLR__WebServer1_
LogsSubFolder : FLRSessions\Windows\FLR__WebServer1_
Logger : Veeam.Backup.Core.XmlLogger
Tracer : Veeam.Backup.Core.CSessionLogTracer
Info : Veeam.Backup.Model.CRestoreSessionInfo
Uid : a2b468f57060495ab150e9ea265a3644
LeaseUid : 6c2dd62aab1e48c5a523d02db89b5383
Initiator : Veeam.Backup.Model.CBaseSessionInfo+SInitiator
OibId : e28a909e-1609-4b49-86e9-a32a8d539ba4
OibUid : e28a909e16094b4986e9a32a8d539ba4
SourcePlatform : EVmware
TargetPlatform : EVmware
Options : <FlrInfo BackupName="File Servers" OibDT="05/04/2023 00:02:11" MountId="00000000-0000-0000-0000-000000000000"
MountSourceId="00000000-0000-0000-0000-000000000000" IsVbo="False" JobId="00000000-0000-0000-0000-000000000000"
JobType="0"><Data OibId="e28a909e-1609-4b49-86e9-a32a8d539ba4" IsVbrSvcRestoreOwner="False" PermittedExtentions=""
InitiatorName="Company\usernameA" InitiatorSid="S-1-5-21-3771090882-3538679689-3568416434-76188"
ShareCredsId="00000000-0000-0000-0000-000000000000" EsxId="00000000-0000-0000-0000-000000000000" PoolRef=""
FolderRef="" IsWinFlrFromSanSnapshot="False" Reason="Started by Powershell at 5/5/2023 9:26:31 AM." CreatorType="2"
IsEnterpriseRestore="False" CloudConnHostId="00000000-0000-0000-0000-000000000000"
CloudProviderId="00000000-0000-0000-0000-000000000000" GuestCredsId="00000000-0000-0000-0000-000000000000"
IsGuiFlrRequest="False" ComlpeteTaskSessionOnFinished="False" CancelExistingRestoreTask="False"
AppliencePlatform="0" MountHostId="00000000-0000-0000-0000-000000000000" UseHostApiForOriginalVm="False"
OverwriteItems="False"><AppliancePlatform PlatformId="00000000-0000-0000-0000-000000000000" Platform="0"
/></Data></FlrInfo>
StateXml : <StateXml />
RestoreSessionAudit : Veeam.Backup.Core.CRestoreSessionAudit
ItemsRestoreAudit :
ParentIdOrNull :
FileLogger : Veeam.Backup.Core.FileCommanderLogger
RestoreType : SingleRestore
MultiRestoreId : 4ffc120d-ed8d-49fe-b3f0-f452d5866841
IsPermanent : False
SessionInfo : Veeam.Backup.Model.CRestoreSessionInfo
Id : a2b468f5-7060-495a-b150-e9ea265a3644
LeaseId : 6c2dd62a-ab1e-48c5-a523-d02db89b5383
JobType : FileLevelRestore
JobName : FLR_[WebServer2]
Name : FLR_[WebServer2]
JobSpec :
JobTypeString : Guest File Restore (Windows)
CreationTime : 5/5/2023 9:27:01 AM
TrackedByVbr : True
CreationTimeUTC : 5/5/2023 9:27:01 AM
Operation :
Description :
BaseProgress : 0
IsCompleted : True
IsWorking : False
IsStarting : False
IsPostprocessing : False
JobId : 3bf52556-e828-4b9e-8df6-bbee4d9a33f3
JobUid : 3bf52556-e828-4b9e-8df6-bbee4d9a33f3
Result : Failed
State : Stopped
EndTime : 5/5/2023 9:28:04 AM
EndTimeUTC : 5/5/2023 9:28:04 AM
AuxData : <AuxData><SessionStarterInfo Version="1" UserName="usernameA" UserDomainName="META" RunManually="True"
LoginType="4" LoginName="veeamAccount" /></AuxData>
IsLowerAgentPriority : False
LogName : FLR__WebServer2_
LogsSubFolder : FLRSessions\Windows\FLR__WebServer2_
Logger : Veeam.Backup.Core.XmlLogger
Tracer : Veeam.Backup.Core.CSessionLogTracer
Info : Veeam.Backup.Model.CRestoreSessionInfo
Uid : b449ab634610482282b3aa99fafe7682
LeaseUid : 4d72a46d05e74c6595db34a84e15b14b
Initiator : Veeam.Backup.Model.CBaseSessionInfo+SInitiator
OibId : e28a909e-1609-4b49-86e9-a32a8d539ba4
OibUid : e28a909e16094b4986e9a32a8d539ba4
SourcePlatform : EVmware
TargetPlatform : EVmware
Options : <FlrInfo BackupName="File Servers" OibDT="05/04/2023 00:02:11" MountId="00000000-0000-0000-0000-000000000000"
MountSourceId="00000000-0000-0000-0000-000000000000" IsVbo="False" JobId="00000000-0000-0000-0000-000000000000"
JobType="0"><Data OibId="e28a909e-1609-4b49-86e9-a32a8d539ba4" IsVbrSvcRestoreOwner="False" PermittedExtentions=""
InitiatorName="Company\usernameA" InitiatorSid="S-1-5-21-3771090882-3538679689-3568416434-76188"
ShareCredsId="00000000-0000-0000-0000-000000000000" EsxId="00000000-0000-0000-0000-000000000000" PoolRef=""
FolderRef="" IsWinFlrFromSanSnapshot="False" Reason="Started by Powershell at 5/5/2023 9:17:03 AM." CreatorType="2"
IsEnterpriseRestore="False" CloudConnHostId="00000000-0000-0000-0000-000000000000"
CloudProviderId="00000000-0000-0000-0000-000000000000" GuestCredsId="00000000-0000-0000-0000-000000000000"
IsGuiFlrRequest="False" ComlpeteTaskSessionOnFinished="False" CancelExistingRestoreTask="False"
AppliencePlatform="0" MountHostId="00000000-0000-0000-0000-000000000000" UseHostApiForOriginalVm="False"
OverwriteItems="False"><AppliancePlatform PlatformId="00000000-0000-0000-0000-000000000000" Platform="0"
/></Data></FlrInfo>
StateXml : <StateXml />
RestoreSessionAudit : Veeam.Backup.Core.CRestoreSessionAudit
ItemsRestoreAudit :
ParentIdOrNull :
FileLogger : Veeam.Backup.Core.FileCommanderLogger
RestoreType : SingleRestore
MultiRestoreId : e9dea459-ac0a-47d9-a308-5a8aa2e81ab0
IsPermanent : False
SessionInfo : Veeam.Backup.Model.CRestoreSessionInfo
Id : b449ab63-4610-4822-82b3-aa99fafe7682
LeaseId : 4d72a46d-05e7-4c65-95db-34a84e15b14b
JobType : FileLevelRestore
JobName : FLR_[WebServer2]
Name : FLR_[WebServer2]
JobSpec :
JobTypeString : Guest File Restore (Windows)
CreationTime : 5/5/2023 9:17:33 AM
TrackedByVbr : True
CreationTimeUTC : 5/5/2023 9:17:33 AM
Operation : Operation was canceled by user Company\usernameA
Description :
BaseProgress : 0
IsCompleted : False
IsWorking : False
IsStarting : False
IsPostprocessing : False
JobId : b6bb9396-8a3e-4d93-be33-1a0299efbd00
JobUid : b6bb9396-8a3e-4d93-be33-1a0299efbd00
Result : None
State : Stopping
EndTime : 1/1/1900 12:00:00 AM
EndTimeUTC : 1/1/1900 12:00:00 AM
AuxData : <AuxData><SessionStarterInfo Version="1" UserName="usernameA" UserDomainName="META" RunManually="True"
LoginType="4" LoginName="veeamAccount" /></AuxData>
IsLowerAgentPriority : False
LogName : FLR__WebServer2_
LogsSubFolder : FLRSessions\Windows\FLR__WebServer2_
Logger : Veeam.Backup.Core.XmlLogger
Tracer : Veeam.Backup.Core.CSessionLogTracer
Who is online
Users browsing this forum: No registered users and 8 guests