Back to homepage
Search in acronis websites
Try Now

Acronis Blog

TRU Security →
Updates from Acronis Threat Research Unit
Acronis Blog
Cyber protection

All stories in Cyber protection

October 15, 2026 — 2 min read
Introducing New Acronis CEO: Prakash Panjwani
October 15, 2026 — 2 min read
Introducing New Acronis CEO: Prakash Panjwani
We are pleased to announce the appointment of our new Chief Executive Officer, Prakash Panjwani. A veteran cybersecurity CEO, Panjwani previously served as CEO of WatchGuard Technologies and SafeNet.
August 10, 2012 — 2 min read
Never Underestimate Your Resource & Skillset Requirements
August 10, 2012 — 2 min read
Never Underestimate Your Resource & Skillset Requirements
The final post in this series of five hidden DR hazards involves underestimating your resource and skillset requirements. When creating a do-it-yourself disaster recovery solution, you must consider your team’s personal priorities and also their ability to access your remote site.
July 31, 2012 — 1 min read
Failed Testing: Another Hidden Hazard of DIY DR
July 31, 2012 — 1 min read
Failed Testing: Another Hidden Hazard of DIY DR
Building a disaster recovery site can be an exciting project for ambitious IT teams. It involves a great deal of planning and results in a high degree of satisfaction once the environment is complete, the budget is justified and the equipment is procured and configured. Overall it is a gratifying experience– until it’s time to test the solution.
July 11, 2012 — 2 min read
How to Avoid Hardware/ Software Drift
July 11, 2012 — 2 min read
How to Avoid Hardware/ Software Drift
I’ve been writing about the hidden hazards of do-it-yourself disaster recovery. One of these hazards is hardware/software drift. Since your disaster recovery site represents a working replica of the production environment, it will need to be maintained on an ongoing basis. There are several strategies for how hardware and software are provisioned for your DR site. The strategies you choose will determine the how much maintenance will be needed to keep your DR site running at an optimal level.
July 03, 2012 — 1 min read
How to Choose a Remote Colocation Site
July 03, 2012 — 1 min read
How to Choose a Remote Colocation Site
Choosing a disaster recovery location is critical to the success of any DR project. One of the biggest mistakes that you can make is to choose a colocation site that is too close to your production site. It’s way too easy for a power grid failure to knock out both your primary and your colocation site if both sites are located in the same metropolitan area. (It happens!) But the challenge of in-house DR is that the technical team responsible for bringing your DR site online will need access to that site. This means that the approach and technology used to deliver a disaster recovery solution must be capable of remote activation. Learn more about remote activation in the nScaled white paper The 5 Things That Can Go Wrong With DIY Disaster Recovery: 5 Things That Can Go Wrong With DIY DR
June 28, 2012 — 2 min read
The Hidden Hazards of SAN-to-SAN Replication
June 28, 2012 — 2 min read
The Hidden Hazards of SAN-to-SAN Replication
It might be tempting to create a “do-it-yourself” disaster recovery solution by purchasing additional hardware and installing it in a branch office or colocation facility. But creating an effective disaster recovery solution is a complex project and there are several unplanned costs and other hidden hazards associated with it. I’ll identify some of these hidden hazards over the next few weeks.
May 04, 2012 — 1 min read
Recovery-in-a-Cave
May 04, 2012 — 1 min read
Recovery-in-a-Cave
Just got done reading the funniest white paper ever, from our friends at Iron Mountain. It asks the question, “…what happens when the devastation is so fierce that it hits the backups too? Don’t panic.”
April 04, 2012 — 1 min read
Really?
April 04, 2012 — 1 min read
Really?
Disco Stu has moved from Springfield to the world of backup and DR.
March 14, 2012 — 1 min read
Boston Fire leads to customer failover
March 14, 2012 — 1 min read
Boston Fire leads to customer failover
The power outage affected the Boston office one of our large disaster recovery customers. We protect 70 servers in 11 offices around the US for this customer.
March 02, 2012 — 1 min read
Hazard Insurance
March 02, 2012 — 1 min read
Hazard Insurance
Clusters of tornados last week and this week in the US Midwest once again bring one’s thoughts to the issue of insurance.
February 22, 2012 — 3 min read
nScaled Closes Series A Investment
February 22, 2012 — 3 min read
nScaled Closes Series A Investment
As you can imagine, we are very excited to announce that we just closed a $7M Series A round of financing!
February 15, 2012 — 4 min read
Protecting Multi-tier Applications, Part II
February 15, 2012 — 4 min read
Protecting Multi-tier Applications, Part II
In a multi-tier server environment, the quiescent state of a single server isn’t enough. In order to achieve a working and consistent application, the various servers that make up the entire application stack may need to be in a quiescent state across multiple servers, a term referred to as “cross-server application quiescence”. As an example, in a document management system where the database server and a file server are both present, it is often necessary for the database and file server to be recovered from virtually the same moment in time. In other cases, it may be better for the file server to have a more recent copy of the data than the database server but never the other way around. In the process of working with our customers, nScaled has experience working with many different types of multi-tier applications.
February 03, 2012 — 2 min read
Protecting Multi-tier Applications
February 03, 2012 — 2 min read
Protecting Multi-tier Applications
Our crack Services team has written a new technical solution brief about the pitfalls of doing DR for multi-tier applications. Seeing as how most apps these days are multi-tier, and those apps are usually the most critical to a business, figuring out how to backup or failover is paramount. We’ll serialize the tech brief for a few days here.