FREQUENTLY ASKED QUESTIONS

FalconStor StorSafe® VTL is a virtual tape library market leader, offering fast, secure, and scalable data protection and migration solutions. Find out how it can help you.​

Why did you select FalconStor StorSafe® VTL?​

“It was the easiest to deploy, the most scalable and flexible, and [is] a very reliable product.”​

Mike Boreham, Technical Lead at Blue Chip, a Service Express Company.

StorSafe VTL enables significant time and cost savings for on-premises and cloud data protection, as well as enabling fast and secure migration to the cloud.

DATA PROTECTION

Due to the explosive growth of data from databases, email applications, and other business applications, backup administrators are finding it increasingly difficult, if not impossible, to complete backups within allotted backup windows. Furthermore, media and device failure and errors are commonplace, requiring valuable time and resources to keep the backup environment up-and-running. FalconStor’s virtual tape library (VTL) solution, StorSafe VTL, enables blazing fast, reliable restores and eliminates the need to re-run backup jobs due to tape errors, saving considerable time and resources.

Because this solution uses disk to back up data, it eliminates the media and mechanical errors that can occur with physical tapes and drives. In addition, because StorSafe VTL can emulate more tape drives than your physical tape library has, you can run more backup streams simultaneously. This enables you to more easily complete backups within shrinking backup windows.

FalconStor StorSafe VTL can be installed at remote sites, consolidating backup data at a central location utilizing an existing tape infrastructure. You can easily add new virtual tape drives and libraries, or increase backup jobs and backup streams, without the expense and hassle of adding new hardware.

CLOUD MIGRATION
The same image that is used for backup is used to migrate workloads to the cloud. IBM Power customers who have delayed moving to IBM Power Systems Virtual Server (PowerVS) are now adopting StorSafe VTL as their preferred migration tool. FalconStor has partnered with industry experts to create scripts and document all the steps necessary to migrate IBM i or AIX workloads to IBM PowerVS with a procedure that is reliable, repeatable, and consistent. The process overview is:

  •     Backups are directed to StorSafe VTL for Power at the customer site
  •     Backups are replicated to StorSafe VTL for PowerVS running in PowerVS
  •     Restore to PowerVS-resident IBM i/AIX to complete the migration
  •     StorSafe VTL for PowerVS then runs in PowerVS for ongoing backups

The StorSafe VTL deduplication engine eliminates redundant data without impacting established backup windows, while minimizing replication time and storage requirements. The deduplication engine scans backup data at the block level, analyzes the data, and determines whether data is unique or has already been stored in the deduplication repository. Only single instances of data are stored. The original virtual tape is replaced with a virtual index tape (VIT) pointing to FalconStor single instance repository (SIR) storage, freeing space for more data. StorSafe VTL offers a choice of deduplication options: Inline, post-process, turbo deduplication, or no deduplication.

 

Engineered with users in mind, StorSafe VTL provides the flexibility to select the desired deduplication method at the tape level, based on unique and changing requirements:

  • Inline deduplication minimizes storage requirements and is ideal for small storage configurations or environments where immediate replication is desired. For the highest performance levels, a recommended best practice is to use StorSafe VTL’s flexible deduplication policies to leverage post-process deduplication for the initial backup, and then switch to inline deduplication for subsequent backups.
  • Post-process and turbo deduplication is ideal when you deploy an external SIR cluster or your VTL server’s computing capacity is limited. As its name implies, it occurs after the backup process completes, thus it can be scheduled to run at any time.
  • No deduplication can be used on data that does not deduplicate effectively or data that is exported to physical tape. Examples include image files and data that is pre-compressed and encrypted. By selectively “turning off” deduplication, you can save cycles and focus on deduplicating the data that will yield the highest overall ratios and value.

Yes. Inline deduplication is compatible with existing deduplication processes. Inline deduplication can coexist with existing post-process and turbo processes, wherein three processes can run at the same time on different tapes. Tapes using turbo deduplication can be moved seamlessly to inline deduplication as needed, and vice-versa. This unique flexibility allows you to adjust to your changing needs without any impact on backup processes.

 

Without deduplication, all of a virtual tape’s new backup data is sent over the wire, resulting in multiple terabytes of duplicate data driving up bandwidth requirements and costs. Since much of the backup data is redundant, only new/unique information needs to be replicated. By identifying unique data, the deduplication engine minimizes the bandwidth needed to replicate backup data, minimizing costs and making replication practical for most organizations.

 

Since local data deduplication makes replication more affordable, you can easily and cost-effectively consolidate backup data from multiple remote offices to a central location, such as a datacenter. However, there may still be duplicate data between remote offices. Global deduplication ensures that redundant data from remote offices is not replicated to the central repository, thus minimizing space requirements.

 

