Frequently Asked Questions
We've got all of your answers right here!
How does Metiix De-Duplication work?
Metiix de-duplicates occurs at the variable block level within each server before transmission to any selected disk destinations. De-duplication occurs prior to any data leaving the server for the smallest transfers possible to local and remote locations. No appliances are necessary to accomplish the de-duplication process. This de-duplication process uses the least amount of disk space possible for storing long term online history.
How much de-duplication & compression should I expect?
De-duplication depends on the makeup and file types of a particular server. Metiix is constantly comparing the blocks across all the files on the entire server. A substantial de-duplication can be expected both on the initial backup and on all subsequent generations and changes. Anytime a block algorithm within any file or application is matched, the duplicate need not be sent to any of the destinations.
What kind of load does Metiix put on the server?
Metiix only needs to deal with the new data that is created in any given interval at a given point in time, server load is minimal. Metiix is set to observe the file system for change on a server and then move the new blocks from those files at a predetermined interval. Load is only placed on the server during the time that those files are moved through the Metiix client for the de-duplication and encryption process at that particular interval.
Can I control CPU limits?
Metiix can limit the percentage (%) of load placed on a server for the de-duplication and encryption process at the time of backup
Can I throttle bandwidth?
Metiix can set any limits on bandwidth utilized to local and remote destinations where data is sent.
What if I lose the host server, can I still do restores?
Metiix allows restores to be performed on any host to and from any destination, or at any destination for any participating host. Restores can be done as the administrator or guest restore privileges may be allowed.
Can I manage Metiix from a central location or interface?
Yes, servers can be centrally managed though a central web interface. Servers can also be accessed individually for configuration and management or via the web portal. Any host servers that share a common destination may also be managed at that joint destination.
Do servers have to be configured the same?
Each server performs independently within a grid style configuration for optimization of that server’s performance, amount of change in a particular interval or schedule, and its connectivity or bandwidth available in relation to its chosen backup destinations locally and abroad. A server’s unique data retention requirements and destination targets may also vary greatly from one to the next.
Do all servers have to write to the same destination?
Servers can choose to write to many different locations, or share common destinations.
Do I have to use the Metiix vault?
Metiix allows for you to choose what data is sent to the vault. Metiix allows customers to write data to our vault when and if necessary, or avoid sending data to Metiix altogether.
One of the major advantages to using Metiix is the ability to choose to backup a server to as many of your own sites as you wish and exclude the Metiix vault.
Can the Metiix engineers see my data?
Metiix engineers have the ability to monitor your backups for successes and failures to assess the potential causes for anything out of the norm, inform you what actions will be required, and what corrections to make. Metiix engineers can also help you manage the configuration of each of your clients. Metiix engineers do not have access or visibility into you data.
What are you monitoring for?
Metiix engineers are monitoring for degrees of successes and failures of the backups to all data destinations selected by the customer, our vault or otherwise. Metiix helps you become aware of any problems that may exist within your backup environment.
Do you need permissions for my LAN?
Metiix Engineers are only monitoring outbound transmissions from the deployed clients to the NOC to determine the success and failure of backups.
Can I go back in history?
Metiix builds a journal or incremental database at the block level so you can go back in time through unlimited history to recovery versions of files and all data.
How many generations can I keep?
You have the ability to set how many versions or generations of a file you would like to hold at each destination. With Metiix, you can hold an unlimited amount of generations at each destination.
Can I restore a single file, at a point in time, and from where?
Yes, with Metiix you can restore any file from any backup point in time, limited only by your retention rules. Restores can be performed from any Metiix client that is part of the same account. Restores can also be performed directly from the destination server.
What type of encryption is used?
448bit Blowfish encryption
Do you support retention policies?
Yes, like file generations, retention policies can also be set to unlimited (hold everything forever), or choose a granular time based retention or delete policy.
How long do backups take?
The completion of a backup depends on how much data changes on a particular server after de-duplication and compression during a particular interval of time, and what is the slowest bandwidth, to the farthest destination.
Example: A host server changes 256 Mbytes of data after de-duplication and compression during a given hour interval and is writing to 3 destinations; (1) to local disk, (2) to a offsite facility with a 9mb pipe, and (3) to a destination with a T1, the times will vary as follows. The local destination will immediately complete at local LAN disk speed, the 9mb connection will take a few minutes, and the T1 will take up to 20min.
How long backups will take depends on the speed of the farthest/slowest destination selected for that data to go to and the amount or rate of data change on a particular server at a particular interval of backup selected.
What if a destination fails?
If a Host server is writing to two or more destinations and one fails, the prevailing destinations will continue scheduled operations as if nothing has occurred. The backup that was headed to the failed destinations will continue to log and track changes and then catch up when the failed destination is brought back online.
How do you handle deletes?
If a file is deleted from the host we are protecting, it will in turn be deleted off the targets corresponding with whatever retention policy has been set for the files on that host server.
Example: if a file is deleted from the host server at 3:05 pm on the 18th a of a given month, and a 162 day hold policy has been set, then the data pertaining to that file will be deleted off of the destinations 162 days from that time stamp.
How are encryption keys managed?
You can manage your own encryption keys on a per server basis. You can also elect to allow Metiix to escrow your encryption keys. At no point will Metiix employees or anyone outside of your immediate administration have access to your keys or the contents of your data.
Does data remain encrypted?
Data is encrypted prior to leaving the server and remains encrypted to all destinations. Data is only decrypted upon restore.
How does Metiix handle open files?
Two ways: Metiix deploys agents to protect databases or by setting tighter intervals of backup to more frequently catch files as they may be closing.
How are database like SQL and Exchange handled?
We build and provide agents for SQL, Exchange, System State, and Active Directory to facilitate the hot backup of those always open files. Metiix-Aware allows us to take scheduled backups of your storage groups, live databases, system state, and active directory.
The Metiix agents control the transfer of the live database or the storage groups to the local Metiix client engine for de-duplication, compression, encryption and transportation to the different destinations. The Metiix database agents access each database or storage group hot for the moves, handle scheduling of those moves, monitoring of those moves, validation of those moves, and notifications of successful completion of each move.
Is pricing based on capacity?
Pricing is only based on capacity when a customer chooses to write data to the Metiix vault. Pricing is not based on capacity when a customer uses their own destinations.
What is the most common way to restore a downed server?
Metiix is sending the System State, Active Directory and all of the file and database history directly to several destinations, all capable of restore from any particular point in time. At the destination where the restore is to take place an operator needs to present the Metiix destination with a pre-configured base OS on new hardware before restoration can begin.
Can I run in continuous mode?
Yes, Metiix can observe file system changes in real-time on a server 24 hours a day and then move those changes to the selected destinations based upon interval scheduling.
Example: Metiix is continually observing and then moving changes to 3 destinations every 5min, 15min, 60 min, 180min, etc…
What if I don’t want to run during the day?
Metiix can be set to only run during pre-determined times or set schedules.
What hardware and storage do I need at my destinations?
The power of Metiix block level dynamics allows you to use any hardware and disk configuration that suites you at your destinations. All that is required at any destination is one Metiix client license loaded onto a Windows or Linux platform and some disk to write to. Choose from: USB, FW, ATA, e-SATA, SATA, SCSI, iSCSI, internal disk, DAS, NAS, or SAN. Mix and match disk manufacturers, hardware types, and the amount of destinations deployed.