December 1, 2015

Asigra

Asigra BLM Archiving – Align the Value of Your Data With the Cost to Protect it

Years ago, we treated all data as being equal. Every piece of data originated on one type of storage and remained there until it was deleted. However, we now understand that not all data is created equal. Some data types are more important or accessed more frequently than others. Backup Lifecycle Management (BLM) is a concept that helps organizations manage data more efficiently by storing it on one system initially, then migrating it to lower-cost storage systems as it ages. This strategic data management approach can reduce storage costs while ensuring critical data remains accessible. Understanding Asigra Backup Tiers Data Classification and Storage Tiers DS-System – Business-Critical Operational Data Business Critical Data such as files, databases, and email systems necessary for daily operations should reside in the DS-System Tier. This tier is optimized for speed and accessibility, ensuring that your mission-critical information is always available. BLM Archiver – Policy-Based Retention for Aging Data Large file servers or repositories containing older data can be migrated to BLM Archiver. The primary advantage is cost savings, as this system automatically moves older data into lower-cost storage tiers based on pre-configured retention policies. At Managecast, we help analyze your data to identify the optimal protection methods suited to your recovery needs and budget. There are many strategies to protect your business’s data by aligning its value with the costs to protect it. BLM Cloud Storage – Low-Cost, Long-Term Data Storage BLM Cloud Storage is a cost-effective solution for rarely retrieved files, typically those older than one year. Large data sets, ranging from 250GB to multiple terabytes, can be moved to long-term storage to ensure compliance and maintain records while reducing storage expenses. Storage Solutions for Rarely Accessed Data Older data can be grouped into long-term cloud storage, making retrieval simple when necessary. Customers can choose between Amazon S3 Cloud Storage or Managecast Enterprise Cloud Storage for scalable, secure storage.

Zerto

Zerto Backup Fails Unexpectedly

We had a recent issue with Zerto backups that took some time to remedy. There was a combination of issues that exposed the problem, and here is a run down of what happened. We had a customer with about 2TB of VM’s replicating via Zerto. We wanted to provide backup copies using the Zerto backup capability. Keep in mind Zerto is primarily a disaster recovery product and not a backup product (read more about that here: Zerto Backup Overview). The replication piece worked flawlessly, but we were trying to create longer-term backups of virtual machines using Zerto’s backup mechanism which is different from Zerto replication. Zerto performs a backup by writing all of the VM’s within a VPG to a disk target. It’s a full copy, not incremental, so it’s a large backup every time it runs, especially if it’s a VPG holding a lot of VMs. We originally used a 1Gigabit network to transfer this data, but quickly learned we need to upgrade to 10Gigabit to accommodate these frequent large transfers. However, we found that most of the time the backup would randomly fail. The failure message was: “Backup Protection Group ‘VPG Name’. Failure. Failed: Either a user or the system aborted the job.” To resolve the issue we had opened up several support cases with Zerto, upgraded from version 3.5 to v4, implemented 10Gigabit, put the backup repository directly on the Zerto Manager server. After opening several cases with Zerto we finally had a Zerto support engineer thoroughly review the Zerto logs. They found there were frequent disconnection events. With this information we explored the site-to-site VPN configuration and found there were minor mismatches in the IPSEC configurations on each side of the VPN which were causing very brief disconnections. These disconnections were causing the backup to fail. Lesson learned: It’s important to ensure the VPN end-points are 100% the same. We use VMware vShield to establish the VPN connections and vShield doesn’t provide a lot of flexibility to change VPN settings, so we had to change the customer’s VPN configuration to match the vShield configuration. Even though we seemed to have solved the issue by fixing the VPN settings, we asked Zerto if there was any way to make sure the backup process ran even if there was a connection problem. They shared with us a tidbit of information that has enabled us to achieve 100% backup success: There is a tweak that can be implemented in the ZVM which will allow the backup to continue in the event of a disconnection, but there’s a drawback to this in that the ZVM’s will remain disconnected until the backup completes. As of now, there’s no way to both let the backup continue and the ZVM’s reconnect. So there is a drawback, but for this customer it was acceptable to risk a window of time that replication would stop to make a good backup. In our case we made the backup on Sunday when RPO wasn’t as critical, and even then the replication only halts if there is a disconnection between the sites which became even more rare since we fixed the VPN configuration. The tweak: On the Recovery (target) ZVM, open the file C:\Program Files (x86)\Zerto\Zerto Virtual Replication\tweaks.txt (may be in another drive, depending on install) In that file, insert the following string (on a new line if the file is not empty) t_skipClearBlockingLine = 1 Save and close the file, then restart the Zerto Virtual Manager and Zerto Virtual Backup Appliance services Now, when you run a backup, either scheduled or manual, any ZVM <-> ZVM disconnection events should not cause the backup to stop. I hope this helps someone else!

