Skip to main content

How Next-Gen Data Management Can Help You Navigate the Hybrid Multicloud World

Chris Wiborg
Cohesity

Once upon a time data lived in the data center. Now data lives everywhere.

You have data in the data center, data at edge locations used by remote offices, data on mobile devices, and data in the cloud. And when a business has data in the cloud, it usually doesn't mean just one cloud.

Chances are good that you have data in SaaS applications like Microsoft 365, Salesforce, and other applications, clouds, and systems. Organizations are increasingly adopting hybrid multicloud strategies. So, some of your data might live on AWS, Google Cloud Platform, and/or Microsoft Azure.

All this signals the need for a new approach to data management, a next-gen solution — one that gives the power of choice to an organization to design a data management strategy that best meets its unique business needs. At the same time, the entire process of data management must be simplified. The era of multiple legacy point solutions to handle a company's data needs cannot meet the needs of a modern enterprise that must manage, protect, and derive business value from its data to compete and succeed.

Understand That Distributed Data Creates New Mobility and Security Implications

When your data lives in many different places, there are several implications.

You need to address data logistics — or how to get data from one place to another. In some cases you are moving data to the cloud. But sometimes you may want to repatriate data, which involves moving data back from the cloud.

Additionally, you have to rethink your approach to security. When all of your data lived in your data center, you could protect it with a hard perimeter around that data center. But because data is now everywhere, your security model must change and adopt zero trust principles.

Now you need to manage data everywhere in a way that is efficient and effective. Your data management approach should start with protecting and backing up your data. This will help you to recover if you have an outage or you are attacked by ransomware, which is growing at an alarming rate.

Take Responsibility Rather Than Assuming That Data in the Cloud Is Safe

You may think that when you put data in the cloud it is automatically protected. But just because your Microsoft 365 implementation is in the cloud, it doesn't mean Microsoft can bring back your data if things go wrong. Microsoft 365 retains customer content for 30 days at most.

Microsoft, Google, and AWS may offer guarantees related to their cloud services' uptime and availability. But you are responsible for making sure your data is secure and accessible for compliance, legal, and other purposes. This is known as the cloud's shared responsibility model. Under this model, you are responsible for your data — even if an employee mistakenly or intentionally deletes that data or you fall victim to ransomware or another type of cyberattack.

But not everybody operating in today's hybrid multicloud world understands that because SaaS and IaaS are relatively new models, and many IT operations teams and other talent responsible for resiliency aren't fully aware of the limitations and risks cloud poses when it comes to your data.

Avoid Creating More Silos By Taking a Centralized Approach

Your database provider may tell you that its database provides native online backup. But that is a siloed approach that adds complexity from a broader operations perspective rather than enabling modernization and simplification.

The best way to avoid silos is to implement a centralized data management solution that protects and lets you manage your data — in the cloud and on premises — using a single administrative interface.

Be Aware That As-A-Service Disaster Recovery Is An Effective Option

You may choose to back up all of your cloud, software-as-a-service, and on-premises data using a self-managed backup solution. But now data management companies also offer additional resiliency via disaster recovery-as-a-service (DRaaS) solutions. This means you now have the flexibility to choose between managing everything on your own or letting your DRaaS provider focus on managing the infrastructure, while you focus on the policies that will govern your data — where the value resides.

Whether you choose to manage your own infrastructure, consume as-a-service options, or adopt a flexible hybrid approach — as more and more organizations are choosing — make sure that your data management solution addresses all of your needs, wherever your data resides.

By consolidating "one off" solutions and adopting a next-gen data management platform approach you can simplify complexity and lower the costs involved with managing your data. At the same time, this approach will allow you to follow an operational strategy that is best for your business while helping you to avoid data mobility problems, and letting you recover faster when disaster strikes.

Now you can more easily protect your data. More importantly, you can protect your business.

Chris Wiborg is VP of Product Marketing at Cohesity

The Latest

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...

Who is watching the watcher? This may not be the first question that comes up when discussing AI observability but sooner or later you start to wonder. Part 12 covers the dilemma of AI monitoring AI ...

Two AI agents got caught in a loop with each other over a weekend and racked up $47,000 in charges, according to John D'Emic, CTO of Revenium. No alert fired because nothing "broke." Stories like this are why cost has become one of the most pressing questions in AI observability. Traditional monitoring was built to catch failures, not wasted spend, and AI systems can burn through budget while every dashboard stays green. Part 11 explores how AI observability relates to AI cost management, and whether they are one discipline or two ...

