Moving Virtual Disk – The VDI Mirroring cannot be performed

Ever attempted a VM move or Move Virtual Disk function in Citrix XenCenter on a live VM encountering “Moving Virtual Disk (name of Virtual Disk) The VDI Mirroring cannot be performed?”

Citrix XenServer Toronto, Citrix XenServer Mississauga, Citrix XenCenter Toronto, Citrix XenCenter Mississauga


  1. Remove all snapshots from existing VM.
  2. Use the Migrate VM Wizard and explicitly set a Home Server.
  3. If you are running a hypervisor pool, Select any other server to be the home server other than the server currently hosting that virtual disk.


Citrix XenServer Toronto, Citrix XenServer Mississauga, Citrix XenCenter Toronto, Citrix XenCenter Mississauga


These issues typically happen when you are transferring a live VM by using XenMotion, and something with the Virtual Disk and VDI go amiss. If down time is an option, you will be able to clone by shutting the VM down for a few minutes and moving the VM that way. Another way to recover without down time is by creating a snapshot of the VM, and then creating a new VM from that snapshot. If the operating system boots, you’ll have a new VM copy running simultaneously with the original VM copy. From there you may move the original and then shut down the new VM copy for later if the VM’s data doesn’t change much. You’ll also be able to shut down the VM to make any custom repairs using xe cli commands in the XenServer shell


HPE ProLiant DL380 Gen10 6130 2P Performance Server

Check out this machine. Packed with so many features in a small 2U box. Contact us for our price. We’ll offer a competitive deal on this product.

HP ProLiant DL380 Gen10

Why not buy 2 for added fault-tolerance?

Lots of storage bays for virtually any configuration. This system has no hard drives installed, which is okay for many IT techs who would like to choose their hard drives. You may call us for a quote for the hard drives. Hard drives vary in price depending on individual needs, so let us know what your daily network workload is.

64 GB RAM installed provides all the physical server memory available for large amounts of data, plus room for virtual machines, plus more room for memory expansion.

Lots can be done with just this box. Those with a server room full of old tower gear could easily consolidate the workload into this machine or two of them.

HPE ProLiant DL380 Gen10 6130 2P 64GB-R P408i-a 8SFF 2x800W PS Performance Server

Technical Specifications

Processor: Intel® Xeon® 6130 (16 core, 2.1 GHz, 22 MB, 125W)
Form Factor: 2U ( not too thin, not too large )
Power supply: 2 HPE 800W Flex Slot Platinum hot plug power supplies (very nice for high-availability service)
Expansion slots: 6 PCIe 3.0
Maximum Supported Memory: 1.5 TB, memory supported differs by processor selection
Amount of Installed Memory: 64 GB (2x 32 GB) RDIMM
Total Memory Slots: 24 slots
Memory type: HPE DDR4 SmartMemory
Included hard drives: None ship standard, 8+2 SFF SAS drives supported
Optical drive type: DVD-RW
System fan features: 6 single rotor fans included
Network controller: 1 HPE 1 Gb 331i Ethernet adapter, 4-ports per controller and 1 HPE 10/25 Gb 2-port 640FLR-SFP28 Ethernet adapter
Storage controller: 1 HPE Smart Array S100i and 1 HPE Smart Array P408i-a SR Gen10 controller
Minimum dimensions (W x D x H): 44.55 x 73.03 x 8.74 cm
Weight: 14.76 kg

Infrastructure management

HPE iLO Standard with Intelligent Provisioning (embedded), HPE OneView Standard (requires download) (standard)
HPE iLO Advanced, HPE iLO Advanced Premium Security Edition, and HPE OneView Advanced (optional)


3/3/3 – Server Warranty includes three years of parts, three years of labor, three years of onsite support coverage. Additional information regarding worldwide limited warranty and technical support is available at:

APACHE .htaccess – Giving WordPress Its Own Directory With Main App

htaccess for WordPress within a subfolder or subdirectory and keep your custom PHP site or framework

When the following instructions were applied from,, my main website’s home page continued to work properly, though all child links routed to apache’s default 404 Not Found page.  Our links get a 404 Not found, because there are simply no existing files there to serve those URI requests. Everything on our primary domain points to a single index file. We’ll call the file main.php for your reference.

If you run a custom website that also serves your internal links and you would like to preserve your core functionality, and serve WordPress in a subdirectory, try these instructions instead.

NOTE: If this .htaccess configuration works for people, I encourage them to cite my article when sharing this configuration method.



RewriteEngine on
# For default app or website in root
RewriteCond %{HTTP_HOST} ^(www.)?$
RewriteCond %{REQUEST_URI} /
RewriteRule ^main\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /main.php
# Snippet of WordPress instructions as directed at their codex
RewriteCond %{HTTP_HOST} ^(www.)?$
RewriteCond %{REQUEST_URI} ^/blog
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ /blog/$1
RewriteCond %{HTTP_HOST} ^(www.)?$
RewriteRule ^(/)?$ blog/index.php [L]
This is the .htaccess code snippet to be installed at your root directory of your custom website or whichever app is located at root. The IfModule conditional element tags for modrewrite.c have been left out here for the sole purpose of publishing in this blog.



^main\.php$” & “main.php” point to the site’s main DirectoryIndex or handler file for internal routes. Replace main with the filename of your index file.

Replace “” with your real-life domain name. Be sure to find and replace all applicable instances of with yours.

blog” represents the subdirectory names. In a WordPress subdirectory installation, this is where you store and/or extract your WordPress files.

Hope this helps somebody. If you need any break / fix / custom / advanced web or wordpress work, please visit our WEBSITE.