You can configure CloudPools so that data that is archived to, or recalled from, a public cloud provider is routed through a proxy server.
By default, CloudPools communicates directly with the designated cloud provider. If the cloud provider is private, the default communication protocol might be acceptable. Example private providers are another
Dell TechnologiesPowerScale cluster or an ECS appliance running on the same corporate network.
However, when CloudPools archives data to a public cloud provider, such as Amazon S3, communication occurs through the public Internet. This protocol might violate your organizational security policies.
In a typical configuration, a
PowerScale cluster is installed in a data center behind one or more firewalls. Ports that enable communication to the public Internet are closed. To enable CloudPools to archive data to a public cloud provider, you can configure it to work with a proxy server.
CloudPools works with proxy servers running the following protocols:
SOCKS v4
SOCKS v5
HTTP
Configuration on the CloudPools side includes creating a network proxy entry and connecting the network proxy to a cloud storage account. Both SOCKS v5 and HTTP can be configured with or without authentication. SOCKS v4 does not support authentication.
From OneFS, you can also list network proxies, view network proxy properties, modify proxy settings, and delete proxies. Except for connecting the network proxy to a cloud storage account, you must use the CLI to run all other proxy server commands.
For details about creating a network proxy, see the
OneFS CLI Administration Guide or the
OneFS Web Administration Guide.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\