There are multiple approaches available to back up and restore ServiceNow data.

Restoring ServiceNow data is like planning for a chess move, several moves in advance. It’s been said that “no plan survives first contact with the enemy,” but you can learn from past events. 

And what we hear from ServiceNow customers is that they seek more control over how they both back up and restore ServiceNow data. So we have some ideas in mind for how ServiceNow customers can restore data better.

How ServiceNow Backs Up and Restores Your Data

ServiceNow makes a daily backup of your whole instance, retaining the backups over the course of 6 days. They also make weekly instance backups, keeping them for 4 weeks. 

If you need to restore to a previous version of your instance, you can contact ServiceNow support. That restore is targeted to the same instance, overwriting the entire instance and making it unavailable while the restore is taking place.

This backup/restore process enables a certain level of operational resilience. But when you take a more granular approach to backup and restore, you act with more agility, improving both risk mitigation and operational resilience.

A More Granular Approach to Backup and Restore

Imagine that a spreadsheet file on your computer has become corrupt. Well, you don’t wish to restore the entire laptop, which might overwrite other needed data – you just need an earlier version of that spreadsheet file. 

In a similar way, you can reduce ServiceNow data loss if you back up and restore at the object level. Of course, maintaining the referential integrity of recovered data would also be nice. 

For example, you might have changes to your catalog that you wish to put into production. You think to yourself, “If this update doesn’t work out, I want to restore my catalog to this exact moment – this right-now snapshot in time before I roll out these changes.”

So here are some of the ways that ServiceNow customers seek more granular control over backup and restore with ServiceNow data.

1. “I want to restore only the data and applications I choose.”

When you restore your entire instance, you lose data that has been added or modified since the backup that you’re restoring.

2. “I want to initiate the restore myself – right now, from within ServiceNow.”

Without the ability to rapidly restore ServiceNow data, you risk extended downtime, delaying business operations.

3. “I want to restore to a different instance.”

By restoring to a different instance, you can migrate data and applications without having to make sure that everything is included in an update set.

4. “I want to restore to any point in time I choose.”

When you make backups more frequently than ServiceNow does or at intervals that you customize, you have more control to restore to a point in time that you desire.

5. “I want to restore from a backup made beyond 6 days ago – or 4 weeks ago.”

By making your own backups, the length of time that they are retained is up to you. You would be able to make and keep as many backups as your storage space allows.

6. “I want to keep the ServiceNow instance running while the restore takes place.”

When ServiceNow returns your instance to a prior backup, the instance is unavailable – for several hours potentially. What if operations could continue normally while you are restoring data?

A Better Way Forward with Backup and Restore

To maintain operational resilience and customer trust, companies must protect their data from attacks, disasters, and even just loading errors or failed rollouts. Moving quickly to protect your ServiceNow data and applications enables business to keep moving forward.

With Perspectium DataSync Snapshot, you control your ServiceNow backup and restore. You choose what you backup when and you restore that with a single button click. Simple. Fast. Under your control.

For a better way forward with restoring ServiceNow data, see our introduction and demo for DataSync Snapshot.

Related Posts