How Next-Gen Data Management Can Help You Navigate the Hybrid Multicloud World

Chris Wiborg
Cohesity

Once upon a time data lived in the data center. Now data lives everywhere.

You have data in the data center, data at edge locations used by remote offices, data on mobile devices, and data in the cloud. And when a business has data in the cloud, it usually doesn't mean just one cloud.

Chances are good that you have data in SaaS applications like Microsoft 365, Salesforce, and other applications, clouds, and systems. Organizations are increasingly adopting hybrid multicloud strategies. So, some of your data might live on AWS, Google Cloud Platform, and/or Microsoft Azure.

All this signals the need for a new approach to data management, a next-gen solution — one that gives the power of choice to an organization to design a data management strategy that best meets its unique business needs. At the same time, the entire process of data management must be simplified. The era of multiple legacy point solutions to handle a company's data needs cannot meet the needs of a modern enterprise that must manage, protect, and derive business value from its data to compete and succeed.

Understand That Distributed Data Creates New Mobility and Security Implications

When your data lives in many different places, there are several implications.

You need to address data logistics — or how to get data from one place to another. In some cases you are moving data to the cloud. But sometimes you may want to repatriate data, which involves moving data back from the cloud.

Additionally, you have to rethink your approach to security. When all of your data lived in your data center, you could protect it with a hard perimeter around that data center. But because data is now everywhere, your security model must change and adopt zero trust principles.

Now you need to manage data everywhere in a way that is efficient and effective. Your data management approach should start with protecting and backing up your data. This will help you to recover if you have an outage or you are attacked by ransomware, which is growing at an alarming rate.

Take Responsibility Rather Than Assuming That Data in the Cloud Is Safe

You may think that when you put data in the cloud it is automatically protected. But just because your Microsoft 365 implementation is in the cloud, it doesn't mean Microsoft can bring back your data if things go wrong. Microsoft 365 retains customer content for 30 days at most.

Microsoft, Google, and AWS may offer guarantees related to their cloud services' uptime and availability. But you are responsible for making sure your data is secure and accessible for compliance, legal, and other purposes. This is known as the cloud's shared responsibility model. Under this model, you are responsible for your data — even if an employee mistakenly or intentionally deletes that data or you fall victim to ransomware or another type of cyberattack.

But not everybody operating in today's hybrid multicloud world understands that because SaaS and IaaS are relatively new models, and many IT operations teams and other talent responsible for resiliency aren't fully aware of the limitations and risks cloud poses when it comes to your data.

Avoid Creating More Silos By Taking a Centralized Approach

Your database provider may tell you that its database provides native online backup. But that is a siloed approach that adds complexity from a broader operations perspective rather than enabling modernization and simplification.

The best way to avoid silos is to implement a centralized data management solution that protects and lets you manage your data — in the cloud and on premises — using a single administrative interface.

Be Aware That As-A-Service Disaster Recovery Is An Effective Option

You may choose to back up all of your cloud, software-as-a-service, and on-premises data using a self-managed backup solution. But now data management companies also offer additional resiliency via disaster recovery-as-a-service (DRaaS) solutions. This means you now have the flexibility to choose between managing everything on your own or letting your DRaaS provider focus on managing the infrastructure, while you focus on the policies that will govern your data — where the value resides.

Whether you choose to manage your own infrastructure, consume as-a-service options, or adopt a flexible hybrid approach — as more and more organizations are choosing — make sure that your data management solution addresses all of your needs, wherever your data resides.

By consolidating "one off" solutions and adopting a next-gen data management platform approach you can simplify complexity and lower the costs involved with managing your data. At the same time, this approach will allow you to follow an operational strategy that is best for your business while helping you to avoid data mobility problems, and letting you recover faster when disaster strikes.

Now you can more easily protect your data. More importantly, you can protect your business.

Chris Wiborg is VP of Product Marketing at Cohesity

The Latest

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...

Who is watching the watcher? This may not be the first question that comes up when discussing AI observability but sooner or later you start to wonder. Part 12 covers the dilemma of AI monitoring AI ...

Two AI agents got caught in a loop with each other over a weekend and racked up $47,000 in charges, according to John D'Emic, CTO of Revenium. No alert fired because nothing "broke." Stories like this are why cost has become one of the most pressing questions in AI observability. Traditional monitoring was built to catch failures, not wasted spend, and AI systems can burn through budget while every dashboard stays green. Part 11 explores how AI observability relates to AI cost management, and whether they are one discipline or two ...