November 30, 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. All data originated on one type of storage and stayed there until it was deleted. We now understand that not all data is created equal. Some types of data are more important than others, or accessed more frequently than others. Backup Lifecycle Management (BLM), defines the BLM concept where data is created on one storage system, then migrated to less expensive storage systems as it ages. Asigra Backup Tiers For example: Data that is 2 minutes old is highly valued.Data that is 2 months old may be of interest but is not as highly valued.Data that is 2 years old may be needed for records but it is not critical to the daily functioning of the company.DS-System – Primary Storage-Business-Critical Operational Data Business Critical Operation Data contains the files, databases, email systems, etc., that are needed for operations on a day-to-day basis. All data that is critical to business operations data should be stored in the DS-System Tier. BLM Archiver – Policy based retention of older data Large file servers or other large repositories of potentially older data can be moved to BLM, Cost savings are the primary benefit by allowing storage of older data and automatic retention policies that move aged data into the lower cost tier. BLM Archiver can also be leveraged to provide storage of past generations of data while keeping the most recent version in business-critical DS-System. Managecast will help with analyzing your data to determine a protection method to best suit your recovery requirements and budget. There are many options to protect business data by strategically identifying the value and aligning the cost to protect it. BLM Cloud Storage – For Low-Cost, Rarely Retrieved Files Typically for files older than 1 year, BLM Cloud Storage is a method to cost-effectively protect large data sets that are still needed for reference, compliance, and infrequent restores. Files older than a specified age can be selected to move to long-term cloud storage and are generally grouped in large chucks from 250GB on up to multiple terabytes and then copied to long-term archive on disk. Customers can utilize Amazon S3 cloud storage or use Managecast Enterprise Cloud Storage Interested in learning how Managecast can help your business with its cloud backup and disaster recovery solutions? Fill out this form for more information!

Veeam

Veeam v 8 Certificate Error When Upgrading (Authentication Failed Because the Remote Party has Closed the Stream)

We were setting up Veeam Cloud Connect infrastructure to offer Veeam Cloud Backup, a feature many of our customers had requested. The installation was going smoothly, and we initially used a self-signed certificate for testing. Later, we applied a certificate from a well-known Certificate Authority, which also worked without any issues. However, we soon received a notification from Veeam about an available update (v8 Update 3). Since it’s important to stay on the same version or higher as our clients, we proceeded with the update. After updating to Update 3, clients were suddenly unable to connect, receiving the following error: “Error: Authentication failed because the remote party has closed the stream.” This error occurred immediately upon connection, and Veeam wouldn’t allow us to edit the Cloud repository because it no longer recognized the certificate. Steps We Took: Fortunately, we had taken snapshots of all Veeam components before updating (Backup and Replication server, Cloud Gateway, WAN Accelerator, and Repository). After reverting to the pre-update state, clients were able to connect again using either the self-signed certificate or the one from the Certificate Authority. Troubleshooting with Veeam Support: We then opened a support ticket with Veeam and provided logs from every component and the client side. After reviewing the logs, Veeam support had us install Update 2b and submit logs before and after the upgrade. Unfortunately, the issue remained. Finally, Veeam support provided a process that worked: This solution worked! After that, we took another set of snapshots and upgraded to Update 3, and everything continued to function properly. Key Takeaway: If you encounter this issue after a Veeam update, try applying a self-signed certificate first, then upgrading, and finally applying the Certificate Authority certificate. This step saved us considerable time, especially since the error wasn’t documented in Veeam’s KB articles or certificate installation documentation.

Scroll to Top