Browsing Posts tagged vCSA

Reading Time: 2 minutes The possibility to backup VCSA using VAMI at file level is very powerfull and could be a good “plan-B” in case the backup at image level is not restorable (it happens in case of file/DB corruptions). But, of course, is not perfect and still in latest version there are some issues, like the VAMI backup retention issue. But can also happen that backup fails with no specific errors.

Reading Time: 2 minutes The VCSA update procedure is usually easy and simple and can be performed from the VAMI as explained in a previous post: Manage VCSA updates with VAMI. But sometimes may failed for different reasons.

Reading Time: 2 minutes A usual way to backup the VMware vCenter Server Appliance (VCSA) is to manage as a common VM and use a backup solution to backup (and restore) the entire VM. But it’s approach does not always work and cannot guarantee a restore in some cases, for example in the case of a database corruption.

Reading Time: 3 minutes One interesting news of the latest version of vCSA is the health monitoring feature. You can check the overlall health with your vSphere Client, by selecting the vCenter node and then Monitor | Health.

Reading Time: 3 minutes One of the advantages of the VCSA compared to the Windows’s based vCenter Server is the simplicity of the update procedure that can be easility managed with the VMwareAppliance Management Interface (VAMI). The VAMI is another web based UI accessible thought the https://vcenter:5480 URL address. Note that you must use the local root user credential in order to login.

Reading Time: 2 minutes One of the big advantages of the virtual appliance version of VMware vCenter (vCSA) is the ability to update both the OS components and the VMware parts with a simple menu. Just use the administrative UI available at https://vCSA_IP:5480 and login with user root and the password that you have chosen during the deployment.

© 2024-2011 vInfrastructure Blog | Disclaimer & Copyright