Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Align
aligncenter

Image Removed

     Content Without Boundaries

Image Added

On This Page

Table of Contents

Overview

Virtual versioning is a DryvIQ feature that allows the transfer of versioned content. With this feature, all versions of a file will be preserved when transferring into a storage platform that does not support versioned content (i.e. network file system or file share). Versioned information displays differently on platforms that don’t support versioning versus how it displays on platforms that support versioning.

When transferring from a platform that supports versioning to one that does not, the format on the destination would look like this:

On the Destination with Virtual Versioning

file1.txt, file1.txt[1], file1.txt[2], where file1.txt is the current version

When transferring virtual versions to a platform that supports versioning, the format on the destination would look like this:

On The Destination with Versioning

File1.txt (has 3 versions)

Note

Virtual versioning is not globally available; it must be enabled per connection.


REST API | JSON Configuration

Virtual versioning is not globally available; rather must be enabled per connection. 

To enable virtual versioning through the REST API, "versioning": true must be added when creating the connection. See the example below.

Code Block
POST {{url}}v1/connections
{
    "name": "\\\\{{NFS_NAME}}\\{{FOLDER}}",
    "platform": {
        "id": "nfs"
    },
    "auth": {
        "unc": "\\\\{{NFS_NAME}}\\{{FOLDER}}",
        "versioning": true
    }
}