Was this content helpful?
How could we make this article more helpful?
Import to Seagate Lyve Cloud
Prerequisites
Before you can configure and submit your import plan, make sure to complete the following steps so that Lyve Import Service can securely access your specified Lyve Cloud bucket to import your data:
Lyve Cloud account—Work directly with a Lyve Cloud Expert to create your Lyve Cloud account.
Lyve Cloud bucket—Set up a bucket for your import. To learn more, see Managing buckets.
Bucket permissions—To learn more, see Managing bucket access permissions.
Seagate authorizations—Ensure that Seagate is authorized to read, write, and list to an existing bucket.
Service account—To learn more, see Managing service accounts.
IP address access—If configured by your organization, list Seagate’s IP address(es) as an allowed source. See IP Address Access.
Recommendations
Seagate recommends creating a bucket dedicated to your Lyve project.
Configure your import plan
Enter credentials
An access key and secret key are required to authenticate requests to your cloud resources. To learn more, see Manage service account.
- In Lyve Management Portal, click Import Plans in the navigation bar, and then click Configure Plan.
- Enter your access key and secret key. (If you need to update the import destination first, click on the Import Destination step and edit.)
- Enter your bucket name.
- (Optional) Enter a name for your folder.
Each storage device in your project will have a designated folder in your bucket. The device’s serial number will be automatically appended to the folder name at the time of import.
- Provide a name for Seagate to use to create the folder(s) in your bucket on your behalf. (Recommended)
- If you leave this field blank, Seagate will create a folder(s) for your files and will use the device’s serial number as its name.
- Alternatively, if you have an existing folder within your bucket that you would like to import your files to, provide the name of this folder.
- Important—Make sure that your bucket policy does not block folder creation. If you are providing a name for a new folder to be created, ensure that the name follows the Naming Guidelines.
- Click Validate Credentials.
- Check the box to confirm that you have read and understand the details in IP Address Access.
- Click Next.
Review and submit your import plan
- Review your import destination and credential details. If you need to make changes to the credentials provided, click the Edit icon.
- Check the box to confirm that you've read and understand the information in this reference guide.
- Click Submit Plan.
Inviting another user to configure an import plan
If a different member of your organization needs to configure the import plan for a project, you can invite them to do so in Lyve Management Portal. See Invite Another User to Configure an Import Plan.
Naming guidelines
| Safe characters | |
|---|---|
| Alphanumeric characters | |
| 0-9 | numerals |
| a-z | lowercase letters |
| A-Z | uppercase letters |
| Special characters | |
| * | asterisk |
| ! | exclamation point |
| - | hyphen |
| ( | parenthesis (open) |
| ) | parenthesis (close) |
| . | period |
| ' | single quote |
| _ | underscore |
| Characters to avoid | |
|---|---|
| & | ampersand |
ASCII characters
|
|
| @ | at sign |
| \ | backslash |
| ^ | caret |
| : | colon |
| , | comma |
| { | curly brace (left) |
| } | curly brace (right) |
| $ | dollar sign |
| = | equal sign |
| / | forward slash |
| ` | grave |
| < | greater-than symbol |
| > | less-than symbol |
| % | percent sign |
| | | pipe or vertical bar |
| + | plus sign |
| # | pound character |
| ? | question mark |
| " | quotation mark |
| ; | semi-colon |
| space - sequences with spaces, especially multiple spaces, may be lost | |
| [ | square bracket (left) |
| ] | square bracket (right) |
Note the following additional requirements:
- An object name matching a prefix is not supported. For example, an object with the name /A/B, where A is a prefix and B is the object name, should not be imported with another object named A.
- A standalone period . in the prefix folder is not supported.
- A standalone period . as an object name is not supported.
Best practices
See the following knowledge base article:
Troubleshooting
See the following knowledge base articles: