Import to Microsoft Azure Blob Storage
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 Azure container to import your data:
Azure subscription—Set up an Azure free account.
Azure storage account—Set up an Azure storage account. To learn more, see Create an Azure storage account.
Azure container—Set up a dedicated container for your import. To learn more, see Create a container.
Seagate authorizations—Ensure that Seagate is authorized to read, write, and list to an existing container.
IP address access—If configured by your organization, list Seagate’s IP address(es) as an allowed source. See IP Address Access.
Additionally, see How to configure the Azure Storage Firewall.
Recommendations
Seagate recommends creating a container dedicated to your import plan.
Important note on file sizes—In general, Seagate does not recommend importing individual files larger than 5TB. Please refer to your cloud provider's file size limitations and best practices.
Add your cloud destination credentials and container information to configure your cloud import plan.
- All devices within a subscription must be imported to the same destination and region.
- You will be required to enter and validate your container credentials.
- On your Home page, select a Lyve Mobile service subscription that includes a Cloud Import plan.
Alternatively, select the More icon in the 'Actions' column, and then select View Subscription.
- Select the link at the top of the page:
- Confirm the Cloud Destination and Region. Select Next.
- Add the Storage Account Name and Storage Account Key for your cloud destination. Specify an existing container for the subscription. Select Validate Credentials.
If the validation fails, check that the Storage Account Name, Storage Account Key, and Container entered are accurate, and then revalidate.
- (Optional) Under 'Customized Path', provide the name of an existing folder or provide a folder name for Seagate to use to create a new folder for import. If you don’t provide a folder name, Seagate will create a folder based on the device serial number and date.
Each storage device in your import plan will have a designated folder in your container. 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 container 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 container that you would like to import your files to, provide the name of this folder.
- Important—Make sure that your container 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.
- To enable the checkbox, select the IP Address Access Guide link.
- Select the checkbox, and then select Submit.
Inviting another user to configure an import plan
If a different member of your Org needs to configure the import plan for a Lyve Mobile subscription, you can invite them to do so in Lyve Management Portal.
- The person must be a member of the Org containing the Lyve Mobile subscription to which you want to add the import plan. See Manage Org members in the Lyve Management Portal User Manual.
- The member must be given the Manage Import Plans permission. See Manage subscription members in the Lyve Management Portal User Manual.
Naming guidelines
Note the following naming guidelines:
- Every folder within a container must have a unique name.
- A folder name can contain any combination of characters.
- For blobs in Azure Storage, a folder name must be at least one character long and cannot be more than 1,024 characters long.
- Folder names are case-sensitive.
- Reserved URL characters must be properly escaped.
- Avoid folder names that end with a dot . , a forward slash / , or a sequence or combination of the two.
For additional information on naming folders, see Naming and Referencing Containers, Blobs, and Metadata.
Best practices
See the following knowledge base articles:
Troubleshooting
See the following knowledge base articles: