One of the most important best practices for working with GhettoVCB is to work with it in a lab environment prior to attempting to use it in any kind of production. If you do decide to use a VM-based NFS volume, it is important to not only choose a VM residing on a different VMware host but also to put rules in place to keep the VM from being accidentally migrated to the host that the backup is protecting.Ĭhanging Configuration in GhettoVCB Lab Validation If possible, it’s probably best to write your backups to an NFS volume that is hosted on a NAS appliance or other dedicated storage device. Otherwise, if something were to happen to the VM or to the underlying datastore, you could end up losing your backups. While there is nothing stopping you from backing up your virtual machines to an NFS volume that is stored on a virtual machine, it’s important to make sure that the VM hosting the NFS volume does not reside on the VMware host that you are backing up. GhettoVCB is designed to backup your VMware virtual machines to an NFS volume. One of the things that you will have to do when you first deploy GhettoVCB is to specify a backup target. Best Practices for Selecting a Backup Target To do so, use the -a switch to tell GhettoVCB that all VMs should be backed up, and then specify the -e switch, followed by your exclusion list of VMs that you do not want to include in the backup. If on the other hand, you want to back up most of your VMs but have a few specific VMs that you don’t want to back up, then you may be better off creating an exclusion list. This switch allows you to list all of the virtual machines that you want to back up. If you only want to back up a small number of VMs, then your best option is probably to use the -f switch. In these situations, it probably doesn’t make sense to back up everything. Similarly, there may occasionally be a need to back up one specific virtual machine or one particular application. For example, you might prefer to skip backing up lab VMs or static application VMs that have already been backed up. Just specify the -a switch to back up all VMs.Īs handy as the -a switch might be, there are situations in which you might not want to back up every virtual machine. GhettoVCB makes it easy to back up all of a VMware host’s VMs. When it comes to backing up a VMware host, it is usually advisable to back up all of your virtual machines. Scheduling a Backup in GhettoVCB Choosing the VMs to Back Up Here is an example of what a dry run command looks like: You will also need to include the -d switch, which tells GhettoVCB to perform a dry run rather than an actual backup. You will need to use either the -a switch to backup all virtual machines, or the -f switch to specify the virtual machines that you want to back up. The syntax used in performing a dry run is really simple. One of the best ways to make sure that GhettoVCB is going to back up everything that you intended is to perform a dry run. Dry Run Modeīackups can be time-consuming, and with any backup application, there is a potential for a backup job to be misconfigured, thereby causing it to fail. This article provides tips, tricks and best practices for working with GhettoVCB. Like VMware’s VCB tool, GhettoVCB works by creating a snapshot of running virtual machines, backing up the VM, and then deleting the snapshot. GhettoVCB is a free, open-source tool that you can use to back up VMware virtual machines.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |