Oracle Cloud Infrastructure Documentation

Installing Storage Gateway

This topic describes the requirements for and step-by-step instructions for installing Storage Gateway.

Hardware Recommendations and Requirements

You can install Storage Gateway in an Oracle Cloud Infrastructure compute instance or on an on-premises host. If you are installing on an on-premises host, that host must meet the following requirements:

  • Two dual-core CPUs (4-core CPUs recommended)
  • Recommended local storage disk size: 600 GB (500 GB for file system cache, 80 GB for metadata storage, 20 GB for log storage)


    Provision local storage before installing Storage Gateway. For best performance, allocate dedicated local storage for each Storage Gateway file system and associated metadata and logs. The installation script prompts you for the paths to your Storage Gateway file system cache, metadata storage, and log storage locations. Follow the stated disk size recommendations.

    We recommend using the XFS file system for file system cache, metadata, and logs. XFS is a 64-bit file system that is designed for parallel I/O. Parallel I/O allows a system to scale based on the number of I/O threads and file system bandwidth.

  • Minimum memory requirements:

    • 16 GB for required for any Storage Gateway file system
    • 32 GB for file systems up to 50 million files
    • 64 GB for file systems up to 100 million files

Software Requirements

  • Oracle Linux 7 with UEK Release 4 or later


    If you are installing Storage Gateway in an Oracle Cloud Infrastructure compute instance, the instance creation wizard provides the option to choose the image operating system.

  • Docker 1.12.6 or greater

    Docker is an open platform for building, shipping and running distributed applications. For more information, see

  • NFSv4


Docker and the NFS protocol are installed automatically during the Storage Gateway installation.

Installing Storage Gateway

An installation script guides you through the Storage Gateway installation. Upon successful installation, you are provided with the following:

  • URL to use to log in to the Storage Gateway management console (if installing on an on-premises host)
  • NFS port number
  • Example mount command for mounting your Storage Gateway file systems
To install Storage Gateway

Additional Steps Required for Compute Instance Installations

If you installed Storage Gateway in an Oracle Cloud Infrastructure compute instance, that instance must be able to receive HTTPS connections from other hosts. To open port 443 for TCP traffic, add a new ingress rule to the security list. For complete details, see Security Lists.

To add a new security rule

Verifying and Updating the Storage Driver in Docker

  1. Start docker:

    sudo systemctl start docker
  2. Verify the information in docker:

    sudo docker info
  3. Look for Storage Driver in the output. For example:

    Containers: 0
     Running: 0
     Paused: 0
     Stopped: 0
    Images: 0
    Server Version: 18.03.1-ol
    Storage Driver: overlay2
     Backing Filesystem: xfs
     Supports d_type: true
     Native Overlay Diff: false
    Logging Driver: json-file
    Cgroup Driver: cgroupfs
     Volume: local
     Network: bridge host macvlan null overlay
     Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
    Swarm: inactive
    Runtimes: runc
    Default Runtime: runc
    Init Binary: docker-init
    containerd version: 773c489c9c1b21a6d78b5c538cd395416ec50f88
    runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
    init version: 949e6fa
    Security Options:
      Profile: default
    Kernel Version: 4.1.12-124.15.4.el7uek.x86_64
    Operating System: Oracle Linux Server 7.5
    OSType: linux
    Architecture: x86_64
    CPUs: 4
    Total Memory: 13.45GiB
    Name: ocisg-mahesh
    Docker Root Dir: /var/lib/docker
    Debug Mode (client): false
    Debug Mode (server): false
    Experimental: false
    Insecure Registries:
    Live Restore Enabled: false
    Registries: (secure)

    If Storage Driver is notdevicemapper, perform the following steps:

    1. Stop docker:

      sudo systemctl stop docker
    2. Look for /etc/docker/daemon.json in the host.

      If the file daemon.json does not exist, then create it.

    3. Add the following text in daemon.json to set the variable storage-driver to devicemapper :

      "storage-driver": "devicemapper" 
    4. Restart docker:

      sudo systemctl start docker
    5. Verify the information in docker:

      sudo docker info

      Look for Storage Driver in the output and verify that the storage driver is devicemapper.

Next Step

Logging In to Storage Gateway Management Console