Veeam Backup & Replication 13.0.2.29

https://www.veeam.com/kb4738 

Standalone Installer of Backup Console

Standalone console installer can now be found on official product download page, under "Extensions and Other" tab or via direct link 

https://www.veeam.com/download_add_packs/vmware-esx-backup/backup-replication-console/

Error then updating Veeam to 12.3.0.310 - VeeamAgent.exe / Windows Script Host must be enabled

When trying to run update 12.3.0.310, you might encounter this error.

First , stop all jobs. and then disable them.
If the error persists

End the task from task manager.

If the VBR server are hardned you will get this error.

"Windows Script Host must be enabled for the duration of setup process"

Follow this guide
https://www.veeam.com/kb4699

RHEL 9.5 is fully supported in the VBR 12.3 release.

 RHEL 9.5 is supported in version VBR 12.2 through the kernel module patch and will be fully supported in the VBR 12.3 release.

Vulnerabilities Resolved in Veeam Backup & Replication 12.3

 https://www.veeam.com/kb4693

Release Information for Veeam Backup & Replication 12.3

 https://www.veeam.com/kb4696

New Veeam Threat Hunter service

 When upgrading to Veeam Backup&Replication_12.3.0.310_20241201

https://www.veeam.com/kb1999

The new Veeam Threat Hunter service scanning process might be interrupted by existing antivirus software on mount hosts. Please read KB1999 to set the appropriate exclusions.

When starting "Veeam Backup & Replication Console"

Under Malware Detection Settings notice license requirements.

Build Numbers and Versions of Veeam Backup & Replication

https://www.veeam.com/kb2680

Veeam One : 12.2.0.4093

Version history:

• 12.2.0.4093 (August 28th, 2024) > What's New in 12.2

Veeam Backup & Replication : 12.2 RTM & GA (build 12.2.0.334)

Version history:

• 12.2 RTM & GA (build 12.2.0.334) on August 28, 2024 > What's New in v12.2

support for vsphere 8.0 U3 (without workarounds), mongodb, significant enhancements to S3 backup, added proxmox support; are a few of the many improvements.

February 1, 2022 - end-of-support of the following products

 

This message is to inform you that effective February 1, 2022, the following products will reach end-of-support:

Veeam® Backup & Replication™ 9.5 Veeam ONE™ 9.5 Veeam Agent for Windows/Linux 3.0 Veeam Disaster Recovery Orchestrator 2.0

When a product version reaches this stage, this version will no longer be supported by Veeam. To continue getting Veeam’s expert support, your customers will need to have an active maintenance contract and upgrade to the latest version.

Veeam version 9.5 and earlier End of Support

V9.5 and earlier for Veeam^® Backup & Replication™ and Veeam ONE™ will reach End of Support on Jan. 1, 2022. Please note that V9 of these products reached end of fix in February of 2020 when Veeam released V10.

How to create new XFS datastore

 

First delete all old partisions

Use fdisk -z /dev/sdb if that is the new disk.
You han also use sgdisk -z /dev/sdb

pvcreate /dev/sdb

WARNING: dos signature detected on /dev/sdb at offset 510. Wipe it? [y/n]: y

Wiping dos signature on /dev/sdb.

Physical volume "/dev/sdb" successfully created.

 vgcreate backup_vg /dev/sdb

 Volume group "backup_vg" successfully created

lvcreate -n backup_vol -l 100%FREE backup_vg

Logical volume "backup_vol" created.

mkfs.xfs -b size=4096 -m reflink=1,crc=1 /dev/backup_vg/backup_vol

meta-data=/dev/backup_vg/backup_vol isize=512    agcount=32, agsize=234414016 blks

               =    sectsz=4096  attr=2, projid32bit=1

               =    crc=1 finobt=1, sparse=1, rmapbt=0

               =    reflink=1

data        =    bsize=4096   blocks=7501248512, imaxpct=5

               =    sunit=64     swidth=512 blks

naming   =    version 2 bsize=4096   ascii-ci=0, ftype=1

log          =    internal log           bsize=4096   blocks=521728, version=2

               =    sectsz=4096  sunit=1 blks, lazy-count=1

realtime  =    none extsz=4096   blocks=0, rtextents=0

mkdir /veeam

vim /etc/fstab

insert this line

/dev/backup_vg/backup_vol       /veeam          xfs     defaults   0 0 

 lsblk

NAME                MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT

sda                        8:0    0  447G  0 disk

├─sda1                8:1    0    1G  0 part /boot/efi

├─sda2                8:2    0    2G  0 part /boot

└─sda3                8:3    0  443G  0 part

  ├─rhel-root        253:0    0   70G  0 lvm  /

  ├─rhel-swap      253:1    0    8G  0 lvm  [SWAP]

  ├─rhel-var           253:3    0   50G  0 lvm  /var

  └─rhel-home          253:4    0  315G  0 lvm  /home

sdb                      8:16   0   28T  0 disk

└─backup_vg-backup_vol 253:2    0   28T  0 lvm  /veeam

Show SQL version on Veeam VBR Server

 Show SQL version on Veeam VBR Server

1. Step 1 -Open a command prompt window on the machine in which SQL is installed. ...
2. Step 2 -SQLCMD -S servername\instancename (where servernameb= the name of your server, and instancename is the name of the SQL instance). ...
3. Step 3 -select @@version
4. Go

Veeam Backup & Replication 11a Cumulative Patches 11.0.1.1261 P20211123.

 This cumulative patch includes the following new features, enhancements and fixes for the original V11a builds:

P20211123

1. Scale-out backup repository (SOBR): initiating SOBR rescan with one of Performance Tier extents being in maintenance mode, and taking said extent out of the maintenance mode at the specific moment of the Rescan process results in all backup files on this extent replaced with stubs downloaded from Capacity Tier.
2. SOBR Capacity Tier: under certain circumstances,  copy/offload to Capacity Tier starts failing with the “Attempt to overwrite existing non-sparse block version” error.
3. SOBR Archive Tier: a rare situation involving an interruption or a failure of the S3 API call to object storage during the specific operation may place Capacity Tier into a state resulting in further Archive Tier offload attempts failing with the “Specified key does not exist” error.
4. Email notifications: backup job email notifications are missing information about datastores with a lack of free disk space.
5. User interface: some UI nodes may show outdated job status information, requiring users to press F5 to refresh the view and actualize it.
6. HPE StoreOnce: updated HPE StoreOnce Catalyst library to version 4.2.4, which includes a fix from intermittent “Pipeline hanged” errors when reading data from the corresponding backup repository.

https://www.veeam.com/kb4245

Design Veeam repository , with a second mirrored repository

(1) Backup Job.

Create backup job, and set retention and GFS

1. Select Tier1 Repository 

2. Here I set at retention to 30 restore points ,

    GFS to 4 weekly, 12 monthly , 3 yearly

(2) Backup Copy

Create backup copy job, and enable immediate copy (mirroring)

1. Set a name for the Copy Job

2. Select immediate copy (mirroring)

1. Add the backup job to the copy job.

1. Select Tier2 Repository 

2 and 3 Configure the same retention and GFS

Now you have created a backup job and a copy job with "immediate copy"

 Tier1 an Tier2 will be identical from now on.