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
      • Introduction the Administrative Console
      • Managing the Security Key
      • Managing Container Settings
      • Docking and Undocking Containers
      • Updating the VirtaMove Activation Code
      • Managing Tethered VAAs
        • VirtaMove Source Agent
        • Viewing Container Messages and Errors
        • Running VirtaDebug
        • Modifying Credentials
        • Managing Source Products
        • Managing Source Services
        • Managing Source Accounts
        • Migrating Scheduled Tasks 2
        • Migrating COM, COM+ and DCOM Components
        • About Shared Folders
        • Migrating Folders, Shared Folders, and Registries
        • Using Tether Sync
        • Resetting a Container
        • Disabling Tether
        • Dissolving a Container
        • Using Sync into Dissolve
      • 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.
    /
    Using Sync into Dissolve
    Updated Mar 28, 2022

      Using Sync into Dissolve

      If you have Dissolved a container application onto the destination machine but want to sync the application between the source and destination machines, you can use the virtasync command to accomplish the update.

      This command syncs only the artifacts that were copied and dissolved; it will not copy newly discovered artifacts in the source machine. For example, if artifacts A, B, C were copied into a container and then dissolved onto the destination machine, then executing Sync into Dissolve will update A, B, C on the destination machine. If new artifacts (e.g., D and E) are detected on the source machine, they will not be brought over or synced across because they were not known by the container before the container was dissolved.

      You can sync using Reset or Update sync modes. See Using Tether SyncPreview for more information.

      To Use Sync into Dissolve using the CLI

      Sync will take place if CPROP_SYNC_INTO_DISSOLVE is set to Y via virtapedit.

      Perform Tether Sync in a command prompt window as follows:

      1. On the destination machine, undock the container:

        virtaundock c:\appliances\<appliance name>
      2. Dissolve the container:

        virtadissolve c:\appliances\<appliance name>
      3. Re-enable Tether:

        virtapedit c:\appliances\<appliance name> CPROP_USE_TETHER y <source_ip>
      4. Enable Sync into Dissolve:

        virtapedit c:\appliances\<appliance name> CPROP_SYNC_INTO_DISSOLVE y
      5. Execute Sync into Dissolve:

        virtasync c:\appliances\<appliance name> [reset | update]

      Synch into Dissolve Log

      After a sync operation, the following file is created in the container directory:

      VAA name\ctrack\Activity\

      This file contains a log of the operations that occurred during the sync.

      {"serverDuration": 9, "requestCorrelationId": "fd41cc088330408fb092113ce70c73c2"}