Frequently, a client asks to refresh their test environment with a real production data to test a new feature or process. The client may also want to restore test over prod during go-live, where data may be loaded in test for verification, then copied to prod prior to go-live.

On Premise clients will refresh their test database by themselves.

To request test DB to be refreshed with the real production data you will need to create the request through our portal providing a time slot in UTC time zone. Typically an hour time slot is enough but we would like to request a two hour window from Clients for this change. This should be the window when users are logged out of the target system. Production is not affected by the restore process.

Standard ISD request window (Mon-Fri, excluding regional public holidays):

Note: Any request outside of the above times needs approval.

We require 2 working days notice for simple copy of db (i.e. latest production copied to test) and 2 weeks if you require test to be refreshed with a copy of production from a specific point of time in the past.

Changes cannot be accommodated at weekends.

Before database restore

Before restoring a database copy, please keep in mind:

• Configuration flag list will not be overwritten

• Messaging service configuration will not be overwritten

• Customers have the choice whether the users are retained from the restore or overwritten

  • If you have a user that is used for API calls - take note of the email address of that user and once the database is restored, change the email address back to the original one (i.e. before the db restore) in the user profile of Security list. Log out and log in again in order to see the Veslink API section.

    Open