Vpro-1085-R Course for RHV/Ovirt/OLVM Implementation & Administration Lab Exercises

vPro-1085-R - Storware vProtect - Implementation & Administration Lab Exercises - v7.md

2/24/2021

vPro-1085-R Course for RHV/oVirt/OLVM Implementation & Administration Lab Exercises

Credentials and access details

Attribute

Value

Download URL vProtect host

http://10.40.0.253/lab-materials/vprotect/vpro-1085 10.41.0.4 root

vProtect username vProtect password vProtect Web UI

St0rL@bs https://10.41.0.4

vProtect Web UI username admin vProtect Web UI password vPr0tect RHV manager UI RHV user

https://rhv-m.storware.lab/ovirt-engine

admin@internalin vProtect in UI, and adminin RHV manager UI
RHV password

St0rL@bs

Lab 1 - Demo of all-in-one installation

In this section we'll show you how to install vProtect components quickly using all-in-one setup scripts. Before installation steps please update and then reboot system

dnf -y update

Remote repository (option 1)

1. Export VPROTECT_REPOvariable to point to the repository URL

export VPROTECT_REPO=http://10.40.0.253/vprotect/current/el8

2. Execute script:

bash < <(curl -s http://repo.storware.eu/vprotect/vprotect-local-install.sh)

1 / 31

2/24/2021

Lab 2 - Installation with RPMs

In this section you're going to install vProtect using RPMs - so that all necessary steps are done

Prerequisites

1. Access vlab.vpro.proxy.v3 2. Open putty on your vlab.vpro.proxy.v3 3. Connect to vProtect machine with a root access 4. Use your CentOS 8 minimal 5. Make sure your OS is up to date:

dnf -y update

If kernel is updated, then You need to reboot your operating system.
6. Install vProtect repository - create file /etc/yum.repos.d/vProtect.repo:

# vProtect Enterprise backup solution for virtual environments repository [vprotect] name = vProtect baseurl = http://10.40.0.253/vprotect/current/el8 gpgcheck=0

7. Install MariaDB repository (vProtect Server host only) usually you generate .repo file at MariaDB download site copy and paste generated repo file into /etc/yum.repos.d/MariaDB.repo, so it looks similar to this (if the repo file doesn't exist):

# MariaDB 10.4 CentOS repository list - created 2020-05-11 09:20 UTC # http://downloads.mariadb.org/mariadb/repositories/ [mariadb] name = MariaDB baseurl = http://DNF.mariadb.org/10.4/centos8-amd64 module_hotfixes=1 gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB gpgcheck=1

vProtect Server installation

2 / 31

2/24/2021

vProtect consists of server (central management point with WebUI) and one or multiple nodes (which can be installed on the same host as server or on other machines). First step is always to install server.

1. Install vprotect-server using DNF:

dnf -y install vprotect-server

2. Setup DB for vProtect:

vprotect-server-configure

Please provide a MariaDB password
3. Start vProtect Server (it can take around a minute for server to be started):

systemctl start vprotect-server

4. Open 8181 port on your firewall. Here is example:

firewall-cmd --add-port=8181/tcp --permanent firewall-cmd --complete-reload

5. For this lab we'll open plain HTTP port 8080 as well:

firewall-cmd --add-port=8080/tcp --permanent firewall-cmd --complete-reload

6. By default, vProtect console running on HTTPS port (8181), there is a script in
/opt/vprotect/scriptsdirectory to setup forwarding from port 8181 to 443 for you:

cd /opt/vprotect/scripts ./ssl_port_forwarding_firewall-cmd.sh

1. Now you should be able to log into the web console using URL: https://VPROTECT_HOST, where
VPROTECT_HOSTis hostname or IP of your vProtect Server

by default vProtect has one admin account - adminwith password vPr0tect(with zero)

Attribute

Value

3 / 31

2/24/2021

Attribute

Value

vProtect Web UI

https://10.41.0.4

vProtect Web UI username admin vProtect Web UI password vPr0tect

vProtect Node installation

vProtect Node is component that executes all tasks. It can be installed together with Server (it is common to have 1 server and just 1 node). More nodes can be always added later.

Local node

1. Create a directory mkdir /vprotect_data- will be later used as a mount point for staging space

mkdir /vprotect_data

2. Install vprotect-node using DNF:

dnf -y install vprotect-node

3. Register node with NODE_NAMEof your choice ADMIN_USERuser name which you would like to use and
URL to vProtect API and provide password when prompted:

Syntax:

vprotect node -r NODE_NAME ADMIN_USER http(s)://VPROTECT_SERVER:PORT/api

In our case we'll use HTTP to make this lab simpler local node (installed to together with server is going to be used RHV) - over HTTP (port 8080):

vprotect node -r node-local admin http://localhost:8080/api

use an admin password - vPr0tect
4. Start vProtect Node:

systemctl start vprotect-node

4 / 31

2/24/2021

Now you should be able to see new entry in Nodesection of vProtect Web UI with your node in RUNNING state.

5. Run script to configure OS for Node:

vprotect-node-configure

6. Reboot vProtect VM to apply OS-specific settings:

reboot

vProtect is installed

Lab 3 - Initial configuration

1. Upload your license key: download it first to your proxy machine desktop from the location provided during labs log in to the vProtect Web UI and go to the Settings -> Licenseand upload your

license.keyfile

2. Run from vProtect Web UI Dashboard -> Configuration wizard: 3. Define RHV manager - oVirt (v4) / RHV (v4) / Oracle Linux VM (credentials provided during classes)

Attribute Value

RHV manager UI https://rhv-m.storware.lab/ovirt-engine/api

RHV user

admin@internal St0rL@bs

RHV password

select DISK_IMAGE_TRANSFERstrategy

confirm to initiate inventory synchronization when asked
4. Create File System backup destination:

retention: defaults

Enable deduplication:

deduplication device: /dev/sdb

enable Mount deduplicated file system... Deduplicated file system mount point: /vprotect_data(we want this file system to act

also as a staging space) on the next screen set Storage path to /vprotect_data/backups- backup destination still must have different path from than staging (even when using same file system for both)

5 / 31

2/24/2021

leave Encryption and Pre/Post access commands - DISABLED set it as a default on the last subscreen and Create

5. In SSH console - verify your backup destination creation has completed successfully with the: dfcommand to check if it is mounted in /vprotect_datadirectory vdostatsto see if VDO device has been initialized and is ready

6. Go back to the wizard 7. Skip VM backup schedule section 8. Skip VM backup policy section 9. Configure daily vProtect DB backups (schedule and policy) using node and backup destination that have been created

10. Confirm to initiate vProtect DB backup when asked 11. Now go to Users section - to set admin accounts: make sure to set the correct time zone for your user - default adminaccount has UTC by default.
12. Create another admin account: click Create in Users section provide username, first name, last name, time zone and language click Save button

Lab 4 - Managing node configuration

1. Log in to vProtect Web UI 2. Go to Nodes -> Node Configurations tab 3. Create a new configuration provide a name of your choice change maximum number of export threads to 2 in Task tab assign your FS with deduplication backup destination to the node config

4. Update node and change node configuration to the one you created (go back to nodes tab)

Lab 5 - Dell EMC DataDomain as a backup destination

1. Prepare your PowerProtect DD as a backup destination:

Attribute

Value

DD URL

https://10.41.0.51/ddem

DD username sysadmin DD password St0rL@bs

6 / 31

2/24/2021

login to PowerProtect DD and verify you have Storage Unit called vprotectbackup go to data management -> MTree on the left menu download BoostFS RPM from URL provided during labs

curl -O http://10.40.0.253:8181/vprotect/current/lab- materials/DDBoostFS-7.0.0.0-633922.rhel.x86_64.rpm

install BoostFS:

rpm -ivh DDBoostFS-7.0.0.0-633922.rhel.x86_64.rpm

create mount point directory

mkdir /dd-backups

save password for BoostFS (DD_BOOST_IPshould be replaced with IP of your DD):

/opt/emc/boostfs/bin/boostfs lockbox set -d DD_BOOST_IP -u vprotect -s vprotectbackup

provide password: St0rL@bs add /etc/fstab entry:

DD_BOOST_IP:/vprotectbackup /dd-backups boostfs defaults,_netdev,bfsopt(allow-others=true) 0 0

Notice that for manual, one-time mount you can run this command:

/opt/emc/boostfs/bin/boostfs mount -o allow-others=true -d DD_BOOST_IP -s vprotectbackup /dd-backups

mount

mount -a

7 / 31

2/24/2021

set ownership to vprotect user on directory /dd-backups:

chown vprotect:vprotect -R /dd-backups

confirm with dfthat your /dd-backups create backup subdirectories that we will need in the next steps

mkdir /dd-backups/short-term mkdir /dd-backups/long-term

1. Log in to vProtect Web UI 2. Go to Backup Destinations tab 3. Create a new File System backup destination - in the details:

provide name: short-term destination

specify retention days for full and incremental backups = 14 days specify retention versions for full backups = 2 specify retention versions for incremental backups = 7

set path as /dd-backups/short-term

assign this node config that you have created in your previous lab explore other options in the settings

4. Create a new File System backup destination - in the details:

provide name: long-term destination

specify retention days for full and incremental backups = 365 days specify retention versions for full backups = 999 specify retention versions for incremental backups = 999

set path as /dd-backups/long-term

assign this node config that you have created in your previous lab explore other options in the settings

5. Go to Settings -> Internal DB backup -> Overview (click on details icon) 6. Run backup manually (top right corner) specify your new backup destination as a target and proceed with backup
7. Verify that backup has been successfully stored refresh backup list in the view when completed
8. Check backup details in Backups tab and show its details (notice backup files listed) 9. Explore contents of the /dd-backups/short-termfolder (notice how versions are stored)

8 / 31

2/24/2021

Lab 6 - Policies & schedules

Policy

1. Log in to vProtect Web UI 2. Go to Virtual Environment -> Backup SLAs tab 3. Create new backup policy

enable auto-assignment - mode Assign only add rule based regular expressions - .*[Aa]lpine.*- matches all VMs with substring Alpineor

alpine

Go to Rule and Select Backup Destination
4. Save Policy 5. Go to Hypervisor Managers tab in the Infrastructure section 6. Run inventory synchronization on your RHV environment 7. Verify that all your RHV VMs have been assigned to the policy

Schedules

1. Go to Virtual Environment -> Backup SLAs tab 2. Change tab to Schedules 3. Create a schedule for full backup:

backup type: Full time: 22:00 days of week: just Sunday choose policy on the right: Production VMs

4. Create a schedule for incremental backup:

backup type: Incremental time: 22:00 days of week: just Monday-Saturday choose policy on the right: Production VMs

5. Go to the Virtual Environments 6. Verify that you have your VMs marked as outdated

Lab 7 - VM Backup & Recovery

Backup

9 / 31

2/24/2021

1. Log in to vProtect Web UI 2. Go to Virtual Environments -> Instances 3. Click backup button (on the right) near the VM that resides on RHV
If you are unsure, click on the name of the virtual machine to enter the details of vm. In the upper right corner you will see the name of the hypervisor

4. Leave Fullbackup as the backup type 5. Run backup 6. Verify if it has succeeded 7. Go to Virtual Environment -> Instances details of your VM
Backup history tab - look for entry related to the backup that has just been created Snapshots tab - look for the snapshot that has just been created and check if it has been marked

as Current for incremental

8. Go to the dashboard and check values of the used space size and charts 9. Go to the the RHV console

Attribute

Value

RHV manager UI https://rhv-m.storware.lab/ovirt-engine

RHV user

admin

RHV password

St0rL@bs

10. Log in as adminand go to Events tab check recent activity related to snapshots go to the Compute -> Virtual Machines -> VM that you have backed up -> Snapshots verify that snapshot has been left for future incremental backups

Restore

1. Go back to the vProtect and try to restore VM:
Virtual Environments instances list - button on the right select your hypervisor manager and default storage leave rest of the fields with defaults
2. Once the job completes, check if it has succeeded and verify again in your RHV console that VM is present

Lab 8 - VMs details & settings

Virtual environments details

1. Log in to vProtect Web UI

10 / 31

2/24/2021

2. Go to VM that resides on the RHV that has been previously backed up 3. Browse through charts at the top - activities / backup size / backup time / restore time 4. Go to the Settings verify which Settings are available for RHV VMs

Lab 9 - Pre/Post snapshot command execution

In this lab we'll simulate remote command execution before and after snapshot takes place. Usually you would execute commands on the remote host, but to skip unnecessary steps required to setup network, we'll execute commands on the 127.0.0.1(which is basically node which executes commands)

1. Log in to vProtect Web UI 2. Go the the VM settings running on RHV 3. in Pre snapshot command execution:

enable it add command argument: /bin/bash add command argument: -c

add command argument: ip a > /tmp/PRE-SNAPSHOT

1. in Post snapshot command execution: enable it add command argument: /bin/bash add command argument: -c

add command argument: hostname > /tmp/POST-SNAPSHOT

1. in Settings -> SSH access tab:
SSH host - 127.0.0.1 SSH user - root

click Save

1. in Change SSH password tab:

SSH password - St0rL@bs- you need to click Change ssh password

1. Run backup with the button at the top-right corner 2. We need to Login with SSH to the vProtect Server and Node operating system and verify if files
/tmp/PRE-SNAPSHOTand /tmp/POST-SNAPSHOTare present and check their contents

Lab 10 - File-level restore

Automatic mount

1. Log in to vProtect Web UI 2. Go to the Virtual Environments tab 3. For the VM running on RHV that you have backed up previously select mount (3rd icon)

4. Select Mount filesystems automatically and node-local

5. Run the job and once it completes go to the Mounted Backups tab in the Virtual Environments section 6. Click magnifying glass icon to go to the details

11 / 31

2/24/2021

7. At the bottom you should be able to see single File System entry - corresponding to the root file system
8. Click browse 9. Navigate to /etc/passwdfile, select file and click Download button
10. Verify that contents ZIP archive contain the file you restored 11. Log in to the node-localusing SSH and navigate to the mount point of the mounted backup - by

default in /mnt/vprotect

12. Check if you are able to list files in this directory 13. Go to Virtual Environments -> Mounted Backups -> click Delete icon on the right of the mounted backup and wait for task to complete
14. Refresh the page and make sure backup is no longer on the list

Manual mount

1. Log in to vProtect Web UI 2. Go the the Virtual Environments tab 3. For the VM running on RHV that you have backed up previously select mount (3-rd icon)

4. Select Specify filesystems to be mounted and node-local

5. Select just first file system on the list and accept default values for rest of the parameters 6. Run the job and once it completes go to the Mounted Backups tab 7. Click magnifying glass icon to go to the details 8. At the bottom you should be able to see single File System entry - corresponding to the selected file system
9. Click browse
10. Navigate to /etc/passwdfile, select file and click Download button 11. Go to Virtual Environments -> Mounted Backups -> click Delete icon on the right of the mounted backup and wait for task to complete

iSCSI share (Linux)

1. Log in to the node-localover SSH and check what is IQN of this iSCSI client

cat /etc/iscsi/initiatorname.iscsi

2. Log in to vProtect Web UI 3. Go the the Virtual Environments -> Instances tab 4. For the VM running on RHV that you have backed up previously select mount (3-rd icon)

5. Select Share drives over iSCSI and node-local

6. Select just first disk on the list 7. Click Add Client and provide IQN that you have found on the node-local 8. Accept default values for rest of the params and run the job

12 / 31

2/24/2021

9. Once it completes login with SSH to the node-localagain
Discover iSCSI targets

iscsiadm --mode discovery --type sendtargets --portal NODE_LOCAL_IP

Login to iSCSI target (change target name to match yours of the target)

iscsiadm --mode node --targetname iqn.2013-03.storware.eu:216b66a1- 9797-41e6-a1f6-a74f767dfc60 --portal NODE_LOCAL_IP --login

Verify block device is present

lsblk

10. Go to Virtual Environments -> Mounted Backups -> click Delete icon on the right of the mounted backup and wait for task to complete

Lab 11 - Snapshot Management

1. Log in to vProtect Web UI 2. Go the the Virtual Environments -> Snapshots SLAs tab 3. Create new policy with the name RHV-1d 4. Leave auto-assignment disabled 5. In Virtual Environments section - assign VM that you previously backed up on RHV environment 6. In Rule section specify:
Retention versions: 2 Retention days: 1
7. Save policy 8. Now create a schedule that will periodically create snapshots - go to the Virtual Environments ->
Snapshots SLAs section and then change tab to Schedules
9. Click Create button and select Interval as Schedule execution type

10. Set time of interval to 08:00-16:00, frequency: every 180 minutes

11. Change days of week for Friday 12. Select policy that you have just created 13. Go to the Virtual Environments -> Instances VM you selected 14. In the details -> top right corner there should be additional Snapshot icon (camera) 15. Click it, so that snapshot task appears 16. Verify if snapshot has been created in RHV (Compute -> Virtual Machines -> Snapshots tab of this VM) 17. Submit 2 more snapshot tasks 18. Verify in RHV client that first snapshot has been removed