Over the course of this series I'll walk thru my process of scripting these steps, provide the updated script and notate any issues I encounter.
This Veeam KB has 4 steps and we'll automate them in the order listed the KB. So with no further delay the first step is: Gathering Veeam Agent Guest Logs.
I wrote the following PowerShell script to do just that:
1 2 3 4 5 6 7 | $ProgramDataLocation = (Get-ChildItem env:programdata).Value $EndpointPath = Join-Path -path $ProgramDataLocation -ChildPath "\veeam\endpoint" $ServerName = (Get-ChildItem env:computername).Value $Date = Get-Date -Format FileDate $EndpointDestination = ("C:\veeam\logs\" + $Date + "_" + $ServerName + "_endpoint.zip") Compress-Archive -Path $EndpointPath -DestinationPath $EndpointDestination -CompressionLevel Optimal |
Line 1: defines the variable $ProgramDataLocation, which finds the environment variable "programdata" location, and returns the value of that object to the variable.
Line 2: defines the location of the Veeam Endpoint folder by joining the location specified in line one, with the standard folder structure specified by Veeam.
Line 3: defines the variable $ServerName, which finds the environment variable "computername", and returns the value of that object to the variable.
Line 4: defines the variable $Date, by using the module Get-Date and storing that date in the YYYYMMDD format.
Line 5: defines the variable $EndpointDestination, which will be the location for the archived/zipped folder to upload to Veeam.
Line 6: whitespace for formatting.
Line 7: Runs the Compress-Archive module specifying the input path as the variable $EndpointPath (defined in line 2), and the destination path as the $EndpointDestination (defined in line 5), further specifying the compression level as maximum.
And if I run this script I am currently encountering the current error: ZipArchiveHelper : The process cannot access the file 'C:\ProgramData\veeam\endpoint\Endpoint.Transport.log' because it is being used by another process.
So in the next blog post we'll determine how to address this issue and modify the script to accommodate it.
No comments:
Post a Comment