Results 1 to 1 of 1

Thread: Compatibility of ZMC with AWS Storage Gateway

  1. #1
    Join Date
    Dec 2019
    Posts
    18

    Default Compatibility of ZMC with AWS Storage Gateway

    Why AWS with Zmanda 3.6

    Tapes are found to be one of the most reliable backup and disaster recovery solutions. Tapes are one of the most durable solutions for this problem. It is not very often that a disaster occurs in an enterprise and it is highly imperative that backup storage devices have a long lifespan and tapes are claimed to have a lifespan of around 30 years. Tapes are also found to be secure, cost effective and portable compared to other backup solutions like cloud services and disks.

    However, physical tapes are very old, and they can be a hindrance in terms of wasting valuable operational time, capital, and flexibility. It is due to these reasons that AWS Storage Gateway is being offered as an effective solution and Zmanda 3.6 is found to be compatible with this latest technology.

    How to configure AWS Storage Gateway with ZMC?

    Just follow these simple steps on the server where ZMC is installed to configure AWS Storage Gateway with ZMC
    • Install iSCSI-initiators-utils
      # yum install iscsi-initiator-utils
    • Make sure that the iSCSI daemon is running
      # sudo /etc/init.d/iscsi status (Rhel/Centos 5/6)
      # sudo service iscsid status(Rhel/Centos 7)
    • If the iSCSI daemon is inactive, it needs to be started
      #sudo /etc/init.d/iscsi start (Rhel/Centos 5/6)
      #sudo service iscsid start(Rhel/Centos 7)

    • Discover the volume or VTL device targets defined for a gateway
      # sudo /sbin/iscsiadm --mode discovery --type sendtargets --portal [GATEWAY_IP]:3260

      StorageGW-2.jpg
    • Connect to a target
      # sudo /sbin/iscsiadm --mode node --targetname iqn.1997-05.com.amazon:[ISCSI_TARGET_NAME] --portal [GATEWAY_IP]:3260,1 –login
    • There are two things to during configuration.
      • Media changer and tape drives need to be connected to using the previous command before being able to use them.
      • The default block size of data sent for backup is set to 32kB but must be changed to 65kB in the amanda.conf file. The following line must be appended in
        the amanda.conf file.
      device-property "BLOCK_SIZE" "65k"
    • Use the lsscsi –g command, this command gives the user a list of scsi devices connected to the system. The first entry on each line is the scsi_host, channel, target_number, and LUN tuple. These entries are placed in brackets and each element is colon separated. During configuration, the medium changer must have the least number of all.

      [html][/html]
    • Once the above steps are followed, proceed with labelling of tapes. Once labelling is successful, a given DLE can be bound to tapes on AWS, to be the end storage device.
    [B]************************************************** ************************************************** ******************
    Please follow the above steps to fix the issue. In case if you need any assistance, kindly contact support.
    support can be reached @ [email protected]
    Or call us @ 888-496-2632 (U.S.)/ 408-732-3208 (INTL)
    Last edited by [email protected]; February 10th, 2020 at 10:42 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •