Skip to main content

VCSA 6.5 Backup




Now VCSA 6.5 is coming with inbuilt backup option. We can take backup directly from VCSA appliance manager portal, backup will include your PSC as well.

If you want to take daily backup or weekly backups, we can automate this backup jobs with help of scripts.

Generally FTP server used for backup repository

I am in my VCSA appliance manager portal, it’s running on VCSA 6.5 with an embedded PSC.
Click on “Backup” button.


















Enter your backup details:-

Select Protocol : I am using FTP ( FTP,FTPS,HTTP,HTTPS,SCP protocols are available)

Select Location: Here FTP server and share location.

Port: 21
Enter your user name and password for FTP share.

If you want to encrypt your vCenter backup, select Encrypt Backup Data option.




Next will be the most important thing, we have to provide password for our vCenter backup, you should keep this password safe. While restoring backup to new vCenter server we require this password, if you forget their is no way to restore or reset the password.

And you can see below warning: The HTTP and FTP protocols are not secure. Do not use them to connect out side of your LAN.

This is completely lab environment so I will go with FTP, If you are configuring in production consider this warning and make your design perfect.

Fill all the details and click “Next” to continue


 




Select which parts you want to backup,

There are two options:-

1. Common (Inventory and configuration)
2. Stats, Events, Alarms and Tasks (Historical data (statistics,events and tasks) in vCenter Server database.

Provide proper discretion for your backup.
Click “Next” to continue.







Verify all provided details and click “Finish”.







As you can see below screenshot initiated backup job completed, verify and click “OK”.








Comments

Popular posts from this blog

Dell EMC VxRail – VMware Virtual SAN Stretched Cluster

Logical Diagram of VMware vSAN Stretched Cluster Physical Diagram of VMware vSAN Stretched Cluster Last week I deployed a test environment of VMware vSAN Stretched Cluster which is running on Dell EMC VxRail Appliance. In this post we will describe how to setup VMware vSAN Stretched Cluster on Dell EMC VxRail Appliance. Above figure is the high level of physical system diagram. In site A/B there are six VxRail Appliances and two 10GB Network Switch which are interconnected by two 10GB links, and each VxRail Appliance has one 10GB uplink connects to each Network Switch. In site C, there are one vSAN Witness host and one 10GB Network Switch. For the details of configuration of each hardware equipment in this environment, you can reference the followings. Site A (Preferred Site) 3 x VxRail E460 Appliance Each node includes 1 x SSD and 3 x SAS HDD, 2 x 10GB SFP+ ports 1 x 10GB Network switch Site B (Secondary Site) 3 x VxRail E460 Appliance Each node includes 1 x SSD and...

VxRail 4.0 – Scale Out

The above is the physical diagram of VxRail Cluster (3 nodes). In this post I will show how to add one VxRail Appliance into this VxRail Cluster (From 3 nodes to 4 nodes). NOTE: The model of each VxRail Appliance is E460. Before the node expansion, you need to verify each Appliance is running in health in dashboard of VxRail Manager. The above is the final physical diagram of VxRail Cluster after scale out. Now we start the node expansion. You have just mounted a new VxRail Appliance (E460) and cabled it up to the top of each rack switch. When you power it on you can see a notification appear in the top left corner of VxRail dashboard. Click “ Add Node “. When you initially configured your VxRail Appliance, you specified an IP pool for ESXi, vMotion and vSAN. You can see that there available IP addresses in these pools, so the only additional action is to set an ESXi password. Click the scroll bar, then click the “ ESXi Password “. Enter the  ESXi  and ...

UEFI Secure Boot with ESXi 6.5

UEFI Secure Boot: UEFI, or Unified Extensible Firmware Interface, is a replacement for the traditional BIOS firmware. In UEFI, Secure Boot is a “protocol” of the UEFI firmware. UEFI Secure boot ensures that the boot loaders are not compromised by validating their digital signature against a digital certificate in the firmware. UEFI can store whitelisted digital certificates in a signature database (DB). There is also a blacklist of forbidden certificates (DBX), a Key Exchange Keys (KEK) database and a platform key. These digital certificates are used by the UEFI firmware to validate the boot loader.  Boot loaders are typically cryptographically signed and their digital signature chains to the certificate in the firmware.The default digital certificate in almost every implementation of UEFI firmware is a x509 Microsoft UEFI Public CA cert. Most of the UEFI implementations also allows the installation of additional certificate in the UEFI firmware and UE...