- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-21-2014 03:35 PM
I don't find anything within the wiki that explains the backup processes in ServiceNow.
Every 24 hours
Every 48 hours
Every 72 hours
Every 7 days
????
Solved! Go to Solution.
- Labels:
-
Performance Analytics

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-21-2014 06:17 PM
I believe it's mirrored to another data center immediately. Check out Section 2.4 on this wiki link:
http://wiki.servicenow.com/index.php?title=Product_Overview
You can submit a ticket on the HI server to find out where your primary data center is and where your fail over data center is located.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-21-2014 06:17 PM
I believe it's mirrored to another data center immediately. Check out Section 2.4 on this wiki link:
http://wiki.servicenow.com/index.php?title=Product_Overview
You can submit a ticket on the HI server to find out where your primary data center is and where your fail over data center is located.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-21-2014 06:29 PM
Actually I found the anwser in the section 2.5
Thanks!!!
2.5 Backup and Recovery
ServiceNow maintains seven daily and three weekly backups on disk. Daily backups are preserved for one week. Weekly backups are preserved for one month. The backup data never leaves the datacenter. Backups include data from the primary and mirrored datacenters of all customers instances, including production and sub-production instances.
ServiceNow generally does not schedule backups for specific instances because most instances share a database server with several other instances. The entire database server is backed up each night.
Restoring from backup, especially for production, is a last resort. There is always the potential for data loss because anything saved after the backup was taken is lost. Also, while the restoration process is running, the production instance is unavailable. For some customers, it can take many hours to restore causing an unacceptable amount of downtime.