From version < 16.1 >
edited by Jonathan Rubiero
on 2018/05/04 12:16
To version < 17.1 >
edited by Jonathan Rubiero
on 2018/05/04 12:22
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -44,6 +44,8 @@
44 44  
45 45  ==== Case 2 : new instance running alongside the old one ====
46 46  
47 +===== Start new instance =====
48 +
47 47  If you new STEP instance will run alongside the existing one, you will have to start a new instance of MongoDB on a different port that the one used by the previous instance.
48 48  
49 49  Follow below instruction in order to achieve this :
... ... @@ -61,6 +61,31 @@
61 61  )))
62 62  * use this modified script to start your new MongoDB instance
63 63  
66 +===== Restore the data =====
67 +
68 +Now that your new instance is running, you can restore your data into it (considering the new MongoDB instance is running on port 28017) :
69 +
70 +====== Case 1 : full backup available ======
71 +
72 +* Considering your backup folder is called "backup", execute the following command :
73 +* (% class="box" %)
74 +(((
75 +mongorestore ~-~-port 27018 -d step backup
76 +)))
77 +
78 +====== Case 2 : partial backup available ======
79 +
80 +* Execute the following commands to restore your keywords, test plans, user and scheduled entries :
81 +* (% class="box" %)
82 +(((
83 +mongoimport ~-~-port 27018 -d step -c functions functions.json
84 +mongoimport ~-~-port 27018 -d step -c artefacts artefacts.json
85 +mongoimport ~-~-port 27018 -d step -c users users.json
86 +mongoimport ~-~-port 27018 -d step -c tasks tasks.json
87 +)))
88 +
89 +
90 +
64 64  == Controller ==
65 65  
66 66  (((
Copyright © exense GmbH
v1.0