Upload File to Vultr From Google Drive

Introduction

This guide describes, in full general terms, the steps to import a server to Vultr's cloud VPS hosting. The exact procedure for each Os distribution and virtualization platform varies. Where possible, we've included links to further documentation. Please research the provided links for your configuration before beginning a migration. Please note that Vultr is responsible for the platform infrastructure, just not the administration of VPS instances. You are responsible for the assistants of the VPS deployments on your account. If you have difficulties performing a task in your account portal, delight open up a support ticket.

Import Requirements

Earlier migrating your server, ensure it meets the Vultr requirements:

The server compages must exist x86-64/x64/amd64
The server must use legacy BIOS (non UEFI) boot. Do non create a UEFI organization segmentation.
The server has an appropriate boot loader installed.
The disk must exist 150 GB or smaller.
The server must take the appropriate VirtIO drivers installed and loaded.

Make sure your workstation has plenty free deejay space to convert the disk images into raw format before uploading it to Vultr'south cloud VPS hosting.

1. Make a Fill-in

Before performing any operations on your existing server, brand a full backup and know how to restore information technology.

2. Clean upwards the Server

This step is optional merely highly recommended. Before creating the raw prototype, clean up the server as much as possible. Remove former logs, temporary files, etc. to gratis upward disk infinite. Overwrite gratis disk sectors with zeros to improve compression and wipe recently-deleted information for security. Ii standard utilities to wipe complimentary disk space are zerofree and dd.

Zerofree is the best pick if it is available for your distribution. See the full documentation. Zerofree is likewise available on the SystemRescue live ISO. Case:

          # zerofree -five /dev/sda2

If zerofree is not available, employ dd. This example creates a temporary file with zeros to fill the disk, then deletes the file.

          # dd if=/dev/zero of=/tmpfile bs=4096k; rm -f /tmpfile

For Windows servers, use the sdelete utility. The -z pick will fille the empty space with nada bytes. Download sdelete from the Windows Sysinternals site. Open an administrative control prompt, and run sdelete on the desired book.

          C:\> sdelete -z c:

three. Export the Server Image File

The server capture process varies depending on the source platform. Here are the most common export steps with links to relevant documentation.

Export an On-Premise Virtual Server

If yous take enough disk space bachelor and can do the conversion directly on the host machine, you may skip this step. If yous need to perform image conversion on a different computer or upload it from a different location, you may desire to export your server to external media. Here are instructions for several popular systems.

Microsoft Hyper-V
VMWare
VirtualBox
QEMU

Export a Physical Server

The dd utility is a popular way to capture a raw disk image. The source deejay should exist dismounted before imaging. One common technique is to temporarily kick the server using the SystemRescue live ISO. You will demand to mountain a storage location to save the raw image.

Assuming the server information device is /dev/sda and the prototype will be written to /mnt/usb_external/server_image.img, apply the following control from a root terminal.

          # dd if=/dev/sda bs=1M of=/mnt/USB_external/server_image.img

Two popular options for Windows imaging are ntfsclone, and disk2vhd. The SystemRescue live ISO includes ntfsclone, and the full documentation is available online. Disk2vhd from Microsoft Sysinternals can capture a alive running system. Information technology can also save the resulting image directly on the server, if enough free infinite is available.

iv. (Optional) Test with QEMU

Vultr VPS images are uniform with QEMU. To verify the VirtIO drivers are installed properly, launch the server in QEMU on your local system before uploading it to Vultr. QEMU is available for all platforms.

five. Convert to Raw Format

Vultr requires snapshots in raw image format. If you created a raw epitome with dd, no conversion is necessary. If your exported epitome is non in raw format, utilize the free utilities from QEMU or VirtualBox. Versions are bachelor for Linux, Windows, and macOS.

QEMU

QEMU supplies the qemu-img utility, which converts many formats including:

QCOW2 (KVM, Xen)
QED (KVM)
VDI (VirtualBox)
VHD (Hyper-5)
VMDK (VMware)

Instance:

          $ qemu-img catechumen -f vmdk -O raw image.vmdk paradigm.img

VirtualBox

VirtualBox supplies the VBoxManage utility to catechumen:

VDI (VirtualBox)
VMDK (VMWare)
VHD (Hyper-V)

Example:

          $ VBoxManage clonemedium disk /path/to/image.vdi image.img --format raw

6. Stage the Image for Upload to Vultr

To add the snapshot to your Vultr account, stage the paradigm at whatsoever publicly-accessible URL. Some suggested options are:

Vultr Object Storage
A Vultr Cloud Server (for optional pinch)
Dropbox
Google Cloud Storage (non Google Drive).

(Optional) Use a Temporary Vultr Cloud Server for Pinch

On a irksome internet connection, you can temporary deploy a Vultr Ane-Click LAMP app as a staging location. And so, use scp or rsync to shrink the upload stream and dramatically ameliorate the upload speed.

Deploy a Vultr One-Click LAMP app with an SSD large enough to hold the uncompressed image.
Upload the RAW image with compression. These examples use 192.0.2.123 as the One-Click LAMP IP accost:

Option 1: Employ scp.
From a terminal (or PowerShell on Windows) on your local workstation, employ scp with the -C parameter for pinch.
```
              $ scp -C image.img root@192.0.2.123:/var/www/html/image.img                          
```
Option ii: Apply rsync.
If rsync is available on your workstation, it is faster than scp in most cases.
```
              $ rsync -z --progress image.img root@192.0.2.123:/var/www/html/image.img                          
```
Later on the transfer completes, utilise the public URL of the One-Click LAMP server to add the image as a Vultr Snapshot.
```
              http://192.0.2.123/image.img                          
```

7. Add the Image equally a Vultr Snapshot

Navigate to Products > Snapshots > Add Snapshot in your customer portal.

AddSnapshot

Enter the URL of your image and click Upload.

8. Deploy Server from Snapshot

Restore the server snapshot, post-obit the steps from the VPS Snapshots Quickstart Guide. Make sure the VPS SSD is the aforementioned size, or larger, than the server snapshot.

9. Expand the Filesystem (if needed)

Log into your newly-deployed server. Verify that the disk, partition, and filesystem sizes are correct.

Verify the disk size: fdisk -l
Verify the partition size: parted -fifty
Check the filesystem size: df -h

If needed, use resize2fs to expand the filesystem to the full sectionalization size. Substitute vda1 with your device name.

          $ sudo resize2fs /dev/vda1

Other Resource

Here are links to useful resource when migrating to a new Vultr VPS.

Change the Server Hostname
Vultr Web Panel FAQ
Troubleshooting Vultr Server Connections
Troubleshoot your VPS with Bootable ISOs

Want to contribute?

jacksoneliand.blogspot.com

Source: https://www.vultr.com/docs/import-a-server-to-vultr-vps/