...
See the page on Repository Administration for instructions on how to backup and restore data from Synapse schemas. To migrate data from one instance to another in a stack the current procedure is to take a back up of the old stack, shut the stack down, and then copy the data to the new stack. Note there is a small risk of data changed in the old stack being lost if somebody adds something to the repository after the backup process has completed. This will be addressed by PLFM-404 404 . (Even if you shut down the Synapse web portal before you take the backup, changes can still come in via the repo API, which must be up to take the backup.) In meantime, workaround by communicating with team members and our small user base.
...
Once you have CNAMES pointed to the new stack, update stackInstance-stack.properties file, upload to S3, and restart the app servers to apply the change. Having our components talk to each other via the public aliases avoids security exceptions. See PLFM-506506 .
Verify Deployment
To verify deployment, run top-level queries against the repository instances from an authenticated account.
...
See Managing R packages for how to install the lastest version on Belltown.
Once the latest version in deployed to the CRAN server, you should upgrade the R Synapse client version on Belltown. An upgrade script is available in /work/platform/configuration/deployment/synapseRClient.
| Code Block |
|---|
cd /work/platform/configuration/deployment/synapseRClient
sudo ./upgradeSynapseClient.sh |
Make sure to check the output for error messages.
How to run the Phenotype Descriptions Loader
...