Skip to content

Latest commit

 

History

History
130 lines (90 loc) · 4.96 KB

README.md

File metadata and controls

130 lines (90 loc) · 4.96 KB

Veeam Boxstarter templates

Version Released GitHub Releases (all releases)

This repository allows you to install different Veeam software configurations depending on your requirements.

Step 1: Download repository.

  • Download latest stable release of this repository and extract it to a local folder (recommended).
  • Download latest unstable commit of this repository and extract it to a local folder.

Step 2: Install Chocolatey and BoxStarter

Run the following commands in an Elevated powershell.

Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))

For more information regarding the installation of Chocolatey please have a look at their documentation

choco install Boxstarter

For more information about installing BoxStarter have a look at their documentation

Step 3: Configure settings.

NOTE: Only required for the vbr_scripts folder.

Edit the settings.ps1 file and change the settings you want to change.

Step 4: Run BoxStarter

Depending on the function of the machine you are running this on, you can use several scripts.

VBR Scripts

Script Function
vbr_all.ps1 Install all the VBR packages
vbr_sql_express.ps1 Install an SQL Express
vbr_server.ps1 Install Veeam Backup & Replication server
vbr_management.ps1 Install Veeam Backup & Replication management console, including the explorers
vbr_proxy.ps1 Install Veeam Backup & Replication proxy server (soon)
vbr_repository.ps1 Install Veeam Backup & Replication repository server (soon)

VBM Scripts


⚠️ The filenames still have the old VBO name for backward compatibility.


Script Function
vbo_all.ps1 Install all the VBO packages
vbo_server.ps1 Install Veeam Backup for o365 server
vbo_management.ps1 Install Veeam Backup for o365 management console, including the explorers

VONE Scripts

Script Function
vone_all.ps1 Install all the VONE packages
vone_sql_express.ps1 Install an SQL Express
vone_agent.ps1 Install Veeam ONE agent (e.g. on VBR Server)
vone_server.ps1 Install Veeam ONE server
vone_management.ps1 Install Veeam ONE Monitor Client
vone_webui.ps1 Install Veeam ONE Reporter WebUI

Example:

BoxStarter.bat c:\path\to\my\vbr_scripts\vbr_all.ps1

Vagrant

For testing purposes, I have added a Vagrantfile in this repository.

This is tested with the following setup:

  • Windows 10, Version 1909 (Probably any OS compatible with Vagrant v2.1.5 and VirtualBox v5.2.36 should work.)

  • Vagrant v2.1.5:

    choco install vagrant --version=2.1.5
  • VirtualBox v5.2.36:

    choco install virtualbox --version=5.2.36
  • StefanScherer/windows_2016 box based on his packer templates.

  • Run vagrant up to boot the Vagrant box.

Additional notes

  • If required, put your packages in the packages folder.
  • The contents of this directory will be copied to c:\temp
  • The contents of the packages folder will be available in c:\packages

vbr_all.ps1 Vagrant only (Full VBR PoC setup)

  • Put a license file inside the packages folder.
  • In the settings.ps1 file:
    • Change $vbr_licenseFile to 'c:\packages\myfile.lic'
    • Change $vbr_sqlServer to 'VAGRANT\SQLEXPRESS'
    • Change $vbr_username to 'vagrant'
    • Change $vbr_password to 'vagrant'

After you have installed these packages, you can continue with step 2 above.

vone_all.ps1 Vagrant only (Full VONE PoC setup)

  • Put a license file inside the packages folder.
  • In the settings.ps1 file:
    • Change $vone_vcSelectedType to 2 (skip the virtual infrastructure configuration)
    • Change $vone_backupAddLater to 1 (skip the add of VBR to VONE)
    • Change $vone_licenseFile to 'c:\packages\myfile.lic'
    • Change $vone_sqlServer to 'VAGRANT\SQLEXPRESS'
    • Change $vone_username to 'vagrant'
    • Change $vone_password to 'vagrant'

After you have installed these packages, you can continue with step 2 above.