what is the back up procedure for Service Now
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2017 11:17 AM
need to know what the back up proceddure is CLOUD backup for ALL services.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2017 11:20 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2017 11:23 AM
Hi Eddie,
Instances are automatically backed up daily during non-peak business hours on schedules defined by ServiceNow. We do not adjust the timing of existing backup schedules. we also take full backup of the database, so that includes all tables along with them.
Thanks,
Dravvy
Please Hit like, Helpful or Correct depending on the impact of the response
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2017 11:47 AM
Hi,
Normally Service Now takes backup of Production instances, the backup cycle consists of four weekly full backups and the past 6 days of daily
differential backups that provide 28 days of backups. Below link may be useful which defines the backup and High Availability Concept service now provides:
To be on a safer side you can reach out to HI Support(Service Now https://www.servicenow.com/support/contact-support.html) for backup conformation.
Hope this helps.Mark the answer as correct/helpful based on impact.
Regards,
Shloke
Regards,
Shloke
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-06-2017 06:42 PM
Are you just working on a DR plan, or do you actually plan to do something that requires restoring from a backup?
The ServiceNow backup is for DR, and not to be relied upon.
Depending on what you are trying to do, you may be better off cloning or developing scoped apps backed up in GitHub or GitLab.
For example: On a major upgrade, we clone Prod to Test just before upgrading Prod. We keep it around during "hyper-care" which is usually about two months. That way, we have an easy way to check if an error is really new, or if a user just wishes it worked that way before and after the upgrade.
Another: When we are ready to clone over the Dev instance, each developer completes and pushes their global scope update sets to Test (and if you are paranoid like me, also exports the update to a local xml file.) After the clone, they pull back their update sets.
I would NEVER want to restore from the ServiceNow backup. I would only resort to that if our database was thoroughly burnt toast.