Solved

Transfer TimeXtender to another Server

  • 18 May 2023
  • 3 replies
  • 99 views

Dear Community, 

I have a few questions regarding transferring to another internal server and if you could help me with any of these questions help is appreciated.

We have currently two servers running on SQL Server 2016, one server has the DEV and ACC environments and the second server has our PROD Environment (TimeXtender 20.10.39.64).

The environments were installed by a supplier but their external employee left, so we want to try and install this on our own (with snapshots/backups in case something goes wrong).

We want to try and move the DEV/ACC environment to a new server which has the same TimeXtender version but SQL Server 2019. For this move I have 3 questions:

  • Can I just export and import the project from old server to my new server and load the data again into a new SQL database?
  • How can I set up my environments in such a way that my DEV → ACC → PROD traject isn’t changed. I could not find those settings and had trouble finding them on the legacy page. As the DEV/ACC environments are on the same server and the PROD environment is on another server.
  • Is it harmful to have a DEV/ACC environment on a higher SQL Version as the PROD environment? We would like to upgrade everything to 2019, but we want to test with our DEV/ACC environments to not hurt our production and the business.

If you can help me with any of this any help would be appreciated. Either by linking me to the correct page or any useful tips or remarks I should have.

Kind regards,

Remco 

icon

Best answer by Christian Hauggaard 22 May 2023, 09:10

View original

3 replies

Userlevel 1
Badge +1

Hi @remco 

You can start with article by Thomas Lind:
https://legacysupport.timextender.com/hc/en-us/articles/115001313583-How-do-I-move-a-project-from-one-server-to-another-
 

BR

Anders

Userlevel 6
Badge +5

​​​Hi @remco 

  • For a complete migration, I would recommend backing up and restoring the TimeXtender repository on the new server, rather than migrating individual projecs.
  • If you are moving to a new server then the settings for the PROD environment under global databases must be updated, and necessary firewall rules must be configured.
  • Running DEV/ACC environment on a higher SQL Version than the PROD environment should be OK, unless using custom scripts/code that it not compatible with SQL 2019.

Thank you for the advice!

We are going to try this tomorrow following these steps. 

Reply