Zerto

Zerto Backup Overview

Zerto is primarily a disaster recovery solution that relies on a relatively short-term journal that retains data for a maximum of 5 days (at great expense in disk storage). Many Zerto installations only have a 4-hour journal to minimize the storage needed for the journal. Zerto is a great disaster recovery solution, but not as great as a backup solution.  Many customers will augment Zerto with a backup solution for long-term retention of past data. Long-term retention is the ability to go back to previous versions of data, which is often needed for compliance reasons. Think about the ability to go back weeks, months, and even years to past versions of data. Even if not driven by compliance, the need to go back in time to view past versions of data is very useful in situations such as: Cryptolocker type ransom-ware corrupts your data and is replicated to the DR site Legal discovery – for example, reviewing email systems as they were months or even years ago. Inadvertent overwriting of critical data such as a report that is updated quarterly. Clicking “Save” instead as “Save As” is a good example of how this can happen. Unexpected deletion of data that takes time to recognize. For reference and further clarification, check out the differences between disaster recovery, backup and business continuity. Even though Zerto is primarily a disaster recovery product, it does have some backup functions. Zerto backup functionality involves making an entire copy of all of the VM’s within a VPG. We sometimes break up VPG’s with the goal to facilitate efficient backups. One big VPG can result in making one big backup which can take many hours (or days) to complete. Since it’s an entire copy of the VPG it can take a significant amount of time and storage space to store the copy. Each backup is a full backup and currently, no incremental/differential backup capability exists within Zerto. It is also advisable to write the backups to a location that support de-duplication, such as Windows 2012 Server. It still takes time to write the backup, but the de-duplication will dramatically lower the required storage footprint for backing up Zerto VPG’s. Without de-duplication on the backup storage, you will see a large amount of storage consumed by each full backup of the VPGs. Zerto supports the typical grandfather-father-son backup with daily, weekly and monthly backups for 1 year. Zerto currently does not support backups past 1 year, so even with Zerto backups, the long-term retention of data is not as good as with other products designed to be backup products. However, Zerto really shines as a disaster recovery tool when you need quick access to the latest version of your servers. Its backup capabilities will get better with time. Interested in learning how Managecast can help your business with its cloud backup and disaster recovery solutions? Fill out this form for more information!

General Cloud Backup

The Difference Between Disaster Recovery, Backup and Business Continuity

It’s common to see terms like backup and disaster recovery (DR) used interchangeably, and sometimes even incorrectly. We often encounter customers asking for a DR solution when what they really need is both backup and disaster recovery. Some in the industry refer to this combination as BDR (Backup & Disaster Recovery). So, what’s the difference between backup and disaster recovery? And why does it matter? Disaster Recovery (DR) Disaster recovery focuses on restoring critical IT functions quickly after a disaster. Disasters can range from something as small as a critical server failure to large-scale events like fires, floods, tornadoes, hurricanes, or even man-made incidents such as construction accidents, theft, sabotage, or chemical spills. These events can render your entire site unusable. The goal of DR is to bring critical IT services back online as quickly as possible. A comprehensive DR plan may involve much more than just data recovery — it might include alternate sites, spare hardware, and other contingency measures. Backup Backup, while it can play a role in disaster recovery, serves a broader purpose. Backup not only supports rapid recovery in the event of a disaster, but it also gives you access to the historical versions of your data. That’s a key difference between backup and disaster recovery. There are DR products designed to provide a fast recovery to the most recent copy of a server, but they aren’t built to retrieve data from two weeks, six months, or years ago. With backup, you can access older versions of files, which is crucial for recovering from issues like data loss or corruption that happened in the past but are only noticed in the present. For example, in the case of a ransomware attack, your most recent backups might include infected files. In this situation, you’d need to restore data from before the infection occurred. Backup also helps in more common scenarios, like accidentally overwriting an important file. If you saved over a monthly report in Word, a backup allows you to recover the original file. Additionally, some industries are required by law to keep copies of their older data. For instance, medical providers must retain patient records for several years. In summary, backup data can be used for DR, but it also includes past versions of data, allowing you to reproduce information as it existed at any given point in time. Business Continuity Business continuity refers to how an organization continues to perform essential functions despite a disaster. It goes beyond just restoring servers and data and often involves non-IT-related concerns as well. Every organization’s business needs are unique. For example, some companies rely heavily on phone services to take customer calls, while others depend on specialized equipment that isn’t easily or quickly replaceable. When creating a business continuity plan, critical questions need to be asked: Who are the essential employees? What functions do they perform? Where will they work if the office becomes unusable? Data recovery is just one piece of a much larger puzzle in business continuity.

Scroll to Top