SnowMirror archive is a Java agent service in a customer’s local environment (Windows and Linux operating systems are supported), and it downloads data from a ServiceNow instance according to the criteria you set. No ServiceNow changes are needed; it uses the out-of-the-box API available in every instance. The SnowMirror team guarantees that it will keep up with every new ServiceNow release.
SnowMirror Archive saves you money by off-loading obsolete attachments and data from your ServiceNow cloud according to rules that you set. Why pay for data that no one has accessed in years?
ServiceNow performance can be affected when instances become full of obsolete data. SnowMirror Archive can improve performance by reducing the size of tables and moving obsolete attachments to your own secure storage.
Your ServiceNow data is offloaded to your own infrastructure, and you can see what’s where using SnowMirror Archive’s viewer. When your data and attachments are on your infrastructure, you can use it for one-directional integration to other platforms.
SnowMirror Archive helps you remain in compliance by keeping your data in the correct data domiciles and handling conditions. Your data is always at hand on your own infrastructure should you ever need to restore it.
Users who don’t actively manage instance size can get an unpleasant surprise in their storage costs, and that’s exactly where SnowMirror Archive can help. Attachments typically make up the biggest part of storage, and therefore costs. Using rules that you set yourself, SnowMirror Archive makes it easy to offload obsolete attachments and data to a relational database such as Oracle or Microsoft SQL Server on your own secure infrastructure, to a filesystem, or cloud storage such as Azure Storage, keeping costs down and performance up.
Data is loaded from a ServiceNow instance and stored on your infrastructure. It’s your data and you can decide how to store it. SnowMirror Archive also includes a viewer to see the data has been offloaded as it appears in ServiceNow.
SnowMirror Archive’s innovative viewer lets you see what your offloaded data looks like in ServiceNow so that you can make informed decisions on what to do with it. The form and list layouts are taken automatically from the ServiceNow metadata, so you are sure to know the context of the data in ServiceNow. This lets you see which data is offloaded in your mirror database.
All
MySQL, MariaDB, PostgreSQL
All
All
N/A
Custom
Custom
All
2
2
All
Silver 8 x 5
Silver 8 x 5
Gold 8 x 5
Platinum 24 x 7
30 days
3 years
3 years
3 years
All prices are monthly excluding VAT or other taxes. Standard duration is 36 months or longer. Minimal contract lenght is 12 months.
All
All
Silver 8 x 5
30 days
All prices are monthly excluding VAT or other taxes. Standard contract duration is 36 months or longer. Minimal contract lenght is 12 months.
MySQL, MariaDB, PostgreSQL
N/A
2
Silver 8 x 5
3 years
All prices are monthly excluding VAT or other taxes. Standard contract duration is 36 months or longer. Minimal contract lenght is 12 months.
All
Custom
2
Gold 8 x 5
3 years
All prices are monthly excluding VAT or other taxes.Standard contract duration is 36 months or longer. Minimal contract lenght is 12 months.
All
Custom
All
Platinum 24 x 7
3 years
All prices are monthly excluding VAT or other taxes. Standard contract duration is 36 months or longer. Minimal contract lenght is 12 months.
SnowMirror creates a ServiceNow read-replica in your own database. Having selected ServiceNow tables in your data center can have many benefits. These are the three most popular use cases:
SnowMirror creates a ServiceNow read-replica in your own database. Having selected ServiceNow tables in your data center can have many benefits. These are the three most popular use cases:
SnowMirror creates a ServiceNow read-replica in your own database. Having selected ServiceNow tables in your data center can have many benefits. These are the three most popular use cases:
SnowMirror creates a ServiceNow read-replica in your own database. Having selected ServiceNow tables in your data center can have many benefits. These are the three most popular use cases:
SnowMirror creates a ServiceNow read-replica in your own database. Having selected ServiceNow tables in your data center can have many benefits. These are the three most popular use cases:
SnowMirror creates a ServiceNow read-replica in your own database. Having selected ServiceNow tables in your data center can have many benefits. These are the three most popular use cases:
SnowMirror creates a ServiceNow read-replica in your own database. Having selected ServiceNow tables in your data center can have many benefits. These are the three most popular use cases:
Yes. If you need high availability there is a possibility to install several SnowMirror installations. Some of our customers even install one SnowMirror into their DRC centers. SnowMirror architecture is cluster-ready and if one node goes down the other node is still synchronizing the data. We usually support this kind of requirements individually and we cooperate on the customer cluster design.
The HA setup is available only for the MAX Edition.
No. The only mandatory requirement is to have a user account which has sufficient rights to access ServiceNow data and meta-data. However, if using the SOAP API, we recommend activating the Aggregate Web Services ServiceNow plug-in to improve the user experience, enable a few fancy features and add a small performance boost.
No. If you have several ServcieNow instances you have to install several SnowMirrors. The idea behind it is the same as for the MID servers.
Yes. And it is quite usual to run a mirror for a test ServiceNow instance and a development instance on one server. It is necessary to configure different ports and different Windows service names. Use the Custom Installation option if installing using the Windows installer. A similar approach applies to Linux systems.
SnowMirror in not resource intensive. It is a Java application running as a Windows service or a Unix daemon. It requires a server to be installed on. The server can be a small virtual or physical machine. The typical configuration is a dual core CPU server with 2 GB RAM and 5 GB HDD. We even recommend to install SnowMirror on the same machine as the ServiceNow MID server. You can save one server using this approach.
Read more about SnowMirror requirements in the admin guide:
http://www.snow-mirror.com/doc/#section-servicenow
The Aggregate Web Services plug-in is a small plugin adding the aggregate method into all direct web services in ServiceNow. SnowMirror is using this new operation to count the records to insert or update before the actual download starts. By activating the plugin the progress bars work better, the count buttons enable you to count records in tables and SnowMirror is able to optimize the downloading algorithm a bit.
The main database is the mirror DB where the ServiceNow data is being stored. However, SnowMirror requires to maintain its configuration in a second database. So-called config DB. The config DB is configured during the installation phase and it is using H2 embedded database by default. The mirror DB can be configured in SnowMirror Settings page.
See the picture of the whole SnowMirror architecture.
If your synchronization failed and you got an error similar to java.sql.BatchUpdateException: Data truncation, it can have two different root causes.
1) Something has changed on the ServiceNow side. Usually someone made a string field longer than before. For example your ServiceNow admin made incident short_description longer (max length) from 80 to 200. So it means the new incident subjects cannot fit into your varchar(80) in the mirror database. To fix this, either manually alter the mirror table (column) or re-create the whole synchronization and perform an initial data load.
2) ServiceNow does not always respect its own data constraints. E.g. try to synchronize the sys_perspective table and it fails by default because one column in this table is configured to have 40 chars as its max length however the longest string in the column has 125 characters by default. There is no other solution than to manually alter the mirror database table to reflect the real situation.
Auto Schema Update feature enables to modify the mirrored table automatically according to the changes on the ServiceNow side. If enabled all the table columns are being synchronized. If there is a new columns in ServcieNow, SnowMirror automatically adds it into the mirror table. The same applies for modified columns a removed ones.
ServiceNow enables to specify a parent for a table. It means all the columns in the parent table are used for the child table as well. For example the table task (parent) and incident (child). Many tables are derived from the task table. The whole CMDB is build on this inheritance design pattern. Etc.
SnowMirror enables two approaches when synchronizing inherited tables (e.g. incident)
1) Synchronize two tables. This is the way ServiceNow itself stores the data. You have to synchronize two tables (e.g. task and incident) and to obtain the incident record you have to join the tables using the sys_id primary key in both tables. The advantage of this approach is lower redundancy. If you are synchronizing several tables derived from the task table the situation is simpler to perform some type of queries.
2) Synchronize only one table with all parent inherited columns included. This is an approach that a typical user expects. To sync the data as it is displayed in the web application. Check the checkbox Include inherited columns in the synchronization settings to choose this approach.
To identify new or updated records in ServiceNow is a straightforward way. However to find the records deleted in a certain time window is not so simple. Most of the tables are audited so the default strategy search for deleted records in the system journals. You can choose different strategies if you need or if the table is not being audited. Truncate option means to perform Clean & Synchronize operation for every sync run (initial load every run). Diff is a good way to find the deleted records in a non-audited table and None ignores the deletes at all.
Please read more about the delete strategies in our user guide.
Please note that synchronization settings for Views do not contain the delete strategy choice at all. It always performs the Truncate option because there is no way how to achieve incremental updates.
SnowMirror does not access the database directly. ServiceNow does not allow neither customers not partners to access the underlying instance database. All the data is downloaded using the our-of-the-box API called Direct Web Services. Event the original ODBC driver uses this API which is the reason why the driver is so limited and slow.
SnowMirror distribution contains an optional ServiceNow dashboard application. If you have installed the update set into your ServiceNow instance enable this setting to start sending SnowMirror activity into the ServiceNow instance.
No. You pay only for every SnowMirror connected to your production ServiceNow instance. Test, UAT, development or sandbox instances are for free.
SnowMirror license is bound to a certain ServiceNow instance host name (e.g. yourcompany.service-now.com). So the ServiceNow host name you configure in Settings -> ServiceNow has to match the license host name. Please do not forget to restart SnowMirror after you change the instance in the Settings. In case of a trial license please feel free to generate yourself another trial license on our website if you need if for a different ServiceNow instance.
