How Do I Migrate Data from an Old-Version Notebook Instance to a New-Version One?
The notebook of the old version will be discontinued. Use the new version. This section describes how to migrate data from a notebook instance of the old version to a notebook instance of the new version.
Storage Differences Between the Old and New Versions
Storage |
Old-Version Notebook |
New-Version Notebook |
Description |
|---|---|---|---|
OBS |
Supported |
Not supported |
OBS is a storage system, not a file system. In old-version notebook, remote replication and local replication of OBS data may be confused, leading to issues in controlling operations on data. Therefore, OBS mounting is removed from notebook of the new version. You can flexibly obtain and operate OBS data using code. |
OBS parallel file system |
Not supported |
Supported |
The new-version notebook allows dynamic mounting of OBS parallel file systems. You can mount storage on the details page of a running notebook instance. Data migration from the old version to the new version is not involved. |
EVS |
Supported |
Supported |
EVS disks can be attached to notebook instances of both the old and new versions. Data stored in the old version needs to be migrated to the new version. |
SFS |
Not supported |
Supported |
SFS is used in dedicated resource pools. This function has been discontinued in notebook of the old version. Therefore, data migration is not involved. |
OBS Used in Notebook of the Old Version
When notebook instances of the old version use OBS for storage, data is stored in OBS and does not need to be migrated. After a new-version notebook instance is created, directly use the data in the OBS directory. For details, see How Do I Read and Write OBS Files in a Notebook Instance?
EVS Used in Notebook of the Old Version
If EVS disks are attached to a notebook instance of the old version for storing data, back up and migrate the EVS data to a notebook instance of the new version.
- If the volume of data stored in EVS is small, download the data to a local directory, create a notebook instance of the new version, and upload the data to the new notebook instance.
- If a large amount of data is stored in EVS, upload the data to an OBS bucket. After a notebook instance of the new version is created, read data from the the OBS bucket.
For more details, see Uploading and Downloading Data in Notebook.
Others FAQs
- How Do I Use Multiple Ascend Cards for Debugging in a Notebook Instance?
- Why Is the Training Speed Similar When Different Notebook Flavors Are Used?
- How Do I Perform Incremental Training When Using MoXing?
- How Do I View GPU Usage on the Notebook?
- How Can I Obtain GPU Usage Through Code?
- Which Real-Time Performance Indicators of an Ascend Chip Can I View?
- Does the System Automatically Stop or Delete a Notebook Instance If I Do Not Enable Automatic Stop?
- What Are the Relationships Between Files Stored in JupyterLab, Terminal, and OBS?
- How Do I Migrate Data from an Old-Version Notebook Instance to a New-Version One?
- How Do I Use the Datasets Created on ModelArts in a Notebook Instance?
- pip and Common Commands
- What Are Sizes of the /cache Directories for Different Notebook Specifications in DevEnviron?
- How Do I Isolate IAM Users for Using Development Environments?
- What Is the Impact of Resource Overcommitment on Notebook Instances?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
