You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/sideloader/pages/migrate-sideloader.adoc
+11-8Lines changed: 11 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -672,7 +672,8 @@ Microsoft Azure::
672
672
For example, `/var/lib/cassandra/data/`.
673
673
* *`SNAPSHOT_NAME`*: The name of the xref:sideloader:migrate-sideloader.adoc#create-snapshots[snapshot backup] that you created with `nodetool snapshot`.
674
674
* *`MIGRATION_DIR`*: The entire `uploadBucketDir` value that was generated when you xref:sideloader:migrate-sideloader.adoc#initialize-migration[initialized the migration], including the trailing slash.
675
-
* *`NODE_NAME`*: The host name of the current node you are uploading the snapshot from.
675
+
* *`NODE_NAME`*: The host name of the node that your snapshots are from.
676
+
It is important to use the specific node name to ensure that each node has a unique directory in the migration bucket.
676
677
677
678
+
678
679
[source,bash,subs="+quotes"]
@@ -720,20 +721,20 @@ After uploading snapshots, you must xref:sideloader:migrate-sideloader.adoc#impo
720
721
721
722
=== Idle migration directories are evicted
722
723
723
-
As an added security measure, migrations that remain continuously idle for one week are subject to xref:sideloader:cleanup-sideloader.adoc[automatic cleanup], which deletes all associated snapshots, revokes any unexpired upload credentials, and then closes the migration.
724
-
725
-
{company} recommends that you xref:sideloader:cleanup-sideloader.adoc#reschedule-a-cleanup[manually reschedule the cleanup] if you don't plan to launch the migration within one week or if you need several days to upload snapshots or import data.
726
-
727
724
[WARNING]
728
725
====
729
726
For large migrations, it can take several days to upload snapshots and import data.
730
727
Make sure you xref:sideloader:cleanup-sideloader.adoc#reschedule-a-cleanup[manually reschedule the cleanup] to avoid automatic cleanup.
731
728
====
732
729
730
+
As an added security measure, migrations that remain continuously idle for one week are subject to xref:sideloader:cleanup-sideloader.adoc[automatic cleanup], which deletes all associated snapshots, revokes any unexpired upload credentials, and then closes the migration.
731
+
732
+
{company} recommends that you xref:sideloader:cleanup-sideloader.adoc#reschedule-a-cleanup[manually reschedule the cleanup] if you don't plan to launch the migration within one week or if you need several days to upload snapshots or import data.
733
+
733
734
[#import-data]
734
735
== Import data
735
736
736
-
After you upload snapshots for each origin node, import the data into your target database.
737
+
After you completely upload snapshots for each origin node, import the data into your target database.
737
738
738
739
Data import is a multi-step operation that requires complete success.
739
740
If one step fails, then the entire import operation stops and the migration fails.
@@ -745,10 +746,12 @@ If one step fails, then the entire import operation stops and the migration fail
If necessary, you can xref:sideloader:stop-restart-sideloader.adoc[pause or abort the migration] during the import process.
751
+
* Before you start the import process, make sure all snapshots are completely uploaded.
752
+
For commands to monitor upload progress and compare uploaded data against the original snapshots, see xref:sideloader:migrate-sideloader.adoc#upload-snapshots-to-migration-directory[Upload snapshots to the migration directory].
751
753
754
+
* If necessary, you can xref:sideloader:stop-restart-sideloader.adoc[pause or abort the migration] during the import process.
Copy file name to clipboardExpand all lines: modules/sideloader/partials/sideloader-partials.adoc
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,8 @@ For example, `/var/lib/cassandra/data`.
18
18
* *`KEYSPACE_NAME`*: The name of the keyspace that contains the tables you want to migrate.
19
19
* *`SNAPSHOT_NAME`*: The name of the xref:sideloader:migrate-sideloader.adoc#create-snapshots[snapshot backup] that you created with `nodetool snapshot`.
20
20
* *`MIGRATION_DIR`*: The entire `uploadBucketDir` value that was generated when you xref:sideloader:migrate-sideloader.adoc#initialize-migration[initialized the migration], including the trailing slash.
21
-
* *`NODE_NAME`*: The host name of the current node you are uploading the snapshot from.
21
+
* *`NODE_NAME`*: The host name of the node that your snapshots are from.
22
+
It is important to use the specific node name to ensure that each node has a unique directory in the migration bucket.
0 commit comments