...
Plugin the USB key into the Transporter device.
Plug the Transporter device and computer/laptop into the same network switch.
Power on the device. The device will be accessible via the network and the will start up. Consult the sheet that came with the device for the URL to enter into your browser to view the console.
...
The boot process for Perifery Transporter can takes take a few minutes, depending on the amount of data stored. No action is required on your part.
...
During boot, Perifery Transporter progresses through the following stages:
...
When the boot is complete, it shows a confirmation message.
...
| Info |
|---|
Perifery Transport Transporter performs these same steps on every boot. |
...
Click
to copy everything in one go. Click
to copy one by one.
Uploading content using S3
...
| Info |
|---|
These access URLs and tokens will be required while performing Move operation. |
You can use any S3 tool to upload content to Perifery Transporter. Here is an example of Cyberduck for illustrative purpose, but the same information may be used for any application that uses an S3 connection.
...
.
...
...
Choose Amazon S3 from the dropdown list of protocols.
...
Fill in the following fields:
Server – The hostname of the Perifery S3 endpoint URL.
Port – A port in the Perifery S3 endpoint URL.
Access Key ID – The Perifery S3 Access Key.
Secret Access Key – The Perifery S3 Secret Key.
Verify that the URL in Cyberduck matches the Perifery S3 Endpoint URL (it is okay if the port is not shown in the Cyberduck URL).
...
Click Connect.
...
Browse to the target S3 bucket in Cyberduck.
View Content Portal
...
For detailed information about how to connect to upload content to S3 using Cyberduck, see <link>.
View Content Portal
Another way to upload content to the Perifery Transporter is using Content Portal, which provides multiple functionalities to safely store and manage content (bucket, objects, etc.) in no time.
Navigate to Advanced > Manage content > click the “Manage Content” link. This will open the Content Portal in a new browser tab to view and manage all the content (bucket, objects, etc.).. For more information about Content Portal, see Using the Content UI.
...
Data Migration
Perifery Transporter allows migrating bucket content to a remote S3 destination.
...
To move a bucket content, refer to the following steps:
...
Click corresponding to the bucket. It displays a form in the sliding panel.
...
Fill in the required fields marked with asterisks (*):
S3 endpoint URL – The target S3 endpoint URL.
S3 region – Optional, a geographic area of the storage.
S3 bucket – The target S3 bucket where the content is to be moved.
Remote folder – Optional, a folder path within the remote bucket.
Access key – An access key for the remote bucket. It must be generated within the remote cloud storage service.
Secret key – The S3 secret key that is generated with the access key.
Click Move. A confirmation message appears.
...
Generate report
When data is moved, irrespective of whether it is failed or successful, the report icon gets enabled for that bucket.
Refer to the following steps to generate a report:
Click
corresponding to the bucket.Scenario 1: For successfully migrated data, the report provides a preview of bucket content as shown below:
Scenario 2: In case of failed data migration, the report shows the cause of failure.
Click Download. It will either download or pop up in a browser tab depending on how the browser handles the content type of the JSON file.
...
After successfully uploading content to Perifery Transporter, you can migrate it to any remote S3 destination. For step-by-step guidance, see https://perifery.atlassian.net/wiki/spaces/DOCS/pages/3132293151/DRAFT+Transporter+User+Guide#Data-migration.