Archive by category "VEEAM"
Veeam backup copy to multiple offline external disks
Wondering how to create an offline disk back-up copy with more than one USB Disk? And not want to spend your IT budget on “Veeam cloud connect” This is originally not possible with the Veeam GUI because you can’t map 1 backup copy job against 2 USB disks. The job will fail because Veeam cant find one incremental which one is copied on the second USB disk which is on a safe place @home. I made a script for enabling and disabling the right copy job for each mapped USB disk.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 |
<# .SYNOPSIS Veeam offline copy to USB or other External disk. .DESCRIPTION PRE-REQUIREMENT!!: 1 or more usb or external disks. Created repositories and Backup copy jobs in Veeam. This scripts contains 3 Functions 1. Prepare offline media for copying to it. 2. Enable and Disable Veeam jobs. 3. Write logging to file .PARAMETER(s) $DiskId = The diskid which is given in the get partition CMDLet or gui. $TargetDrvLtr = Driveletter where the Veeam repository is mapped to $USBDisklabels = Volumenames $BCopyJob = Backupcopyjobnames $Logfile = Logging the actions to a logfile .INPUTS $PartitionInfo = PartitionStuff -DiskId "usb" -TargetDrvLtr "Z" TheVeeamStuff -PartitionInfo $PartitionInfo -UsbDiskLabel1 "USBDISKLABEL1" -UsbDiskLabel2 "USBDISKLABEL2" -BCopyJob1 "BCOPY1" -BCopyJob2 "BCOPY2" -logfile "C:\PSScripts\VBRTaskLogging.txt" .OUTPUTS Log file stored in C:\.log> .NOTES Version: 1.0 Author: Rob Verhees Creation Date: 13-12-2018 Purpose/Change: Initial script development #> Function PartitionStuff { Param( $DiskId, $TargetDrvLtr ) $drvltr = get-partition | where{$_.DiskId -match $DiskId} IF(!$drvltr){ write-log -Level ERROR -logfile $logfile -Message "Cant find disk with DiskID $($diskid)" } IF($drvltr.DriveLetter -ne $TargetDrvLtr ){ $drvltr | Set-Partition -NewDriveLetter $TargetDrvLtr } Else { write-log -Level INFO -logfile $logfile -Message "TargetDriveletter already present!" } IF($drvltr){ $PartitionInfo = $drvltr | get-volume | select -ExpandProperty filesystemlabel } $PartitionInfo } function LoadVeeamPowerShell { Try { Add-PSSnapin VeeamPSSnapin } Catch { write-log -Level ERROR -logfile $logfile -Message "Cant load Veeam!" Exit } Try { get-vbrserver } Catch { write-log -Level ERROR -logfile $logfile -Message "Change the permissions of the following registry key: \\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\ -> Users full control." write-log -Level ERROR -logfile $logfile -Message ":: Or run this Script as Administator, not recommended when using a scheduled task." Exit } } function TheVeeamStuff { Param ( $PartitionInfo, $UsbDiskLabel1, $UsbDiskLabel2, $BCopyJob1, $BCopyJob2, $logfile ) LoadVeeamPowerShell IF($PartitionInfo -match $UsbDiskLabel1){ Try { Get-VBRBackupRepository -Name $UsbDiskLabel1 | Sync-VBRBackupRepository write-log -Level INFO -logfile $logfile -Message "Syncing repository $($usbdisklabel1)" start-sleep -Seconds 60 Get-VBRJob | where{$_.name -eq $BCopyJob1} | Enable-VBRJob write-log -Level INFO -logfile $logfile -Message ":: Enabling VBRJob $($BCopyJob1)" Get-vbrjob | where{$_.name -eq $BCopyJob2} | Disable-VBRJob write-log -Level INFO -logfile $logfile -Message ":: Disabling VBRJob $($BCopyJob2)" } Catch { write-log -Level ERROR -logfile $logfile -Message "Can't find VBRjob or Repository" write-log -Level ERROR -logfile $logfile -Message ": Errormessage: $($_.exception.message)" Exit } } ELSEIF($PartitionInfo -match $UsbDiskLabel2) { Try { Get-VBRBackupRepository -Name $UsbDiskLabel2 | Sync-VBRBackupRepository write-log -Level INFO -logfile $logfile -Message "Syncing repository $($usbdisklabel2)" start-sleep -Seconds 60 Get-VBRJob | where{$_.name -eq $BCopyJob2} | Enable-VBRJob write-log -Level INFO -logfile $logfile -Message ":: Enabling VBRJob $($BCopyJob2)" Get-vbrjob | where{$_.name -eq $BCopyJob1} | Disable-VBRJob write-log -Level INFO -logfile $logfile -Message ":: Disabling VBRJob $($BCopyJob1)" } Catch { write-log -Level ERROR -logfile $logfile -Message "Can't find VBRjob or Repository" write-log -Level ERROR -logfile $logfile -Message ": Errormessage: $($_.exception.message)" } } Else { write-log -Level ERROR -logfile $logfile -Message "$($Partitioninfo) and the given External disk label does not match each-other." } } Function Write-Log { [CmdletBinding()] Param( [Parameter(Mandatory=$False)] [ValidateSet("INFO","WARN","ERROR","FATAL","DEBUG")] [String] $Level = "INFO", [Parameter(Mandatory=$True)] [string] $Message, [Parameter(Mandatory=$False)] [string] $logfile ) $Stamp = (Get-Date).toString("yyyy/MM/dd HH:mm:ss") $Line = "$Stamp $Level $Message" If($logfile) { if (!(Test-Path $logfile)) { New-Item -path $logfile -type "file" } Add-Content $logfile -Value $Line } Else { Write-Output $Line } } $PartitionInfo = PartitionStuff -DiskId "usb" -TargetDrvLtr "Z" TheVeeamStuff -PartitionInfo $PartitionInfo -UsbDiskLabel1 "USBDISKLABEL1" -UsbDiskLabel2 "USBDISKLABEL2" -BCopyJob1 "BCOPY1" -BCopyJob2 "BCOPY2" -logfile "C:\PSScripts\VBRTaskLogging.txt" |
VEEAM Task failed Error: Exception of type ‘System.OutOfMemoryException’ was thrown
Last week I had the following error when starting a Veeam backup job. I thought my proxy servers where out of memory, so I rebooted them. Then I started the backup jobs again, with no result.
Solution:
To solve this issue you must logoff all the other RDP sessions, which have a disconnected session with the Veeam console open. Alternatively, give the Veeam backup server more resources so there is more memory available.
Exchange backup VEEAM
Veeam Backup and Replication gives the possibility to create a consistent backup from your Exchange farm. This can be a standalone Exchange system or an Exchange DAG cluster. It makes use of the Microsoft Exchange VSS writers inside the VM. The Veeam server creates a RPC connection to the Exchange servers, and place some backup scripts on the /ADMIN$ share. When the backup starts Veeam starts this script which talks to the Microsoft VSS Writers to create a consistent backup.
Enable application aware processing
To create an application aware backup in Veeam you must enable the “Application aware processing” option in the Veeam job properties. Then go to applications for application specific settings. In this tab you can configure VSS, Log and error settings. Configure settings which are suitable for your systems.
User rights Veeam Exchange backup
Select credentials which have full rights (read / write) to all files in the folder with the database.
For direct restore to your exchange farm the user must also have full access to the Mailbox. This user permissions can be set with the following command:
|
1 |
Add-MailboxPermission –Identity “<target_mailbox>” -User “<user_account>” -AccessRights FullAccess –InheritanceType All |
When you have a service account for restoring to all mailboxes you can use Exchange impersonation. This can be set with the following command:
|
1 |
New-ManagementRoleAssignment -Name "Test" -Role ApplicationImpersonation -User "Test User" -CustomRecipientScope "contoso.local/TargetUsers" |
Back-up Exchange DAG Cluster
When you create a backup of an Exchange DAG Cluster node, default all active and passive nodes are available for restore. So theoretically you only have one backup of 1 exchange node.
Tips for creating backup of your Exchange DAG Cluster:
- Backup both of your exchange servers in one backup job, this gives you better dedup results.
- Don’t backup your exchange nodes in separate jobs at the same time, this can cause a failover.
- Veeam backup can cause load on your exchange server, the best situation is to create a new exchange cluster node server with only passive mailboxes.
- When your exchange servers failover during a backup you can increase the failover time of your exchange cluster nodes. Commands for changing the cluster parameters:
|
1 2 3 4 |
cluster /prop SameSubnetDelay=2000:DWORD cluster /prop CrossSubnetDelay=4000:DWORD cluster /prop CrossSubnetThreshold=10:DWORD cluster /prop SameSubnetThreshold=10:DWORD |
Veeam Backup free
Veeam delivers powerful backup software for backup your virtual or psychical servers (veeam endpoint). The backup method for VMWare or Hyper-V virtual systems is agentless. There is no need to install something on the guest system. Veeam Connects to the Hypervisor layer, creates a snapshot, transports this snapshot to a backup repository and saves it. Veeam make use of the Hypervisor API to create a backup. When there is some application installed on the system there is a possibility to create a what they called application aware backup. The Veeam service connects with RPC to the virtual system and make use of the application VSS writers to create a consistent backup.
VEEAM Backup free features:
Veeam Free make use of the VeeamZIP to create ad hoc backups of the virtual machine for operational, portability or archival purposes.
Following features are enabled in the free edition:
– Backup & Restore: Full back up creation and restore.
– VM File recovery: The possibility to restore VM files (vmdk, vmx for example).
– Veeam Explorer: Restore AD, SQL, Exchange or Sharepoint objects.
– Native tape support: copying files to tape drives.
– Backup encryption: Allows you to encrypt the backup files.
Veeam Backup psychical server, client or desktop
Veeam endpoint protection allows you to make use of a stand-alone Windows service for backup of your physical client or server. It does not require a dedicated server or repository’s. You just install the software on each server you want to protect. The windows server makes use of a little local MS SQL DB. It is possible to integrate Veeam endpoint with Veeam Backup and Replication software. This allows you to save your endpoint backup on a Veeam repository.
Note: Veeam Endpoint does not support Application VSS writers yet. So the backup is not Application consistent. But for many situations is a crash consistent enough.
Features Veeam endpoint backup:
– Backup & Recovery: Choose to back up your entire computer, volume or just a couple of maps.
– Scheduler: When do you want that the backup task runs?
– Backup target: Where do you want to place the created backup? When you choose a removable device (USB stick) you can choose to detach the device when ready. This protect the device from ransomware.
– Bitlocker: Veeam endpoint supports bitlocker encrypted drives.
– Create recovery media: In case of a full system crash you can use your created recovery boot USB stick.
– Support: Veeam gives free support, because they want to be the best. Yes this is awesome
Veeam download
Access to the registry key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication’ is denied.
There are two ways to solve this:
1. Run VEEAM PowerShell always as Administrator
2. Change the permissions of the following registry key: \\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\ -> Users full control.
PowerShell Rest API programming
With the PowerShell invoke-restmethod command it’s possible to interact with a REST based API.
In the following script I’ve added a couple of examples how-to interact with methods as GET and POST.
Add VM to VEEAM Portal scope with PowerShell and the VEEAM Rest API
The steps taken in this script:
– Creating a new session with the given credentials.
– Search for the VMid (GET query).
– Search for the right account. (GET query)
– Add VM To portal scope (POST with XML body).
*note: No error/exception handling added, just a beginners script to show howto interact with the VEEAM Rest API with PowerShell.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 |
[CmdletBinding()] param ( [parameter(Mandatory=$true,ValueFromPipeline=$true)] [string[]]$vmname, [parameter(Mandatory=$true,ValueFromPipeline=$true)] [string[]]$account, [parameter(Mandatory=$true,ValueFromPipeline=$true)] [string[]]$uri ) #Example usage #PS_RESTAPI.PS1 -uri 0.0.0.0:9399 -vmname VMTST01 -account TST #Portal credentials $cred = get-credential #Create rest api powershell session $Auth = @{uri = "http://$uri/api/sessionMngr/?v=v1_2"; Method = 'POST'; } Write-host "Created VEEAM Rest API Powershell Session" -ForegroundColor Yellow #Searching for new VM ID wich can add to the new scope, this can take a wile... $AuthXML = Invoke-WebRequest @Auth -Credential $cred Write-host "Searching for VMID...." -ForegroundColor Yellow $Sessions = @{uri = "http://$uri/api/lookup?host=urn%3aveeam%3aHierarchyRoot%3a673b84ce-2d1d-466c-87bc-929694962897&name=$vmname&type=vm"; Method = 'GET'; Headers = @{'X-RestSvcSessionId' = $AuthXML.Headers['X-RestSvcSessionId']; } } $response = invoke-restmethod @Sessions -TimeoutSec 800 $Jobobject = $response.GetElementsByTagName("HierarchyItem") Write-host "Object $vmname with ID $($jobobject.objectref) is found" -ForegroundColor Yellow #search for the right user scope $accounts = @{uri = "http://$uri/api/security/accounts"; Method = 'GET'; Headers = @{'X-RestSvcSessionId' = $AuthXML.Headers['X-RestSvcSessionId']; } } [xml]$accountinv = invoke-restmethod @accounts $accounts = $accountinv.GetElementsByTagName("Ref") $finalaccount = $accounts | where{$_.Name -match $account} | select -ExpandProperty href $hieraobj = $Jobobject.objectref $body = @" <?xml version="1.0" encoding="utf-8"?> <HierarchyScopeCreateSpec xmlns="http://www.veeam.com/ent/v1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HierarchyScopeItem> <HierarchyObjRef>$hieraobj</HierarchyObjRef> <ObjectName>$vmname</ObjectName> </HierarchyScopeItem> </HierarchyScopeCreateSpec> "@ $headers["Content-Type"] = "application/xml" $portalhref = $finalaccount + "/scopes" $addvm = @{Method = 'POST'; Headers = @{'X-RestSvcSessionId' = $AuthXML.Headers['X-RestSvcSessionId']; 'content-type' = 'application/xml'; } } invoke-restmethod @addvm -Body $body -uri $portalhref Write-host "Object $vmname is add to $($finalaccount.name) " -ForegroundColor Yellow |
Add VM to VEEAM Backup job using PowerShell
I created a simple PowerShell function to add VM’s in a VEEAM backup job. This script has 2 options, enable indexing and/or application aware processing per object.
There are many more possibilities to add functionality. For now, it fits our needs. If you have some feature requests, please comment below.
It can be used by VMWare and Hyper-v users; it checks the hypervisor in the beginning.
Run this script on a VEEAM VBR Server.
Together we can improve this PowerShell function, don’t hesitate to comment.
Deleted some bugs 23-01-2017
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 |
<# .EXAMPLE First, import the function with the following command: C:\PS> . .\PS_AddVMJob Second C:\PS> ps_addvmjob -vmname NAME -Application y -Indexing y .HYPERVISOR This script can be used by VMWare and Hyper-v users, it uses commands from both hypervisors .VERION Tested with VEEAM B&R V8 and V9.5 2.0 .NOTES Author: Rob Verhees Date created: 23-1-2017 PowerShell beginner #> function PS_AddVMJob { [CmdletBinding()] param ( [parameter(Mandatory=$true,ValueFromPipeline=$true)] [string]$vmname, [parameter(Mandatory=$true,ValueFromPipeline=$true)] [ValidateSet("y","n")] [string]$application, [parameter(Mandatory=$true,ValueFromPipeline=$true)] [ValidateSet("y","n")] [string]$indexing ) Begin { If ((Get-PSSnapin -Name VeeamPSSnapin -ErrorAction SilentlyContinue) -eq $null) {add-pssnapin VeeamPSSnapin} #File indexing $Excludedfolders = @("%windir%","%ProgramFiles%","%ProgramFiles(x86)%","%ProgramW6432%","%TEMP%") #Determine the Hypervisor type $VBRServerType = Get-VBRServer | where{$_.type -match "esxi" -or $_.type -match "HvServer"} | Select -ExpandProperty Type -Last 1 } Process{ #Get VBRJobs and create a menu $jobs = Get-VBRjob | where{$_.JobType -eq 'Backup'} $menu = @{} for ($i=1;$i -le $jobs.count; $i++) { Write-Host "$i. $($jobs[$i-1].name)" $menu.Add($i,($jobs[$i-1].name)) } [int]$ans = Read-Host 'Kies back-up job:' $selection = $menu.Item($ans) $jobname = get-vbrjob -name $selection #Add VM in VBRjob Hyper-V IF($VBRServerType -match "HvServer"){ $newvm = Find-VBRHvEntity -name $vmname IF(!$newvm){ Write-host "No vm found with the name: $vmname" -foreground "red" Return } Add-VBRHvJobObject -Job $jobname -Entities $newvm } #Add VM in VBRjob VMWare ELSEIF($VBRServerType -match "ESX"){ $newvm = Find-VBRViEntity -name $vmname IF(!$newvm){ Write-host "No vm found with the name: $vmname" -foreground "red" Return } Add-VBRViJobObject -Job $jobname -Entities $newvm } ELSE{ Write-host "VBRServerType $VBRServerType not recognized" -Foreground "red" Return } #Get Job object $jobobject = $jobname | Get-VBRJobObject | where{$_.name -match $newvm.name} IF($Application -match "y" -and $indexing -match "y"){ $vssjoboptions = Get-VBRJobVssOptions -job $jobname.name IF($vssjoboptions.enabled -match "false"){ $vssjoboptions.enabled = $true Set-VBRJobVssOptions -Options $vssjoboptions -Job $jobname $jobobjects = Get-VBRJobObject -Job $jobname Foreach($obj in $jobobjects){ $vssobjoptions = Get-VBRJobObjectVssOptions -ObjectInJob $obj $vssobjoptions.enabled = $false set-vbrjobobjectvssoptions -Options $vssobjoptions -object $obj } } IF($vssjoboptions.GuestFSIndexingType -match "none"){ $vssjoboptions.GuestFSIndexingType = "ExceptSpecifiedFolders" Set-VBRJobVssOptions -Options $vssjoboptions -Job $jobname $jobobjects1 = Get-VBRJobObject -Job $jobname Foreach($obj1 in $jobobjects1){ $vssobjoptions = Get-VBRJobObjectVssOptions -ObjectInJob $obj1 $vssobjoptions.GuestFSIndexingType = "None" set-vbrjobobjectvssoptions -Options $vssobjoptions -object $obj1 } } $vssobjectoptions = Get-VBRJobObjectVssOptions -ObjectInJob $jobobject $vssobjectoptions.enabled = $true $vssobjectoptions.IgnoreErrors = $true $vssobjectoptions.SqlBackupOptions.TransactionLogsProcessing = "TruncateonlyonSuccessJob" $vssobjectoptions.ExchangeBackupOptions.TransactionLogsProcessing = "TruncateonlyonSuccessJob" $vssobjectoptions.GuestFSIndexingType = "ExceptSpecifiedFolders" $vssobjectoptions.ExcludedIndexingFolders = $Excludedfolders set-vbrjobobjectvssoptions -Options $vssobjectoptions -object $jobobject } IF($Application -match "y" -and $indexing -match "n"){ $vssjoboptions = Get-VBRJobVssOptions -job $jobname.name IF($vssjoboptions.enabled -match "false"){ $vssjoboptions.enabled = $true Set-VBRJobVssOptions -Options $vssjoboptions -Job $jobname $jobobjects = Get-VBRJobObject -Job $jobname Foreach($obj in $jobobjects){ $vssobjoptions = Get-VBRJobObjectVssOptions -ObjectInJob $obj $vssobjoptions.enabled = $false set-vbrjobobjectvssoptions -Options $vssobjoptions -object $obj } } $vssobjectoptions = Get-VBRJobObjectVssOptions -ObjectInJob $jobobject $vssobjectoptions.enabled = $true $vssobjectoptions.GuestFSIndexingType = "none" $vssobjectoptions.IgnoreErrors = $true $vssobjectoptions.SqlBackupOptions.TransactionLogsProcessing = "TruncateonlyonSuccessJob" $vssobjectoptions.ExchangeBackupOptions.TransactionLogsProcessing = "TruncateonlyonSuccessJob" Set-vbrjobobjectvssoptions -Options $vssobjectoptions -object $jobobject } IF($Application -match "n" -and $indexing -match "y"){ $vssjoboptions = Get-VBRJobVssOptions -job $jobname.name IF($vssjoboptions.GuestFSIndexingType -match "none"){ $vssjoboptions.GuestFSIndexingType = "ExceptSpecifiedFolders" Set-VBRJobVssOptions -Options $vssjoboptions -Job $jobname $jobobjects1 = Get-VBRJobObject -Job $jobname Foreach($obj1 in $jobobjects1){ $vssobjoptions = Get-VBRJobObjectVssOptions -ObjectInJob $obj1 $vssobjoptions.GuestFSIndexingType = "None" set-vbrjobobjectvssoptions -Options $vssobjoptions -object $obj1 } } $vssobjectoptions = Get-VBRJobObjectVssOptions -ObjectInJob $jobobject $vssobjectoptions.GuestFSIndexingType = "ExceptSpecifiedFolders" $vssobjectoptions.Enabled = $false $vssobjectoptions.ExcludedIndexingFolders = $Excludedfolders Set-vbrjobobjectvssoptions -Options $vssobjectoptions -object $jobobject } IF($Application -match "n" -and $indexing -match "n"){ $vssobjectoptions = Get-VBRJobObjectVssOptions -ObjectInJob $jobobject $vssobjectoptions.GuestFSIndexingType = "none" $vssobjectoptions.Enabled = $false set-vbrjobobjectvssoptions -Options $vssobjectoptions -object $jobobject } IF($Application -match "y" -and $indexing -match "y"){ $vssjoboptions = Get-VBRJobVssOptions -job $jobname.name IF($vssjoboptions.enabled -match "false"){ $vssjoboptions.enabled = $true Set-VBRJobVssOptions -Options $vssjoboptions -Job $jobname $jobobjects = Get-VBRJobObject -Job $jobname Foreach($obj in $jobobjects){ $vssobjoptions = Get-VBRJobObjectVssOptions -ObjectInJob $obj $vssobjoptions.enabled = $false set-vbrjobobjectvssoptions -Options $vssobjoptions -object $obj } } IF($vssjoboptions.GuestFSIndexingType -match "none"){ $vssjoboptions.GuestFSIndexingType = "ExceptSpecifiedFolders" Set-VBRJobVssOptions -Options $vssjoboptions -Job $jobname $jobobjects1 = Get-VBRJobObject -Job $jobname Foreach($obj1 in $jobobjects1){ $vssobjoptions = Get-VBRJobObjectVssOptions -ObjectInJob $obj1 $vssobjoptions.GuestFSIndexingType = "None" set-vbrjobobjectvssoptions -Options $vssobjoptions -object $obj1 } } $vssobjectoptions = Get-VBRJobObjectVssOptions -ObjectInJob $jobobject $vssobjectoptions.enabled = $true $vssobjectoptions.IgnoreErrors = $true $vssobjectoptions.SqlBackupOptions.TransactionLogsProcessing = "TruncateonlyonSuccessJob" $vssobjectoptions.ExchangeBackupOptions.TransactionLogsProcessing = "TruncateonlyonSuccessJob" $vssobjectoptions.GuestFSIndexingType = "ExceptSpecifiedFolders" $vssobjectoptions.ExcludedIndexingFolders = $Excludedfolders set-vbrjobobjectvssoptions -Options $vssobjectoptions -object $jobobject } IF($Application -match "y" -and $indexing -match "n"){ $vssjoboptions = Get-VBRJobVssOptions -job $jobname.name IF($vssjoboptions.enabled -match "false"){ $vssjoboptions.enabled = $true Set-VBRJobVssOptions -Options $vssjoboptions -Job $jobname $jobobjects = Get-VBRJobObject -Job $jobname Foreach($obj in $jobobjects){ $vssobjoptions = Get-VBRJobObjectVssOptions -ObjectInJob $obj $vssobjoptions.enabled = $false set-vbrjobobjectvssoptions -Options $vssobjoptions -object $obj } } $vssobjectoptions = Get-VBRJobObjectVssOptions -ObjectInJob $jobobject $vssobjectoptions.enabled = $true $vssobjectoptions.GuestFSIndexingType = "none" $vssobjectoptions.IgnoreErrors = $true $vssobjectoptions.SqlBackupOptions.TransactionLogsProcessing = "TruncateonlyonSuccessJob" $vssobjectoptions.ExchangeBackupOptions.TransactionLogsProcessing = "TruncateonlyonSuccessJob" Set-vbrjobobjectvssoptions -Options $vssobjectoptions -object $jobobject } IF($Application -match "n" -and $indexing -match "y"){ $vssjoboptions = Get-VBRJobVssOptions -job $jobname.name IF($vssjoboptions.GuestFSIndexingType -match "none"){ $vssjoboptions.GuestFSIndexingType = "ExceptSpecifiedFolders" Set-VBRJobVssOptions -Options $vssjoboptions -Job $jobname $jobobjects1 = Get-VBRJobObject -Job $jobname Foreach($obj1 in $jobobjects1){ $vssobjoptions = Get-VBRJobObjectVssOptions -ObjectInJob $obj1 $vssobjoptions.GuestFSIndexingType = "None" set-vbrjobobjectvssoptions -Options $vssobjoptions -object $obj1 } } $vssobjectoptions = Get-VBRJobObjectVssOptions -ObjectInJob $jobobject $vssobjectoptions.GuestFSIndexingType = "ExceptSpecifiedFolders" $vssobjectoptions.Enabled = $false $vssobjectoptions.ExcludedIndexingFolders = $Excludedfolders Set-vbrjobobjectvssoptions -Options $vssobjectoptions -object $jobobject } IF($Application -match "n" -and $indexing -match "n"){ $vssobjectoptions = Get-VBRJobObjectVssOptions -ObjectInJob $jobobject $vssobjectoptions.GuestFSIndexingType = "none" $vssobjectoptions.Enabled = $false set-vbrjobobjectvssoptions -Options $vssobjectoptions -object $jobobject } } } |
Veeam exclude disks using PowerShell
When you have multiple jobs with many VMs it’s a boring task to change all the disk exclusions by hand. That’s why VEEAM have made a nice PowerShell module to automate this boring tasks.
Excluded disks are displayed with numbers, the numbers in Hyper-V are different (because of the IDE disks) then how the numbers are showed in VMWare.
Since Veeam 9.5 Update 4 the diskfilter mechanism in Veeam is changed.
Now we can report both.. SCSI Controller id and the Keynumber as we known earlier.
This means the PowerShell CMDLets also Changed.
Report diskfilter:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
#Load VEEAM PowerShell Module Add-PSSnapin "VeeamPSSnapIn" -ErrorAction SilentlyContinue #Get all VEEAM Diskfilter data $jobs = get-vbrjob $data = @() foreach ($job in $jobs) { $data += $job | Get-VBRJobObject | select name, @{label="Diskfilter";expression={$_.diskfilter.disks}} } #Export to CSV $data | export-csv C:\DiskExclusion.csv |
Change diskfilter:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 |
Add-PSSnapin "VeeamPSSnapIn" -ErrorAction SilentlyContinue $job = get-vbrjob -Name "TST" $jobobjects = $job.GetObjectsInJob() Foreach($jobobject in $jobobjects){ $DiskArray = @() $DKeys = "2000","2001","3000","3001" foreach($Dkey in $Dkeys){ $VDiskKey = [Veeam.Backup.Model.VDiskKey]::New($DKey) $DiskArray += [Veeam.Backup.Model.CDiskKeyInfo]::CreateDiskInfo($VDiskKey) } $CDiskFilterInfo = [Veeam.Backup.Model.CDiskFilterInfo]::CreateSelectedDisks($DiskArray) $VSSOptions = $jobobject.vssoptions $JobInfoType = $jobobject.info.Type $jobobject.Update($VSSOptions,$CDiskFilterInfo,$true,$JobInfoType) } |
Change diskfilter before 9.5 Update 4
See the current excluded disks and the numbers with this script (Run as Administrator):
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
#Load VEEAM PowerShell Module Add-PSSnapin "VeeamPSSnapIn" -ErrorAction SilentlyContinue #Get all VEEAM Diskfilter data $jobs = get-vbrjob $data = @() foreach ($job in $jobs) { $data += $job | Get-VBRJobObject | select name, diskfilter } #Export to CSV $data | export-csv C:\DiskExclusion.csv |
Change the disks exclusions with PowerShell (Run as Administrator):
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
#Load VEEAM Powershell module Add-PSSnapin "VeeamPSSnapIn" -ErrorAction SilentlyContinue #Get all objects in VEEAM Back-up job $objects = Get-VBRJob -name "TEST" | Get-VBRJobObject #$a is the default parameter #$b are the SCSI IDs in number format $a = "Verb8|" $b = "2000;2001;2002;2003" $disks = $a + $b #Change the disk exclusion for each object in the job Foreach($o in $objects){ $objInfo = $o.info $objInfo.diskFilter = $disks [Veeam.Backup.Core.CObjectInJob]::Update($objInfo) $locatie = $o.Name Write-host "Back-up diskconfig changed on VM: $locatie" } |
Comments are welcome.
Task failed. Failed to expand object. Error: Object was not found
Task failed. Failed to expand object. Error: Object was not found
Change VM ID VEEAM database.
In my case I had to replace the old VM id with the new one.
There are multiple reasons why the VMID is changed. This can be caused by exporting and importing the VM for example. When this situation occurred you get the following error in VEEAM:
“Task failed. Failed to expand object. Error: Object was not found”
If you don’t want to add the new object and creating a new full back-up of the VM. You can change the VM ID in the database.
When this is done the forward incremental runs as before.
First we need to determine the OLD id where VEEAM is looking for.
This can be done with the following lines SQL Query against your VEEAM DB:
Get old object ID before Veeam version 9.5
|
1 2 3 4 5 |
SELECT bo.object_name, bo.object_id, bo.path FROM bjobs bj INNER JOIN ObjectsInJobs oij ON bj.id = oij.job_id INNER JOIN BObjects bo ON bo.id = oij.object_id WHERE bj.Name = 'VMJOBNAME' and bj.type=0 |
Get old object ID Veeam 9.5
|
1 2 3 |
SELECT Objectsinjobs.location, bobjects.object_id FROM BObjects INNER JOIN ObjectsInJobs ON ObjectsInJobs.object_id = BObjects.id where ObjectsInJobs.location like '%VMNAME%'; |
The following step is to get the new VMID from Hyper-V or VMWare.
With Hyper-V Virtual Machines Manager (SCVMM) PowerShell Module.
Run PowerShell as Administrator:
|
1 2 |
import-module virtualmachinemanager Get-VM VMNAME | ft name, ID |
With VMWare can this be done with PowerCLI on the ESX host.
Excuse me when I’m wrong, but I think:
|
1 |
get-vm | select name, Id |
SQL Query:
Put the new ID by SET.
Put the old ID by WHERE.
|
1 2 3 |
UPDATE bobjects SET [object_id] = '###' WHERE [object_id] = '###' |
*Tested with VEEAM Backup & Replication 8
CSV IO Paused during Back-up
Finally there are hotfixes for the annoying CSV IO Paused during the back-up. The issue mostly occurs when multiple CSV VSS Snapshots are initiated. I’ve tested the hotfixes in my test envoirement and the issues seems to be gone now.
The components:
KB3090343 https://support.microsoft.com/en-us/kb/3090343
Component: Clussvc.exe
Resolves an issue when multiple VSS backups are in progress, the cluster service may crash because of inconsistent state in the CSV VSS provider.
KB3060678 https://support.microsoft.com/en-us/kb/3060678
Component: Volsnap.sys
Resolves an issue where unneeded snapshots may not be deleted after a backup is completed. This prevents future backups from failing due to a lack of free space consumed by snapshots.
KB3063283 https://support.microsoft.com/en-us/kb/3063283
Component: Hyper-v Integration Services
Increases the time-out to detect the volumes to shadow copy when the Guest OS has multiple volumes.
KB3072380 https://support.microsoft.com/en-us/kb/3072380
Component: Rdvgpuinfo.dll / Vmms.exe
Resolves an issue on a Hyper-V cluster where the heartbeat component times out during a long-running snapshot. The snapshot fails and the VM restarts.
The full list of Microsoft Cluster Hotfixes:
https://support.microsoft.com/en-us/kb/2920151
Recent Comments