Access to Nodeum Container

Access to Containers from Windows, MacOS and Linux

The containers can be reached for accessing Archived Data, it is a virtual file system containing a complete file(s) and folder(s) structure. The file system used an internal cache system and is extended with secondary storage volumes.

The solution supports the following protocols :

and Operating Systems :

Windows 7, 8, 10
MacOS
Linux

Container Access through SMB

Windows based Operating System

Go through the command line and type the command to access Network File Explorer : \\nodeumhostname\
In this screenshot, "nodeum-prod.mt-c.local" is the hostname.
You will then see the list of container available into your Nodeum. In this example, "archive" is a valid defined container. Then click on the icon to access it.
If you have configured Nodeum with Active Directory, this windows will not appear ; if you have configured Nodeum with local user account, you will have to use your Nodeum's local user name and password to access the Container.
Once autorized, the you will see the contents available in the container as a normal Network Shared Folder.

MacOS based Operating System

Access the Go menu in the top bar of your MacOS and go to "Connect to Server" option.
Then you type into the address list, the Nodeum hostname, such as smb://nodeumhostname, and click on "Connect" button :
If credentials are well set, you can then access the contents of the Network Shared Folder :

Linux based Operating System

In your Linux terminal, mount the container (named archive in the example) in using SMB protocol. Verify that you have the right package installed :
```
# sudo yum install cifs-utils
# sudo mount.cifs //nodeum-prod.mt-c.local/archive /mnt/testmnt -o user=johndoe,pass="secret"
```
In this example:
nodeum-prod.mt-c.local : hostname of server
/archive : Container name into Nodeum
/mnt/testmnt : access point in your linux system. In the best practice, the name "testmnt" must be choosen according the container name.
-o user=johndoe,pass="secret" : johndoe is a user who have access to the container and "secret" is the password of the user.
t is also possible to add this mount point in /etc/fstab :
```
...
//nodeum-prod.mt-c.local/archive /mnt/testmnt cifs credentials=johndoe 0 0
...
```
In your Linux terminal, mount the container (named archive in the example) in using either NFS protocols. Verify that you have the right package installed :
```
# sudo yum install nfs-utils nfs-utils-lib
# sudo mount -t nfs -o vers=4 nodeum-prod.mt-c.local:/archive /mnt/testmnt
```
It is also possible to add this mount point in /etc/fstab :
```
...
nodeum-prod.mt-c.local:/archive /mnt/testmnt/ nfs rw,sync,hard,intr 0 0
...
```
Container Access through S3

Different S3 clients are available to connect to a S3 bucket, we will use in this example rclone. We assume that a stable version of rclone is installed correctly. rclone is easy to install and is compatible with different operating systems : Windows, Linux or MacOS. rclone configuration is based on a config file which contains all informations related to the different endpoints available.

Rclone Config File
```
[nodeum]
type = s3
access_key_id = xxxx
secret_access_key = xxxx
endpoint = http://nodeum.mt-c.local:9000
```
List all directories/containers/buckets in the path
```
C:\Program Files\rclone>rclone lsd nodeum:
-1 2021-11-04 14:42:42 -1 emptycontainer
C:\Program Files\rclone>
```
List all contents and directories in the path
```
C:\Program Files\rclone>rclone ls nodeum:emptycontainer
31373 items.png
2162147328 linux-20.2-64bit.iso
8508953 tn5250j-0.8.0-beta2.zip
C:\Program Files\rclone> 
```
Copy contents to a Nodeum Container
```
rclone copy "C:\Users\JohnDoo\Downloads\linux-20.2-64bit.iso" nodeum:/emptycontainer --no-check-dest --s3-no-check-bucket
```
Copy contents from a Nodeum Container
```
rclone copy nodeum:/emptycontainer "C:\Users\JohnDoo\Downloads\linux-20.2-64bit.iso" --no-check-dest --s3-no-check-bucket
```
Specific Parameters

--no-check-dest : (optional) - recopy all contents even if already exst at destination
--s3-no-check-bucket : (mandatory) - do not do an auto creation of the bucket

Related Categories

Active Archive

Subscribe to Email Updates

Access to Nodeum Container