A few weeks ago, a story came out of Delhi University that I have not been able to stop thinking about.

An assistant professor someone who had been working on their PhD research for six years had a bag stolen from a parked vehicle near North Campus. Inside that bag was a laptop. On that laptop was everything: drafts, datasets, analysis, unpublished findings. Six years of intellectual work. Gone.

The police case is ongoing. The laptop has not been recovered.

And the thing that hit me most when I read this was not the theft itself.

It was the realization that this could happen to almost anyone working in research today.

The One-Line Version

The Delhi University incident asks a question that most researchers quietly avoid:

If your laptop disappeared right now, how much would you lose, permanently?

For a lot of people, the honest answer is: most of it.

Why This Specific Story Unsettled Me

I work in theoretical physics, so my data is mostly calculations, notes, LaTeX files, references.

But I know people working in fields where the data is irreplaceable fieldwork interviews, experimental readings, longitudinal observations. The kind of data where you cannot just go back and collect it again.

Six years in, just before the final stretch of a PhD, is arguably the worst possible moment to lose everything.

And the theft was not sophisticated. It was a bag in a parked car. Something that happens every day in every city in India.

That gap between how fragile research data actually is, and how casually most of us treat its protection is what the story made visible.

The Real Problem Is Not the Theft

Here is the thing:

The theft is the event that made the news. But the theft is not really the problem.

The problem is what made the theft catastrophic rather than just inconvenient.

If the data had been backed up truly backed up, not just “I think it’s on my Google Drive somewhere” losing the laptop would mean losing a device. Painful, expensive, disruptive. But not career-defining.

The reason this story exists at all is because the data lived in one place.

And I do not say that to assign blame. I say it because I have done the same thing. Most researchers I know have done the same thing. There is something about research work maybe its intimacy, maybe the pace of it, maybe just the habits we develop when we are tired and busy that makes it easy to defer the boring administrative tasks of data hygiene indefinitely.

Until you cannot anymore.

What “Backed Up” Actually Means

This part matters because I think there is a false sense of security that comes from vague backup habits.

Having a file on Google Drive does not mean it is backed up not if you only synced it three months ago.

Having an external hard drive in the same bag as your laptop is not a backup.

What backup actually requires is something like this:

  • At least two copies, in at least two different locations
  • One of which is off-site or cloud-based
  • Updated frequently enough that losing the last version would not matter
  • Actually tested meaning you have opened those files from the backup, not just assumed they are there

This sounds obvious when written out. It is less obvious at 1am when you are finishing a draft and your mind is elsewhere.

The Infrastructure Gap in Indian Academia

There is also a larger structural issue here that the Delhi story highlights.

Research data security is almost entirely treated as an individual researcher’s problem in most Indian universities.

There is no standard institutional cloud storage for PhD scholars at most places. No mandatory backup protocols. No training on data security during onboarding. No awareness programs.

The researcher is handed a supervisor, an enrollment number, and a library card. What happens to the data is largely up to them.

This is a failure of institutional design.

Universities that take research seriously need to think about:

  • Providing researchers access to institutional storage systems
  • Building awareness programs on data practices into PhD orientation
  • Encouraging or requiring version-controlled backups for research files
  • Creating infrastructure where data can live somewhere beyond a single personal device

This does not need to be expensive or complicated. But it requires someone deciding that it matters.

The Emotional Weight of Data Loss

I want to name something that the technical conversation around backups can obscure.

Research is not just data. It is also time. And momentum. And the internal state you were in when you wrote something, understood something, made a connection you had never made before.

You can sometimes reconstruct files. You cannot reconstruct the version of yourself that made them.

The Delhi professor described the loss as emotionally devastating and that framing is exactly right. This is not like losing a laptop. This is losing a period of your life.

That weight is worth sitting with, because I think it is what should actually motivate researchers to treat their data more seriously. Not because backups are a bureaucratic requirement. But because the work matters and protecting the work is part of taking it seriously.

What This Problem Is Not

It is worth being clear about what I am not arguing here:

  • This is not a reason to be paranoid about leaving your home
  • This is not a criticism of the researcher who lost their work
  • This is not just a problem in India, or specific to academia

It is a structural issue, with a practical solution, that most of us keep postponing.

Some Foundational Habits Worth Considering

If you are a researcher reading this, the practical action is not complicated:

  • Pick a cloud sync service and actually use it, daily
  • Keep version histories turned on wherever possible Google Drive, Dropbox, and OneDrive all support this
  • Maintain a working copy and a backup copy as distinct things
  • If your work involves irreplaceable data (fieldwork, experiments, interviews), treat backing it up as part of the work itself, not a separate chore
  • Periodically verify that your backups actually contain what you think they do

The tools exist. The friction is mostly psychological.

Why I Keep Coming Back to This

There is something about the Delhi University story that sits at an intersection I find genuinely important:

  • the structural neglect of how Indian academia supports its researchers
  • the quiet fragility of intellectual work that takes years to build
  • and the strange distance between how much we care about our research and how casually we protect it

It is one of those situations where the problem is not dramatic or invisible.

It is mundane and very fixable.

And that, somehow, makes it more worth paying attention to.

Closing Thought

Six years is not an abstraction. It is mornings before sunrise. It is revisions made at the end of exhausting days. It is the slow accumulation of understanding that does not happen quickly or easily for anyone.

The least we can do for ourselves, for that work is make sure a bag theft cannot erase it.

Back it up. Today. Not tomorrow.

Related reading: