Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
VirtaMove Knowledge Center
VirtaMove Documentation
  • VirtaMove Support Knowledge Base
    VirtaMove Support Knowledge Base
     This trigger is hidden
Results will update as you type.
  • V-Migrate Documentation
    • 01. Managing Your VirtaMove Licensing
    • 02. Installation Guide
    • 03. Application Migration Guide
    • 04. Administration Guide
      • Requirements
        • Administrator Privileges
        • Bitness
        • Mapping System Drives
        • Renaming Files and Folders
      • Introduction the Administrative Console
      • Managing the Security Key
      • Managing Container Settings
      • Docking and Undocking Containers
      • Updating the VirtaMove Activation Code
      • Managing Tethered VAAs
      • Managing Container Services
      • Managing Credentials for Container Users
      • Running Containers
      • Moving, Compressing, and Deleting Containers
      • Upgrading Containers
      • Logging
      • Testing Containers
      • Junctions in Windows 2008 R2
    • 05. CLI Guide
    • About VirtaMove V-Migrate Documentation
  • V-Maestro Documentation
  • VirtaLinux Documentation
    You‘re viewing this with anonymous access, so some content might be blocked.
    /
    Mapping System Drives
    Updated Mar 28, 2022

      Mapping System Drives

      VirtaMove supports the deployment of containers where the source and destination machines have different system drives. However, the destination machine must have a local drive assigned the same drive letter as the source machine’s system drive.

      You can use the https://virtamove.atlassian.net/wiki/spaces/VDOC/pages/314114486/virtavdrive?search_id=3ee06282-3e86-4399-9a65-04f234c3ca98 command to map the system drive from the source machine to a system drive on the destination machine.

      For example:

      Scenario 1:

      Source machine
      Local Drives: C:
      System Drive: C:

      Destination machine
      Local Drives: E:
      System Drive: E:

      virtavdrive c:\appliances\mycontainer move c e

      Scenario 2:

      Source machine
      Local Drives: C:, E:
      System Drive: E:

      Destination machine
      Local Drives: C:, E:
      System Drive: C:

      virtavdrive c:\appliances\mycontainer move e c

       

      {"serverDuration": 9, "requestCorrelationId": "06879b14df0e476698c9027e05a2d74c"}