Please follow these four simple steps to begin using Perifery Transporter:
| Table of Contents | ||||
|---|---|---|---|---|
|
In the
...
box
The following items should be are present:
The Perifery Transporter device
A License USB key
A sheet with information about connecting to the device
Step 1: Set up
The whole setup needs three steps:
Plugin Plug the License USB key into the Perifery Transporter device.
Plug the Transporter device and computer/laptop into the same network switch.
Power on the device. Now, the The device will be accessible via the network and the reboot process will start.
Reboot
Reboot takes a few minutes to start the Perifery Transporter so please wait until the reboot process is finished. You will see the following screens during the reboot:
...
will start up. Consult the sheet that came with the device for the URL. Enter the same URL
...
into
...
the browser to view the console.
...
Boot
The boot process for Perifery Transporter can take a few minutes, depending on the amount of data stored. No user action is required.
...
A confirmation message displays when the boot is complete.
...
| Info |
|---|
Perifery Transporter performs these same steps on every boot. |
Step 2: Login
...
Enter the default username and password available on the sheet that came with the device.
Username – periferyadmin
Password – password
Click Login.
| Info |
|---|
Login will not be possible until all the services have fully come online. This may take several minutes. |
Step 3: Update your password
This is a one-time update for step is applicable to the first-time login useronly.
Enter the new password and re-enter it to confirm.
Click Update password.
A confirmation message appears saying that ‘Password updated successfully’.
Step 4: Dashboard
The dashboard screen provides:
...
Status overview – Provides the current state of hardware (CPU, RAM, network, and disks) and transporter Perifery Transporter services.
- Shows all the hardware/services are working fine.❗ – Shows all the hardware/services are not up and running as expected.
Storage – Provides the total storage space of the device and how much space has been consumed in a bar format.
How to connect
This section is used to copy access URLs and tokens. Choose either option to copy and save access URLs and tokens information in a text document or email:
Click
to copy everything in one go. Click
to copy one by one.
| Info |
|---|
Info Access URLs and tokens will used later to perform the Move operation. |
How to upload content using S3?
Cyberduck is being used for illustrative purposes, but Use any S3 tool to upload content to Perifery Transporter. Here is an example of Cyberduck for illustrative purposes; the same information may be used for any application that uses an S3 connection.
...
Launch Cyberduck and click Open Connection.
...
.
...
...
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.
...
For detailed information about how to connect to upload content to S3 using Cyberduck, see https://perifery.atlassian.net/wiki/spaces/DOCS/pages/3132293151/DRAFT+Transporter+User+Guide#How-to-connect.
View Content Portal
...
Navigate to Advanced > Manage content > click . It leads to the Content Portal to view all the 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.).
Data Migration
It is used to migrate 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 – A target S3 endpoint URL.
S3 region – A geographic area of the storage.
S3 bucket – A target S3 bucket where the content is to be moved.
Remote folder – 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 – An 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.
...
Navigate to Advanced > Content Management > click Manage Content. This will open the Content Portal in a new browser tab. For more information about Content Portal, see Using the Content UI.
...
Data Migration
After successfully uploading content to Perifery Transporter, 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.