No. FalconStor StorSafe VTL enhances the performance of your current backup application, so you can decrease your current backup window without having to modify job configurations. The solution works with the most common backup and restore applications available in the market.

 

To meet retention requirements, data on virtual tape or NAS share can be exported directly to physical tape for long-term archiving (D2D2T). Data can continue to be copied to physical tape using the backup application’s “copy” function. The unique open architecture of StorSafe VTL enables integration with local and remote physical tape resources for the best possible return on investment (ROI).

 

FalconStor StorSafe VTL can emulate more tape libraries and tape drives than any other vendor. For each node, you can emulate up to 128 virtual tape libraries, 1,024 virtual drives, and 1,000,000 (1 million) virtual tapes. A complete list of supported vendors can be found on the FalconStor Certification Matrix.

FalconStor StorSafe VTL offers SMB or NFS network share or Veritas OpenStorage Technology (OST) over IP for NetBackup and Backup Exec backup applications. This easy-to-use file interface is compatible with all source data, seamlessly integrating with major backup software, database utilities, archiving applications, virtual machine data, and manual file copy methods. There is little or no need to change D2D backup applications or file and data archiving processes. Backup performance and reliability are drastically improved, and secondary storage capacity requirements are minimized.

 

You can use FalconStor StorSafe VTL to copy data to physical tape, or you can use any backup software that offers copy-to-tape functionality. Using backup software enables you to leverage the same processes as you would with physical tape. However, this puts an additional load on your backup server and the traffic between it and the virtual tape library. StorSafe VTL enables you to keep barcodes in sync locally and remotely, letting you proactively manage the tape export process.

 

Yes. You can migrate virtual tapes to private and public cloud object storage. Today, connectors are available for Amazon Web Services (AWS) S3 and Glacier and for Hitachi Content Platform (HCP) object storage for archive purposes in the cloud, and you can set up policies on virtual tape libraries to automatically migrate tape data when a tape is ejected to the virtual vault after backup. Migrated tapes are replaced with stub tapes to optimize on premise storage usage. To support the isolation of data between different users and separate accounts, buckets can be defined for each virtual tape library.

 

Yes. You can export up to five virtual tapes to physical tapes at a time.

 

No. FalconStor StorSafe VTL with deduplication includes a “Capacity on Demand” feature that allows you to create and allocate space as needed. This can save considerable disk space without affecting system performance. Inline deduplication allows you to back up directly to the repository, minimizing the capacity requirement.

 

With Automated Tape Caching, tapes always appear to be inside the FalconStor solution and are visible to the backup software regardless of whether the data resides on disk or tape. This gives the backup application direct access to data at any time. FalconStor StorSafe VTL acts as a transparent cache to the physical tape library. Based on extremely flexible migration policies (e.g., age of data, time of day, disk space, end of backup), the data is staged to the virtual tape cache and copied to physical tape after the backup completes.

Yes. A key advantage of FalconStor StorSafe VTL is that you can protect data on your existing physical tapes by importing them into your virtual tape system. If you need to recover files, you can use the import function to directly access the physical tape for immediate recovery.

 

FalconStor StorSafe VTL supports a variety of protocols, such as FC, iSCSI, NDMP, NFS, and SMB for unparalleled performance. A single VTL node can back up over 30TB of data in an hour over four 16GB FC ports, while a clustered pair can back up over 40TB per hour.

 

Yes. For high availability (HA), FalconStor StorSafe VTL can scale up to four pairs (eight nodes). If a machine fails, another will automatically take over its workload. The FalconStor SIR engine supports N+1 clustering of up to 4 active nodes, with a total repository size of up to 2PB.

One, two, or four active nodes can support a single deduplication repository for enterprise-level performance and capacity scalability. When paired with a standby node, the standby system (+1) will automatically take its place in the event of failure to ensure continuity. This allows you to start with the smallest possible configuration that meets your exact needs, and expand incrementally as your data requirements grow.

Using the secure backup and archival process on-premises, we support offsite protection using the cloud provider of your choice. This tape-free and touch-free automation uses the VTL image to facilitate your migration to the cloud.

Go to our IBM partnership page to discover all the ways you can use FalconStor StorSafe VTL with your IBM workloads. Migration to PowerVS is explained on this page.​

Resources

Certification Matrix

The FalconStor Certification Matrix outlines all of the hardware and software certified to work with FalconStor products. This matrix is constantly being updated, so please check back frequently for updates.

StorSafe® VTL with StorSight™ Product Collateral

Customer Success Story

Service Express offers MSPs services to a broad range of companies across Europe and North America.

VTL Best Practices Guide

This document is intended for new VTL users who have a good understanding of backup applications and a basic understanding of virtual tape libraries. It is assumed that the system has already been architected and deployed in the environment.​

Learn More