Downloads:

1,268

Downloads of v 10.0.1.4854:

381

Last Update:

01 Aug 2020

Package Maintainer(s):

Software Author(s):

  • Veeam Software AG

Tags:

veeam-backup-and-replication-server veeam server admin

Veeam Backup & Replication Server

10.0.1.4854 | Updated: 01 Aug 2020

Downloads:

1,268

Downloads of v 10.0.1.4854:

381

Maintainer(s):

Software Author(s):

  • Veeam Software AG

Veeam Backup & Replication Server 10.0.1.4854

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test


Validation Testing Passed


Verification Testing Exempt:

The package has a number of dependent packages that require a reboot.

To install Veeam Backup & Replication Server, run the following command from the command line or from PowerShell:

>

To upgrade Veeam Backup & Replication Server, run the following command from the command line or from PowerShell:

>

To uninstall Veeam Backup & Replication Server, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade veeam-backup-and-replication-server -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade veeam-backup-and-replication-server -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure veeam-backup-and-replication-server installed
  win_chocolatey:
    name: veeam-backup-and-replication-server
    state: present
    version: 10.0.1.4854
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'veeam-backup-and-replication-server' do
  action    :install
  version  '10.0.1.4854'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: veeam-backup-and-replication-server,
    Version: 10.0.1.4854,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller veeam-backup-and-replication-server
{
   Name     = 'veeam-backup-and-replication-server'
   Ensure   = 'Present'
   Version  = '10.0.1.4854'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'veeam-backup-and-replication-server':
  provider => 'chocolatey',
  ensure   => '10.0.1.4854',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install veeam-backup-and-replication-server version="10.0.1.4854" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 01 Aug 2020.

Description

Exit when reboot detected

When installing / upgrading these packages, I would like to advise you to enable this feature choco feature enable -n=exitOnRebootDetected

Industry-leading backup, recovery and replication software

Veeam® Backup & Replication™ helps businesses achieve comprehensive data protection for ALL workloads — virtual, physical and cloud-based workloads. With a single console, achieve fast, flexible and reliable backup, recovery and replication of all applications and data.

NOTE You do have to install a SQL Server before you can use this package.

To have choco remember parameters on upgrade, be sure to set choco feature enable -n=useRememberedArgumentsForUpgrades.

Package Parameters

The package accepts the following optional parameters:

  • /nfsDatastoreLocation - Specifies the vPower cache folder to which the write cache will be stored. By default, Veeam Backup & Replication uses the folder on a volume with the maximum amount of free space, for example, C:\ProgramData\Veeam\Backup\NfsDatastore.
  • /backupPort - Specifies a TCP port that will be used by the Veeam Backup Service. By default, port number 9392 is used.
  • /mountserverPort - Specifies a port used for communication between the mount server and the backup server. By default, port 9401 is used.
  • /licenseFile - Specifies a full path to the license file. If you do not specify this parameter, Veeam Backup & Replication will operate in the Community Edition mode.
  • /sqlServer - Specifies a Microsoft SQL server and instance on which the configuration database will be deployed. By default, Veeam Backup & Replication uses the (local)\VEEAMSQL2012 server for machines running Microsoft Windows 7, Microsoft Windows Server 2008 or Microsoft Windows Server 2008 R2, and (local)\VEEAMSQL2016 for machines running Microsoft Windows Server 2012 or later.
  • /sqlDatabase - Specifies a name for the configuration database. By default, the configuration database is deployed with the VeeamBackup name.
  • /sqlAuthentication - Specifies if you want to use the SQL Server authentication mode to connect to the Microsoft SQL Server where the Veeam Backup & Replication configuration database is deployed. Specify if you want to use the SQL Server authentication mode. If you do not specify this parameter, Veeam Backup & Replication will connect to the Microsoft SQL Server in the Microsoft Windows authentication mode.
  • /sqlUsername - This parameter must be used if you have specified the /sqlAuthentication parameter. Specifies a LoginID to connect to the Microsoft SQL Server in the SQL Server authentication mode.
  • /sqlPassword - This parameter must be used if you have specified the /sqlAuthentication parameter. Specifies a password to connect to the Microsoft SQL Server in the SQL Server authentication mode.
  • /username - Specifies the account under which the Veeam Backup Service will run. The account must have full control NTFS permissions on the VBRCatalog folder where index files are stored and the Database owner rights for the configuration database on the Microsoft SQL Server where the configuration database is deployed. If you do not specify this parameter, the Veeam Backup Service will run under the Local System account.
  • /password - This parameter must be used if you have specified the /username parameter. Specifies a password for the account under which the Veeam Backup Service will run.
  • /create - Create the requested user on this machine, this user will be added to the local Administrators group.

Example: choco install veeam-backup-and-replication-server --params "/port:9000 /nfsDatastoreLocation:D:\ProgramData\Veeam\Backup\NfsDatastore\"

Please Note: This is an automatically updated package. If you find it is
out of date by more than a day or two, please contact the maintainer(s) and
let them know the package is no longer updating correctly.


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$isoPackageName = 'veeam-backup-and-replication-iso'
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$filename = 'VeeamBackup&Replication_10.0.1.4854.iso'
$installPath = Join-Path  (Join-Path $commonPath $isoPackageName) $filename

$fileLocation = 'Backup\Server.x64.msi'
$updateFileVersion = ($filename -replace 'VeeamBackup&Replication_' -replace '.iso').ToLower()
$updateFileLocation = "Updates\veeam_backup_$($updateFileVersion)_setup.exe"

$pp = Get-PackageParameters

$silentArgs = ""

if ($pp.nfsDatastoreLocation) {
  $silentArgs += " VBR_NFSDATASTORE=`"$($pp.nfsDatastoreLocation)`""
  if(!(Test-Path -Path $pp.nfsDatastoreLocation )){
    New-Item -Path $pp.nfsDatastoreLocation -ItemType Directory
  }
}

if ($pp.backupPort) {
  $silentArgs += " VBR_SERVICE_PORT=$($pp.backupPort)"
}

if ($pp.mountserverPort) {
  $silentArgs += " VBR_SECURE_CONNECTIONS_PORT=$($pp.mountserverPort)"
}

if ($pp.mountserverPort) {
  $silentArgs += " VBR_SECURE_CONNECTIONS_PORT=$($pp.mountserverPort)"
}

if ($pp.sqlServer) {
  $silentArgs += " VBR_SQLSERVER_SERVER=$($pp.sqlServer)"
}

if ($pp.sqlDatabase) {
  $silentArgs += " VBR_SQLSERVER_DATABASE=$($pp.sqlDatabase)"
}

if ($pp.sqlAuthentication) {
  if(-not $pp.sqlPassword -or -not $pp.sqlUsername) {
    throw 'sqlUsername and sqlPassword are required when using sqlAuthentication...'
  }
  $silentArgs += " VBR_SQLSERVER_AUTHENTICATION=$($pp.sqlAuthentication) VBR_SQLSERVER_USERNAME=`"$($pp.sqlUsername)`" VBR_SQLSERVER_PASSWORD=`"$($pp.sqlPassword)`""
}

if ($pp.username) {
  $computername = $env:computername
  $fulluser = $pp.username
  if ($pp.username -notmatch "\\") {
    $fulluser = "$($computername)\$($pp.username)"
  }
  if(-not $pp.password) {
    throw 'Password is required when setting a username...'
  }
  if ($pp.create) {
    if ($pp.username -match "\\") {
      throw "Only local users can be created"
    }

    if (Get-WmiObject -Class Win32_UserAccount | Where-Object {$_.Name -eq $pp.username}) {
      Write-Warning "The local user already exists, not creating again"
    } else {
      net user $pp.username $pp.password /add /PASSWORDCHG:NO
      wmic UserAccount where ("Name='{0}'" -f $pp.username) set PasswordExpires=False
      net localgroup "Administrators" $pp.username /add    }
  }
  $silentArgs += " VBR_SERVICE_USER=`"$($fulluser)`" VBR_SERVICE_PASSWORD=`"$($pp.password)`""
}

if ($pp.licenseFile) {
  if(!(Test-Path -Path $pp.licenseFile )){
    throw "Invalid license file provided"
  }
  $silentArgs += " VBR_LICENSE_FILE=$($pp.licenseFile)"
}



$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  isoFile        = $installPath
  softwareName  = 'Veeam Backup & Replication Server*'
  file           = $fileLocation
  fileType       = 'msi'
  silentArgs     = "$($silentArgs) VBR_AUTO_UPGRADE=1 ACCEPTEULA=YES ACCEPT_THIRDPARTY_LICENSES=1 /qn /norestart /l*v `"$env:TEMP\$env:ChocolateyPackageName.$env:ChocolateyPackageVersion.log`""
  validExitCodes = @(0,1638,1641,3010) #1638 was added to allow updating when an newer version is already installed.
  destination    = $toolsDir
}

Install-ChocolateyIsoInstallPackage @packageArgs

# An update file is provided in the ISO. This should be executed after
# the installation of the software.
# This update file contains an update to all available software on the
# ISO and should be executed After each installation.
#
# This should be in a seperate package, but you can't trigger / force a
# dependency after the installation Therefore I need to trigger it this way.
If ($filename -Match "Update") {
  $updatePackageArgs = @{
    packageName    = $env:ChocolateyPackageName
    isoFile        = $installPath
    softwareName   = $packageArgs['softwareName']
    file           = $updateFileLocation
    fileType       = 'exe'
    silentArgs     = "VBR_AUTO_UPGRADE=1 /silent /noreboot /log `"$env:TEMP\$env:ChocolateyPackageName.$env:ChocolateyPackageVersion.log`""
    validExitCodes = @(0,1641,3010)
    destination    = $toolsDir
  }

  Install-ChocolateyIsoInstallPackage @updatePackageArgs
}

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Veeam Backup & Replication Server 10.0.0.4461 514 Tuesday, February 18, 2020 Approved
Veeam Backup & Replication Server 9.5.4.2866 255 Friday, September 6, 2019 Approved
Veeam Backup & Replication Server 9.5.4.2753 118 Friday, July 5, 2019 Approved
Discussion for the Veeam Backup & Replication Server Package

Ground Rules:

  • This discussion is only about Veeam Backup & Replication Server and the Veeam Backup & Replication Server package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Veeam Backup & Replication Server, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus