Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • autosubmit autosubmit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 338
    • Issues 338
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Earth SciencesEarth Sciences
  • autosubmitautosubmit
  • Wiki
  • migrate experiments

migrate experiments · Changes

Page history
Update migrate experiments authored Mar 06, 2023 by acarreri's avatar acarreri
Hide whitespace changes
Inline Side-by-side
migrate-experiments.md
View page @ 950fa635
......@@ -104,21 +104,21 @@ You can expand this **basic configuration** as follows:
Once configured, double-check that you're using the AS v3.13.0+ or a more recent one.
There are two modes of running `autosubmit migrate`, both of them consist of a two-step procedure:
* offering: `-o` moves all data from `$scratch/$original_project/$original_user/$expid` to `$tmp_dir/$expid`
* receiving: `-p` transfers all data `$tmp_dir/$expid` to `$scratch/$project_to/$user_to/$expid`
There are two ways to do it:
* Migrate everything:
* * (User-Owner) `autosubmit migrate <expid> -o`
* * (User-Target)`autosubmit migrate <expid> -p`
* Migrate only remote files (useful if the local user is the same. This is for migration from res to bsc32).
* * (User-Owner) `autosubmit migrate <expid> -o --onlyremote`
* * (User-Target) `autosubmit migrate <expid> -p --onlyremote`
Explanations: `-o` moves all data from `$scratch/$original_project/$original_user/$expid` to `$tmp_dir/$expid` and `-p` transfers all data `$tmp_dir/$expid` to `$scratch/$project_to/$user_to/$expid`
** (User-Owner) `autosubmit migrate <expid> -o`
** (User-Target)`autosubmit migrate <expid> -p`
* Migrate only remote files (useful if the local user is the same. This is for migration from res to bsc32).
** (User-Owner) `autosubmit migrate <expid> -o --onlyremote`
** (User-Target) `autosubmit migrate <expid> -p --onlyremote`
Warning: if you use the complete command (without onlyremote), the autosubmit folder of your experiment (`/esarchive/autosubmit/$expid`) will diseappear during the process. Don't run your autosubmit command from this folder, as it won't go for the second step because this folder won't exist anymore.
**Warning**: if you use the complete command (without onlyremote), the autosubmit folder of your experiment (`/esarchive/autosubmit/$expid`) will diseappear during the process. Don't run your autosubmit command from this folder, as it won't go for the second step because this folder won't exist anymore.
**Before running** the experiment with the new user, remind to change the **queue** parameter (example CLASS_A to bsc_es) if necessary.
**Before running** the second step of the migration (with the new user), remind to change the **queue** parameter (example CLASS_A to bsc_es) if necessary in the platform.conf file.
......
Clone repository
  • Code coverage
  • Deployment
  • Issues documenting different aspects
  • Leaflet
  • Possible Operational Problems and Solutions
  • Running Autosubmit in Earth Sciences
  • Testing_Suite
  • Updating ReadTheDocs Autosubmit documentation
  • Visual Identity
  • [DestinE] Autosubmit VM on Lumi
  • background
  • bibtex
  • databases
  • development
  • dissemination
View All Pages