This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Find answers, ask questions, and share expertise about Alteryx Server.
It's the most wonderful time of the year - Santalytics 2020 is here! This year, Santa's workshop needs the help of the Alteryx Community to help get back on track, so head over to the Group Hub for all the info to get started!
Perhaps you are still interested in moving workflows and apps to a different server. If so, you might find a user's comment helpful. The information there doesn't cover organizational structure like collections and districts, nor does it help you set up schedules, so you'll still have to do that part "manually."
Lisa LePome Senior Customer Support Engineer -- Knowledge Management Coach Alteryx, Inc.
The new API endpoints are a great way to migrate apps/workflows etc. in a programmatic way to a new environment. If you are looking to just take a copy of your TEST environment and overwrite your PROD environment you absolutely can also take a back up of the MongoDB itself and restore on the PROD machine. The main thing to consider here is that this is not going to preserve anything that's already on the PROD environment - you're just making a mirror image of TEST. You'd also need to ensure that your PROD environment has permission to reach out to all the same places and has access to all the necessary dependencies for your workflows in order to make the transition seamless. Check out this link if you'd like to know more about the Backup and Restoration process:
Thanks, I was hoping that I could replace everything from TEST onto PROD for starters.
I also tested this and it worked flawlessly.
For others reading this thread, I did the following steps:
1. Upgraded both servers to the same version (2019.2)
Then On the test server:
2. Stop the AlteryxService
It did not stop, even after 10 minutes because a job was running. Therefor I closed the Alteryx process as well. Make sure not to cancel this process if any critcal workfow is running. 3 Open Command Line as administrator 4. Run the following "C:\Program Files\Alteryx\bin\AlteryxService.exe" emongodump=c:\temp\dumpOutput
5. Copy the folder that got created c:\temp\dumpOutput to clipboard (around 1.5 GB)
6. Start the AlteryxService
On PROD server
7. Stop the AlteryxService
8. Past the above folder into c:\temp
9. Run the following from command line as administrator "C:\Program Files\Alteryx\bin\AlteryxService.exe" emongorestore=c:\temp\dumpOutput,c:\temp\restoreInput
This extracted the MondoDB content into a folder C:\temp named restoreInput. So I could have changed the parameter of the Run Command to point directly to the install path of the MongoDB. I did not, but no worries.
10. Copy the content inside "restoreInput" to the MongoDB directorey. Do not copy/paste the folder itself. For me it was the default location "C:\ProgramData\Alteryx\Service\Persistence\MongoDB"
11. Start AlteryxService
And that was it. The whole structure of scheduels, user settings, collections and everything else was successfully transfered from TEST to PROD.
Keep in mind that ALL schedules were transfered as well, meaning they were active at both servers at the same time. You will need to disable all schedules from TEST, one by one.
As of 6/13 the Host Recovery Guide content appears to be missing from the above link that LisaL posted -> Alteryx Server Host Recovery Guide. I have provided my feedback by responding to the "Was this Helpful" form provided at that link - it looks like it will be a great reference, once the content appears as expected.