Cloud Migrate User Manual 
Cloud Migrate User Manual 

Was this content helpful?

OPEN MENU CLOSE MENU

Create New Plan

A plan contains the settings and configuration for a migration. It specifies the source and destination and determines whether the migration runs once or on a recurring basis.

  1. In the sidebar, select Migrations > Plans.
  2. Select New Plan in the upper-right screen.

cloud-migrate-new-plan-button-01

Prerequisites

Add details about the cloud source.

  1. Edit the following:
Source CloudSelect the appropriate source cloud.
Source RegionSelect the appropriate source region.
  1. Select Next.

Add source credentials

Add source credentials and assign a bucket.

 Amazon S3 customers—Proceed to the instructions in Amazon S3 credentials below.
  1. Edit the following:
Source Access KeyEnter the access key for the source cloud.
Source Secret KeyEnter the secret key for the source cloud.
Source Endpoint URLEnter the URL for the source endpoint.
  1. Select Validate.
 If the validation fails, re-enter the source credentials and try again.
  1. Use the dropdown to select the source bucket/container name.
  2. (Optional) Enter a prefix that will be used to filter object filenames during migration.
 Prefixes are common way to filter objects. You can use a prefix to copy only files that begin with the specified prefix.
  1. Select the IP Address Access link to read about access requirements for data migration. Select the checkbox to confirm that you understand the information provided.
  2. Select Next.

Amazon S3 credentials

Configure your Amazon S3 bucket for migration to Lyve Cloud:

  • If necessary, set up an AWS account. 
  • Create a dedicated bucket for your migration. See Creating a bucket. 
  • Create an identity and access management (IAM) role and supporting policy. See Providing access to AWS accounts owned by third parties. 
  • Seagate requires the following permissions to perform the import: 
    • s3:AbortMultipartUpload 
    • s3:CreateBucket 
    • s3:DeleteObject 
    • s3:GetAccelerateConfiguration 
    • s3:GetBucketLocation 
    • s3:GetObject 
    • s3:GetObjectAttributes 
    • s3:ListBucket 
    • s3:ListBucketMultipartUploads 
    • s3:ListMultipartUploadParts
    • s3:PutObject
 If you do not have permissions to administer IAM roles or policies, contact your AWS account owner or IAM administrator.
  1. In Lyve Cloud, enter your AWS account ID. This is a 12-digit number that uniquely identifies your account. See View AWS account identifiers.
  2. Enter your Amazon S3 bucket name.
  3. Select Validate.
  4. To specify that all versions of the object should be migrated to the destination, set the Include all versions switch to ON. Set the switch to OFF if only the most current version of objects should be migrated.
  5. Select the IP Address Access link to read about access requirements for data migration. Select the checkbox to confirm that you understand the information provided.
  6. Select Validate.
 If the validation fails, re-enter the source credentials and try again.

Add destination credentials

Use an existing Lyve Cloud bucket

Add source credentials and assign a bucket.

  1. Edit the following:
Lyve Cloud Destination Access KeyEnter the access key for the Lyve Cloud destination.
Lyve Cloud Destination Secret KeyEnter the secret key for the Lyve Cloud destination.
  1. Confirm that the Lyve Cloud Destination endpoint URL is correct.
  2. Select Validate.
 If the validation fails, re-enter the source credentials and try again.
  1. Use the dropdown to select the source bucket/container name.
  2. Select the IP Address Access link to read about access requirements for data migration. Select the checkbox to confirm that you understand the information provided.
  3. Select Next.

Select settings

Select the settings you want applied to the migration.

Full sync

In a full sync, source objects will overwrite objects in the destination folder with the same name.

To specify a full sync migration:

  1. Use the Sync Type dropdown to select Full.
  2. Select Next.

Incremental sync (coming soon)

Incremental syncs are designed to optimize the transfer process by avoiding the need to migrate unchanged files. Two incremental sync modes are available in Lyve Cloud:

  • Name Differential Sync—Transfers only source objects that do not exist in the destination.
  • Name & Time Differential Sync—Transfers source objects that do not exist in the destination, as well as any objects that have changed (files that have been renamed, opened, or with changed time stamps).

To specify an incremental sync migration:

  1. Use the Sync Type dropdown to select Incremental.
  2. Select Name Differential Sync or Name & Time Differential Sync.
  3. (Optional) Schedule a repeating transfer (see Schedule repeating transfers below).
  4. Select Next.

Schedule repeating transfers (coming soon)

  1. Select the Schedule the repeating transfer checkbox.
  2. Edit the following:
Start DateSelect the field and use the calendar widget to specify a start date.
Repeat everyUse the dropdown menus to set the repeat cycle.
Start timeUse the dropdown menus to specify the time of day when transfers will start.
DaysSelect/unselect days to specify when transfers will start.
End dateUse the dropdown to specify an end date for the repeating transfers. Alternatively, select Remove end date to repeat transfers indefinitely.

(Optional) Set up notifications

You can receive email notifications related to the migration.

  1. Check the Receive notifications for this job via email checkbox.
  2. Enter an email address.
  3. Select Next. 

Review plan

  1. Review the details of your plan, including:

    • Source details
    • Destination details
    • Settings
    • Notifications
  1. Select the Lyve Cloud Terms & Conditions link. Select the checkbox to confirm that you understand the information provided.
  2. Select Submit.

Cloud Migrate User Manual 

Click here to access an up-to-date online versionof this document. You will also find the most recent content as well as expandable illustrations, easier navigation, and search capability.