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: articles/storage/common/tape-migration-guide.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,14 +54,12 @@ Resources are the most critical part of the tape migration process, and we divid
54
54
| Hardware | - Different tape generations require different type of hardware <br> - Speed of the migration is proportional to available drives |
55
55
| Software | - Access to software that created the data is needed <br> - Access to encryption keys is needed |
56
56
57
-
Hardware is usually the most challenging part. If we're migrating existing tape generations, hardware is available, but used as part of the existing production. When migrating older tape generations, hardware is often not available anymore, and it's harder to acquire. With older tape generation, using a tape migration partner is a preferred option.
58
-
When hardware is available, careful planning is needed to make sure migration doesn't interfere with the existing production workloads. Here we can apply three different models:
57
+
Hardware is usually the most challenging part. If we're migrating existing tape generations, hardware is available, but used as part of the existing production. But for older tape generations, hardware is often end-of-life, and it's harder to acquire. With older tape generation, using a tape migration partner is a preferred, and simpler option.
58
+
When production hardware is used for migrations, careful planning is needed to make sure migration doesn't interfere with the production workloads. Here we can apply three different models:
59
59
60
-
| Model | Pros | Cons |
61
-
| ----- | ---- | ---- |
62
-
| Run production, and migration together | - Easy to schedule, and plan | - Possible impact to production <br> - Reduced hardware available for production |
63
-
| Run migration off-hours | - No impact to production | - Complex schedule, and execution <br> - Requires people working off-hours |
64
-
| Use dedicated hardware for migration | - Easy to schedule, and plan <br> - No impact to production | - Cost increase <br> - Hardware utilization post migration |
60
+
1. Use dedicated hardware for migration: simplest migration model, it is easy to schedule, and plan with no impact to production. It includes additional cost for acquiring the hardware (if not available already), and causes a low hardware utilization post-migration.
61
+
1. Run migration off-hours on production hardware: migration model with no impact to production. Requires complex scheduling, execution, and people working off-hours. Possible only if production hardware is not utilized 24x7.
62
+
1. Run production, and migration together: least-preferred migration model as it can easily impact production. This model reduces hardware available for production, requires complex scheduling, and planning. If this model is used, processes around reducing impact to production are critical to keep the migration timeline under control. This model is recommended only when production hardware has low utilization.
65
63
66
64
### Data transfer options
67
65
@@ -87,7 +85,7 @@ Here is a simple flowchart to ease the selection process.
87
85
88
86
### Data format
89
87
90
-
Data format has a large impact on migration design, and is the critical consideration for future data usability. Data can be stored in a proprietary, or native format. Proprietary formats are commonly stored as a virtual tapes, a raw image from the original tape. Native format requires to restore the data from tapes, and store them as files, or objects.
88
+
Data format has a large impact on migration design, and is the critical consideration for future data usability. Data can be stored in a proprietary, or native format. Proprietary formats are commonly stored as virtual tapes. Native format requires restoring files from tapes, and storing them as files, or objects.
91
89
92
90
| Model | Pros | Cons |
93
91
| ----- | ---- | ---- |
@@ -98,7 +96,7 @@ Main criteria for deciding the format is how do we plan to use the migrated data
98
96
99
97
## Migration process
100
98
101
-
Once we made decisions on file format, and migration execution, we can start with the migration. Migration goes through several phases.
99
+
Once we made decisions on migration execution, and prefeered file format, we can start with the migration. Migration goes through several phases.
0 commit comments