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
      • Environmental and Machine Requirements for Migration
      • Introduction to VirtaMove Application Migration
      • Activating Your VirtaMove License
      • Migrating an Application
      • Migrating an IIS Application
      • Using VirtaMove Source Monitor
      • Monitoring Migration
      • Running and Exercising Your Application
      • Dissolving Your Application
      • Advanced Application Migration
        • Config-on-the-Fly
        • Global COTF Utility
        • Creating a Config-on-the-Fly File
        • Considerations When Compressing and Moving a Container
    • 04. Administration Guide
    • 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.
    /
    Considerations When Compressing and Moving a Container
    Updated Mar 28, 2022

      Considerations When Compressing and Moving a Container

      Compressing a container (virtacompressPreview) will copy a custom COTF file specified during migration into the scripts folder of the container and automatically update the CPROP_CONFIG_FILE property to reference the new location of the COTF file.

      If custom script files are required for the tethering process, or for executing special actions related to your migrated application, place the scripts in the container's scripts folder before you compress and move the container.

      If tether is enabled for a container and you compress a container, the CPROP_USE_TETHER property for the .cap file will be set to "N". Compressing will untether the container, and credentials to the source machine will be lost. You will have to enable tether again and specify credentials once again as required after you uncompress the container on a new destination.

      {"serverDuration": 12, "requestCorrelationId": "0a7a096d54a143598b816d12b63b5fac"}