Technical blog

Configure SQL Server transaction log Backup in Veeam & Backup Replication

I have created backup job using Create Backup Job In Veeam Backup & Replication and added both SQL node that is member of MS cluster and AG.

POC01 & POC02

Select Existing created Job Backup-SQL-AG

Right click and Edit -> Go to Virtual Machine and verify both nodes are added or not.

Go to Guest Processing
Check Mark on Enable application-aware processing

Click Application

Select VM one by one and click Edit
Click on SQL -> Check mark on Backup logs periodically (requires simple recovery model)
And set the time to run SQL Server transaction log back on every *** Minutes.

Also, if you may decide to keep SQL Server transaction log backup for how long time
Check mark on Retain log backups, like Until the corresponding image-level backup is deleted or keep only last *** days of log backups.

Add Guest OS credentials, make sure you have local Administrator access as well as Sysadmin at SQL level.

Click Test now to check the credentials that you have enter is correct.

No apply and Finish.
Once the backup will complete go to Disk under Backup and you will see SQL Server transaction log backup has also taken along with full backup.

One-time full backup will run, and SQL T log backup will run in every 5 Minutes

Step to enable NFS service, create NFS shared folder and give access to mount NFS shared folder in Veeam backup and Replication using Synology NAS device.

Click on File Services

Click File Services -> NFS -> Enable NFS service.

Maximum NFS protocol: Drop down and select the version NFSv3.

Click Advanced Settings and configure the policy based on our requirements.

Step to create Shared Folder and enable NFS sharing.

Click File Sharing -> Shared Folder -> Create.

Under General

Name-: Give folder name.

Description-: Description

Location-:

Check mark on below highlighted.

Advanced -> Check mark on Enable shared folder quota.

Permissions

Add local or Domain users and give access based on requirements.

Add initiator host IP/subnet to allow access to mount NFS folder.

Oracle KVM

Mount ISO file in VMware workstation

Boot the VM with ISO

Select Install Oracle Linux

Select Language

Click on warning under system, Software & Localization configuration. And update the missing configuration.

Enter User Name and password.

Select Disk -> Click Next

Once all the highlighted warning you fixed-> Begin the installation.

Once installation will complete, install required packages

What is vSAN file service? And how to configure step by step

vSAN native file services draw attention for many reasons.
Its flexibility, integration, and capabilities make it a good fit for a variety of use cases.
The initial version provided a key element to serving up cloud-native applications in vSAN:

Persistent, read-write many (RWM) volumes. vSAN 7 Update.

1 improved on the capabilities of file services even further with support for SMB v2.1 and v3,

Active Directory integration and Kerberos Support. vSAN 7 U2 extends the capabilities of vSAN file services

in new and interesting ways including support for stretched clusters, data-in-transit encryption,

snapshots and improved scale, performance and efficiency.

Step to configure File service using vSAN step by step.

I have already built 3 node vSAN cluster.

1 Node I am using for Witness and 2 nodes for FTT.

Click on vSAN enabled cluster

Configuration -> Select File Shares

Give File service domain name -> Next

Select Protocol –> IPv4

Assign DNS servers

Assign DNS suffixes

Assign Subnet mask & Gateway

Assign IP and DNS name manually or select Autofill.

Click next

Check mark on Active directory service

AD domain name

AD username and password

Follow the steps and click next & finish

Get-Certificate: CertEnroll::CX509Enrollment::Enroll: Error Parsing Request The request subject name is invalid or too long. 0x80094001

Get-Certificate: CertEnroll::CX509Enrollment::Enroll: Error Parsing Request The request subject name is invalid or too long. 0x80094001 (-2146877439 CERTSRV_E_BAD_REQUESTSUBJECT) The request ID is 1109849. A certificate could not be issued by the certification authority.: The request subject name is invalid or too long. 0x80094001 (-2146877439 CERTSRV_E_BAD_REQUESTSUBJECT). This may be the result of user credentials being required on the remote machine. See Enable-WSManCredSSP Cmdlet help on how to enable and use CredSSP for delegation with PowerShell remoting.

When you are getting error The request subject name is invalid or too long. 0x80094001 make sure you are not using more than two characters for C=

Get-Certificate -Template WebServerCustom -SubjectName "CN =DEMOVC002.ads.com,OU = DEMO,O = DEMO,L = Dubai,S = IND,C = DE" -DnsName DEMOVC002.ads.com, DEMOVC002 -CertStoreLocation cert:\LocalMachine\My

error: No DHCPv4 option 11 server ip or option 17 server name streaming aborted

Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

If you are getting below error while adding node or connecting node in existing cluster .

Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Solution -: Make sure you have installed all latest patches in node before adding to the cluster.

In-Place Upgrade failed with error 0x8007042B - 0x4000D

If you see error code 0x8007042B - 0x4000D at 82-83% during In-Place upgrade from 2012 R2 to windows server 2016 or 2019.

Make sure, you have enough space in C drive, always keep C drive space around 100GB free space before going for In-Place Upgrade.

vCenter Upgrade Plan Workflow

VMware vRealize Orchestrator | Aria Automation Installation and known issue troubleshooting | LCMVRAVACONFIG590003

Aria Automation Installation failing at Initialize vRealize Automation cluster with below error.

Issue – Error Code: LCMVRAVACONFIG590003

Cluster initialization failed on vRA.
vRA va initialize failed on : xxxx-xxxx-xxxx,
Please login to the vRA and check /var/log/deploy.log file for more

information on failure. If its a vRA HA and to reset the load balancer,

set the ‘isLBRetry’ to ‘true’ and enter a valid load balancer hostname.

Default root password of VMware vRealize Orchestrator Appliance is vmware

passwd -x 99999 root