reevert Firmware 1.14
The reevert appliance is provided as an OVA file, so you can import it into several different virtual environments. The recommended specifications and instructions for importing the appliance on each platform can be seen below. If you have any kind of web blocker in your environment, please make sure to exclude your appliance from its restrictions. Your appliance needs internet access to be able to function properly.
CPU and Memory Allocation
Minimum Requirements: 2 CPU Core / 4 GB Memory
Recommended Requirements: 4 CPU Core / 8 GB Memory
Larger Datasets: For larger data sets that are 500GB+, 8 CPU Core / 16 GB Memory
Disk Space Allocation
To have an idea of how much disk space is needed for your appliance, see our example below and easy to use calculator!
Our client Company A has 100GB of data that needs to be stored, and decided on using the default snapshot retentions settings (144 Hourly, 31 Daily, 4 Weekly, 12 Monthly). If they estimate that only 1GB of data will change on a daily basis, they will need 330GB of space to hold the data and one year worth of snapshots. Now please note that this is only a rough estimate. Depending on how compressible your data is, this can reduce by a large margin.
Please note that this is a rough estimate, and your true storage needs can vary depending on how compressible your data is, which can reduce the requirements by a large margin.
These instructions are with the assumption that you are using the VMware vSphere Client.
Importing the Appliance
Click on File in your vSphere Client and then Deploy OVF Template. This will bring up the Deploy OVF template process which involves several steps.
First, you will need to Browse to the reevert OVA file and then click Next to go to the next step.
You will be shown the OVF Template Details, which will go over information such as the product name, import file size, and the size the appliance will take on the storage disk if thin provisioned or thick provisioned.
The next step will allow you to name your appliance. This is so you can distinguish your reevert appliance from your other virtual machines.
Next you will select the resource pool that you want to add your appliance to.
The next screen will display the list of destination storages for the virtual machine files. You will need to pick one to get to the next step.
Once you have selected the datastore, you will be shown the name of the datastore, how much storage space is available, and three options on how you want your virtual machine drive formatted. These options are Thick Provision Lazy Zeroed, Thick Provision Eager Zeroed, and Thin Provision. If you remember, the OVF Template Details went over how much space the virtual machine will take on Thick or Thin Provision.
The next step will bring you to Network Mapping, where you will select the source and destination networks for the appliance.
Finally, you will be brought to a summary page which will display all of the settings you chose in the previous steps. Below the summary you will also see a checkbox that will allow you to power on the appliance after deployment.
For more information on how to add more CPU or memory resources to your appliances, or add and / or delete virtual drives, please visit the VMware documentation here.
Oracle VM VirtualBox Deployment
Importing the Appliance
To change the default location of your Virtual Box hard disks, go to File > Preferences > General -> Default Machine Folder. Then import the OVA file.
To import the OVA file, imply click on File and then Import Appliance, which can also be accessed by the keyboard combination Ctrl + I.
Once there, you will be able to browse to the OVA file by clicking the folder icon next to the field. Once you have located your file, click Next.
This step displays the final configuration of the reevert appliance import, which you will then press import to deploy the appliance. The reevert appliance will come configured with the mininum specifications, and any increase in memory or CPU cores will need to be done through the virtual machine settings.
For more information on how to add more CPU or memory resources to your appliances, or add and / or delete virtual drives, please visit the VirtualBox documentation here.
For the Hyper V Deployment, you will need to proceed with a few extra steps to prep the reevert image for importing. You will need to extract the OVA file and convert the vmdk file to vhd or vhdx. This can be done by installing the Microsoft Virtual Machine Converter found here. Once this is done, you can use the powershell modules provided with the converter to convert the vmdk file. You will need to open Windows Powershell and then import the converter module using the command,
Import-Module ‘C:\Program Files\Microsoft Virtual Machine Converter\MvmcCmdlet.psd1′
Once the module has been imported, you can use the conversion command to convert the vmdk to vhd listed below,
ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath C:\PathToFile\reevert-1.4.10-disk1.vmdk -VhdType DynamicHardDisk -VhdFormat vhd -DestinationLiteralPath c:\PathToFile\
which will create the vhd file that you will use to import the appliance.
Importing the Appliance
Connect to your Hyper-V server and click on New under the Actions side menu on the right side. Under the new drop down select Virtual Machine, which will bring up the New Virtual Machine Wizard.
Click next to bypass the 'Before You Begin' page to get to the Specify Name and Location step.
Once there, enter a name for your appliance, and a location to store it, if you choose. If you don't choose a specific location, it will store it in your default VM store location. Once you have done so, click next to visit the Assign Memory page.
On the Assign Memory page, you will need to set the amount of memory available to the appliance. Please see the 'Resource Requirements' for the recommended memory amount and click next to visit the Configure Networking page.
On the Configure Networking page, you will need to set the connection to the virtual network you wish to connect the reevert appliance to. Once you have done that, click next to get to the Connect Virtual Hard Disk page.
The Connect Virtual Hard Disk page is where you will connect the reevert converted vhd. Select the "Use an existing virtual hard disk" option, and point to the reevert vhd file. You can click Next to visit the summary page to review all of the settings, or click finish to finish the creation process.
For more information on how to add more CPU or memory resources to your appliances, or add and / or delete virtual drives, please visit the Hyper-V documentation here.
For the KVM deployment, you will need to proceed with a few extra steps to prep the reevert image. The reevert OVA file will need to be extracted to get the img file. This can be done with the command "tar -xf reevert-1.4.10.ova". This will extract the reevert vmdk file. This vmdk file will need to be converted into an img file. This can be done with the command,
qemu-img convert -O raw reevert-1.4.10-disk1.vmdk reevert.img
Once you have converted the image to a .img file, you will need to move it to your virtual machine store. Once you have done that you can start importing the appliance.
Importing the Appliance
You will need to first click on the Create a new virtual machine button in the toolbar, which will bring up the New VM window.
Step 1 of 4 is where you choose how you would like to install the OS. Because we are importing the reevert appliance, you will have to select the import existing disk image option then click Forward.
Step 2 of 4 is where you will point to the reevert .img file. You will also need to choose an operating system type and version. This part is important because you will need to select Linux for the OS type, and Debian Wheezy (or Later) for the version. Once you do that, click on Forward.
Step 3 of 4 is where you choose how much memory and CPU cores to give to the appliance. Please refer to the Resource Requirements above to set the correct settings. Once done, click Forward.
Step 4 of 4 is where you will name your appliance. You will also enter the Bridge name under the Advanced Options to connect the appliance to your network. Once you have done this, click on Finish to import the appliance.
When adding storage devices, make sure that they are not virtIO Disk Bus type. You will risk losing your data if you do so.
For more information on how to add more CPU or memory resources to your appliances, or add and / or delete virtual drives, please visit the KVM documentation here.
Citrix Xen Server Deployment
Importing the Appliance
Right click on your Host in your XenCenter and select the Import option. This will bring up the Import window, where you will go through several steps.
First, the Import Source step is to locate the Import Source file, which you will do by clicking on Browse and locating the reevert OVA file. Once you have done so, click Next.
The Location step allows you to choose which pool or server you want to place your VM in. Once you have chosen the proper location, click on Next.
The Storage step allows you to select where you want to store the virtual disks of the reevert appliance. Select the option that you wish and click on Next.
The Networking step is where you need to select the target network your virtual machine's network interface will map to.
The OS Fixup Settings step is the Operating System Fixup selection. This option will only need to be set on "Don't use Operating System Fixup", because the reevert Appliance will not utilize it.
The Transfer VM Settings step is where you setup the network settings for the transfer VM. Please note: these are not the final network settings for your appliance. Once set, click Next to start the import.
Once the import is done, you will need to run the appliance.
For more information on how to add more CPU or memory resources to your appliances, or add and / or delete virtual drives, please visit the Citrix Xen Server documentation here.
Additional Deployment Information
Changing Appliance IP Configuration
In the situation where you have to temporarily assign a manual IP address to the appliance, you will need to have access to the appliance console to configure the IP settings during boot. This is for those instances where your network does not have a DHCP server to assign an IP to the appliance automatically. Once the appliance enters the GNU GRUB menu, press e.
Once there, scroll down using the arrow keys untill you reach the line that starts with linux and press end to reach the end of the line. There you will enter the IP address, Net Mask, Gateway, and DNS server. See below code and screenshot for an example. Once you have entered the information, simply boot the machine by either pressing Ctrl X or F10 to boot. Please note that this is just a one time on the fly IP assignment. This will enable you to get to the WebUI and perform the setup, which will let you save this IP or change it to something else.
ip=10.1.10.212 nm=255.255.255.0 gw=10.1.10.1 dns=10.1.10.10