Chat now with support
Chat with Support

QoreStor 6.0.0 - User Guide

Introducing the QoreStor documentation Introducing QoreStor Setting up your QoreStor system Configuring QoreStor settings Managing containers Managing storage groups Managing replications Managing Users Managing QoreStor Remotely Monitoring the QoreStor system Support, maintenance, and troubleshooting

Creating a VTL type container

NOTE: For more information on using VTL containers, see Configuring and using VTL.

To create a virtual tape library (VTL) type container, complete the following steps.

NOTE: The number of supported VTL containers varies depending on the QoreStor installation mode. Refer to the QoreStor Interoperability Guide for more information.

  1. In the navigation menu, click Containers. The Containers page is displayed.
  2. Click Add Container.
  3. For Name, type the name of the container.

    NOTE: QoreStor does not support spaces or the following special characters in container names: /, #, or @. VTL container names cannot exceed 32 characters in length, must start with a letter, and can be composed of any combination of the following characters:

    • A-Z (uppercase letters)
    • a-z (lowercase letters)
    • 0-9 (numbers). (Do not start a container name with a number.)
    • underscore (_) special characters
    • hyphen (-) special character

    NOTE: iSCSI VTL containers do not support the following characters:

    • ASCII CONTROL CHARACTERS and SPACE through ,
    • ASCII /
    • ASCII ; through @
    • ASCII [ through `
    • ASCII { through DEL
  4. For Protocol, select Virtual Tape Library (VTL).
  5. Click Next.
  6. For Robot Model, select the type of virtual tape library for the VTL container.
    • STK L700—This is the standard emulation of the StorageTek L700 library.
    • QUEST DR_L700 - This is a Quest OEM version of StorageTek L700 library.

    NOTE: The Quest version of the VTL issupported only with Symantec Backup Exec and Netbackup data management applications (DMAs).

  7. For Tape Size, select the size of the tapes for your tape library from one of the following options.
    • 800 GB
    • 400 GB
    • 200 GB
    • 100 GB
    • 50 GB
    • 10 GB

    NOTE: Creating a VTL container type creates a tape library of type Storage Tek L700 with 10 tape drives of type IBM Ultrium LTO-4 and 60 tape slots holding 60 tapes. Additional tapes can be added as required. For more information, see VTL and QoreStor specifications.

  8. For Access Protocol, select one of the following options. Each protocol has different configuration requirements, as listed below.
    • NDMP
      • Enter DMA’s FQDN or IP address that will access the VTL container.
      • For Marker Type, select the appropriate marker that supports your DMA from the options below:
        • None — Disables marker detection for the container.
        • Auto — Automatically detects CommVault, Tivoli Storage Manager (TSM), ARCserve, and HP Data Protector marker types. In addition, select this option if you need to support EMC Networker 2.0.
        • ARCserve—Supports the ARCserve marker.
        • BridgeHead — Supports the BridgeHead HDM marker.
        • CommVault—Supports the CommVault marker.
        • HP DataProtector—Supports the HP Data Protector marker.
        • Acronis —Supports the Acronis marker
        • Networker — Supports EMC Networker 3.0. If you need to support EMC Networker 2.0, select Auto.
        • TSM—Supports the TSM marker.
        • Unix Dump — Supports the Amanda marker, among others.
    • iSCSI
      • Enter the FQDN, IQN, or IP address of the iSCSI initiator that can access the VTL container.
      • For Marker Type, select the appropriate marker that supports your DMA from one of the following options:

        NOTE: Improper marker selection can result in non-optimal savings. As a best practice, if you have only one type of DMA with traffic directed to a container, it is best to select the marker type that supports your DMA. Conversely, as a best practice, if you have traffic from a DMA that is not one of the supported marker types, it is best to disable marker detection for the container by selecting the None marker type.

        • None — Disables marker detection for the container.
        • Auto — Automatically detects CommVault, Tivoli Storage Manager (TSM), ARCserve, and HP Data Protector marker types. In addition, select this option if you need to support EMC Networker 2.0.
        • ARCserve—Supports the ARCserve marker.
        • BridgeHead — Supports the BridgeHead HDM marker.
        • CommVault—Supports the CommVault marker.
        • HP DataProtector—Supports the HP Data Protector marker.
        • Acronis —Supports the Acronis marker
        • Networker — Supports EMC Networker 3.0. If you need to support EMC Networker 2.0, select Auto.
        • TSM—Supports the TSM marker.
        • Unix Dump — Supports the Amanda marker, among others.
    • FC
      • For Marker Type, select the appropriate marker that supports your DMA from the options below:
        • None — Disables marker detection for the container.
        • Auto — Automatically detects CommVault, Tivoli Storage Manager (TSM), ARCserve, and HP Data Protector marker types. In addition, select this option if you need to support EMC Networker 2.0.
        • ARCserve—Supports the ARCserve marker.
        • BridgeHead — Supports the BridgeHead HDM marker.
        • CommVault—Supports the CommVault marker.
        • HP DataProtector—Supports the HP Data Protector marker.
        • Acronis —Supports the Acronis marker
        • Networker — Supports EMC Networker 3.0. If you need to support EMC Networker 2.0, select Auto.
        • TSM—Supports the TSM marker.
        • Unix Dump — Supports the Amanda marker, among others.
      • Enter the targetWWN and initiatorWWN.
    • No Access.

    NOTE: QoreStor allows you to create a VTL container type without configuring it with a specific protocol (that is, by selecting No Access). You can configure the container at a later date.

  9. Click Next.

    A summary of the options you selected for creating the container appears.

  10. Click Finish.

Viewing VTL tape information

Once you have created a virtual tape library (VTL) type container, you can view the detailed tape information of the VTL. This includes information about the vendor and model information for medium changer and tape drives. To view VTL information, complete the following steps.

  1. In the navigation menu, click Containers. The Containers page is displayed.
  2. In the list of containers, find the container for which you want to view statistics, and then click the (ellipsis icon) in the upper-right corner of the container's information pane.
  3. Click Details.
  4. You can view the following information:
    • Container Details
      • Number of Tape Drives
      • Library ID
      • Tape Size
      • is OEM
      • Container Path
      • Marker
      • Created On
    • Connection
      • Enabled
      • Status
      • Cartridges Available

Adding a Cloud Tiering policy

Once a cloud tier is created, you must enable a cloud tiering policy for a container before that container can be replicated to the cloud. Refer to Adding a Cloud Tier for more information.

  1. In the navigation menu, click Containers. The Containers page is displayed.
  2. In the list of containers, find the correct container and then click Enable Cloud Tiering Policy.
  3. In the Enable Cloud Tiering Policy page, enter the following information:
    • Cloud Policy-- allows you to configure the amount of time that files must be idle before being sent to the cloud as well as how long to keep a local copy of the files.
      • Idle time before cloud migration--Specify the number of hours files must be idle before being sent to the cloud.
      • On-Prem Retention Age--Specify the number of hours files will be kept locally after they are sent to the cloud.
    • Folder Paths--files can be included or excluded based on their location.
      • Include--only files in the listed directories will be included for replication.
      • Exclude-- all files except those in the listed directories will be replicated.
    • File Extensions--files can be included or excluded based on their extension.
      • Include--only files with the specified extensions will be included for replication.
      • Exclude--all files except those with the specified extensions will be replicated.
  4. Click Enable.

NOTE: To add a cloud tiering policy through the command line, use the command:

container --cloud_policy [--age_of_file <1 hours to 70 years (in hours)>] [--incl_file_ext <file extension list>] [--excl_file_ext <file extension list>] [--incl_dir <include directory list>] [--excl_dir <exclude directory list>] [--on_prem_reten_age <1 hours to 70 years (in hours)>] [--reset <incl_file_ext|excl_file_ext|incl_dir|excl_dir>] --name <name>

Example:

container --cloud_policy --age_of_file 1 --on_prem_reten_age 1 --incl_file_ext  .txt  --incl_dir  /include  --name <cont_name>

Refer to the QoreStor Command Line Reference Guide for more information.

Deleting a container

Deleting a container through the GUI

To delete an existing container that contains data, complete the following steps.

Caution: Before deleting a container, you should first carefully consider whether you need to preserve the data in the container. Before deleting any QoreStor container that contains deduplicated data, you should take steps to preserve this data using another means of long-term retention. Once a container is deleted, the deduplicated data cannot be retrieved.

  1. On the navigation menu, click Storage Groups. Select the storage group that contains the container you want to delete. (If you are only using the DefaultGroup storage group you do not need to select a group.)
  2. In the list of containers, select the container you want to delete, and then click the Delete icon.
  3. In the Warning dialog box, click Yes to confirm the deletion.

Deleting a container through the command line

To delete an existing container that contains data, complete the following steps.

  1. (missing or bad snippet)
  2. Delete a container with the command
    container --delete --name <name> [--delete_files]

    Refer to the QoreStor Command Line Reference Guide for more information.

Related Documents