MOVEit Transfer Backup/Restore utility works but not with Blobs. For backing up an MOVEit Transfer file store in Azure Blobs, use AzCopy.

You can use AzCopy to:

  • Create full or incremental backups of your file store. (Using sync flag)
  • Restoring your file store.

Tasks for Backing up Your Blob Service

Follow these steps to perform a one-time backup of your primary file store to a target backup.

Tip: These instructions can also be adapted for sync of a file store contained within an Azure Blob service.

Task

Description

1.

Download and install AzCopy (no install needed for version 10)

AzCopy version 10 is needed for authentication feature.

2.

Give AzCopy access to File Store

Provide access with OAuth (Azure AD) or by using a container level access token.

3.

Run a sync (azcopy sync)

Sync your file store with your secondary storage

Task 1: Download AzCopy

When this topic was written, AzCopy 10 had been released. You can learn and download AzCopy from the Microsoft documentation site.

A couple of features make AzCopy 10 preferable over AzCopy 8. AzCopy 10 provides:

  • Authentication using container-level shared access signatures (SAS).
  • OAuth/login authentication using your Azure Management Portal credentials for Blob Storage Service container access (Azure Storage Blob Data Contributor role is required)

Tip: AzCopy 10 is a free application.

Task 2: Give AzCopy Temporary Access to Your Azure Storage Container

Before you can run a copy or a sync, provide AzCopy with access to your Azure Storage Service.

You can provide AzCopy access in one of two ways:

  • Use the azcopy login command interactively or with an identity string.
  • Append a container-level shared access signature (SAS) to the Blob storage URL.

Use azcopy login Handshake (Interactive)

  1. With azcopy.exe on your search path or in the current directory, run the azcopy login command. For example: 
    C:\Users\midmzops>azcopy login

    AzCopy prompts you with instructions you need to complete an authentication challenge. For example:

    To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code <authCode> to authenticate

  2. Open https://microsoft.com/devicelogin. You will be prompted to select the identity and enter the credentials you use to sign-on to the Azure Management Portal that controls the Storage Service that you want to backup.

    [Microsoft returns/displays a web form where you can enter your <authCode>]

  3. Enter the value given for <authCode> in the web form

    After you enter the code a success message displays. For example:

    Login succeeded.

  4. Proceed to the next Task and run your copy or sync.

Task 3: Run the Copy or Sync

For this section, you will run the copy or sync of Blob resources. You can run a copy or sync only with an Azure user role with Storage Blob Data Contributor access permissions. If your user does not already have these, you will need to go to the Azure Management Portal and assign them.

Tip: You can use AzCopy to copy or sync with a shared file system or additional Azure Blob file store. For details and syntax run azcopy.exe -help.

Run a Backup Copy

  1. Run a copy operation on your MOVEit Transfer Blob storage container. For example: 
    azcopy copy "https://example.blob.core.windows.net/midmz2019" "C:\Users\Administrator\Desktop\Backup\1Feb2019" --recursive

    —where example is your storage service name and midmz2019 is the storage service container.

    —and, where "C:\Users\Administrator\Desktop\Backup\1Feb2019" is the target folder to back up to.

    Backup runs with a GUID for the job ID. This job ID is also used for your log file. For example:

    Scanning...
    Using OAuth token for authentication.
    Job ca7ddf27-a6b7-7c43-5c67-e7f2d155afe5 has started
    Log file is located at: C:\Users\Administrator/.azcopy/ca7ddf27-a6b7-7c43-5c67-e7f2d155afe5.log
    50 Done, 0 Failed, 4 Pending, 0 Skipped, 54 Total , 2-sec Throughput (Mb/s): 192.4471

    Job ca7ddf27-a6b7-7c43-5c67-e7f2d155afe5 summary
    Elapsed Time (Minutes): 0.5006
    Total Number Of Transfers: 54
    Number of Transfers Completed: 54
    Number of Transfers Failed: 0
    Number of Transfers Skipped: 0
    TotalBytesTransferred: 1569461472
    Final Job Status: Completed
  2. Save the log file for future reference.