Method for supporting data archiving transparent access

Abstract

The invention provides a method for supporting data archiving and transparent access, and relates to the technical field of data storage and visity.The method comprises the steps that mounting directories of first-level storage and second-level storage are created at a client side, a dynamic symbolic link pointing to a mounting point of the second-level storage is created, and files are migrated to the second-level storage from the first-level storage through a migration tool, and meanwhile, creating a symbolic link of the file in the first-level storage. And when a user accesses the file in the first-level storage, analyzing the actual path of the target file in the second-level storage based on the symbolic link, and accessing the file in the second-level storage through the dynamic symbolic link. Through the method, on the premise of not modifying the symbolic link in the first-level storage, continuous access to the archived file is realized, transparent archiving and dynamic link access of the file are realized, the limitation of a traditional stub scheme is avoided, and the flexibility and efficiency of data storage and access are improved.

Description

Technical Field

[0001] The present application relates to the technical field of data storage and access, and in particular to a method for supporting transparent access to data archiving. Background Art

[0002] Data archiving transparent access technology, as a key means of optimizing storage systems, is widely used in enterprise-level data management, cloud computing platforms, and big data processing. With the rapid development of mobile internet and smart devices, the amount of global data is growing exponentially. According to Statista, the total global data volume will reach 149ZB in 2024. Against this backdrop, storage tiering technology has emerged. By storing critical core data on high-performance storage devices and migrating non-core data to large-capacity, low-cost storage devices, this technology achieves efficient resource utilization. Specifically, this technology system covers the entire process from data classification and migration strategy formulation to access path management, including key steps such as identifying hot and cold data, scheduling migration tools, and maintaining stub files. The transparent access mechanism is the core of ensuring user-unaware data migration and typically relies on the collaborative operation between the file system and storage devices to maintain data accessibility and consistency.

[0003] However, in the existing transparent access method, the private stub files generated directly by the migration tool do not follow the industry's common file system standards, which may lead to problems such as poor cross-vendor compatibility and strong system closure. Specifically, the stub file records static path information. If the mount point changes or the stub file is accidentally deleted, it will directly lead to the isolation of archived data, affecting the continuous availability of data and the maintainability of the system. In addition, because the format and management method of the stub file are bound to a specific migration tool, users often need to reconfigure a large number of data paths when changing storage platforms or migration tools, which increases the migration cost and operational complexity. Based on this, the existing technology has obvious deficiencies in dynamic adaptability, path flexibility and system openness. There is an urgent need for a standardized and dynamically updateable access mechanism to improve the compatibility and stability of the overall system. Summary of the Invention

[0004] The present application aims to solve one of the technical problems in the related art at least to a certain extent.

[0005] To this end, the first purpose of this application is to propose a method for supporting transparent access to data archiving, which is used to solve the vendor binding problem caused by the use of private stub files in existing data archiving transparent access solutions, as well as the maintenance difficulties and data isolation problems caused by static binding of stub file paths.

[0006] The second objective of this application is to provide a system that supports transparent access to data archives.

[0007] The third objective of this application is to provide an electronic device.

[0008] The fourth object of this application is to provide a computer-readable storage medium.

[0009] A fifth object of this application is to provide a computer program product.

[0010] To achieve the above objectives, the first embodiment of the present application proposes a method for supporting transparent access to data archives, including:

[0011] Create a first mount directory and a second mount directory on the client, where the first mount directory is mounted to the shared directory of the primary storage, and the second mount directory is mounted to the shared directory of the secondary storage;

[0012] Creating a dynamic symbolic link pointing to the secondary storage mount point in the client, where the direction of the dynamic symbolic link can be dynamically adjusted as the mount point path changes;

[0013] When migrating a target file from primary storage to secondary storage using the migration tool, a symbolic link of the target file is created on the primary storage;

[0014] When a user or application accesses a file in the primary storage, if the file is a symbolic link, the actual path of the target file in the secondary storage is parsed based on the symbolic link, and the target file in the secondary storage is accessed through the dynamic symbolic link.

[0015] Optionally, the process of creating the dynamic symbolic link includes:

[0016] A dynamic symbolic link is created in the client's local file system, and the dynamic symbolic link points to the mount point path of the secondary storage; the mount point path is configured as different path names in different clients or different storage clusters, and the pointing of the dynamic symbolic link can be uniformly managed and dynamically updated.

[0017] Optionally, the migration tool migrates the target file from the primary storage to the secondary storage according to a preset migration strategy, where the migration strategy is determined based on at least one of access frequency, file size, and timestamp.

[0018] Optionally, the process of creating the symbolic link includes:

[0019] A symbolic link is created in the primary storage, the symbolic link pointing to the target file under the secondary storage path mapped by the dynamic symbolic link; the path structure of the symbolic link is consistent with the path structure of the dynamic symbolic link.

[0020] Optionally, when accessing the symbolic link in the primary storage, the client parses the symbolic link through a file system interface and accesses the actual file in the secondary storage according to the current pointing of the dynamic symbolic link.

[0021] To achieve the above objectives, a second embodiment of the present application provides a system supporting transparent access to data archives, including:

[0022] The client device is used to mount the shared directories of the primary storage and the secondary storage and create a dynamic symbolic link pointing to the secondary storage mount point;

[0023] a migration tool module, connected to the client device, for migrating files from the primary storage to the secondary storage according to a preset migration policy, and creating a symbolic link in the primary storage pointing to the file in the secondary storage;

[0024] a symbolic link management module, connected to the client device and the migration tool module, and configured to dynamically maintain the pointing direction of the dynamic symbolic link to adapt to changes in the secondary storage mount point path;

[0025] The file system interface module is used to respond to a user or application's access request to a file in the primary storage. If the file is a symbolic link, the module parses the symbolic link and accesses the actual file in the secondary storage based on the dynamic symbolic link.

[0026] Optionally, the migration tool module includes:

[0027] a hot and cold data identification unit, configured to determine whether a file should be migrated to secondary storage based on at least one of access frequency, file size, and timestamp;

[0028] The symbolic link generation unit is used to generate a symbolic link in the primary storage pointing to a target file in the secondary storage.

[0029] Optionally, the symbolic link management module includes:

[0030] Dynamic path configuration unit, used to configure dynamic symbolic links pointing to secondary storage mount points in the client;

[0031] A path updating unit is used to automatically update the pointing of the dynamic symbolic link when the mount point path changes, without modifying the paths of all symbolic links in the primary storage.

[0032] Optionally, the symbolic link management module includes:

[0033] Dynamic path configuration unit, used to configure dynamic symbolic links pointing to secondary storage mount points in the client;

[0034] A path updating unit is used to automatically update the pointing of the dynamic symbolic link when the mount point path changes, without modifying the paths of all symbolic links in the primary storage.

[0035] Optionally, the file system interface module supports cross-cluster access, allowing the client to access data in multiple storage clusters, and the path of the dynamic symbolic link can be configured to point to secondary storage mount points in different clusters.

[0036] Optionally, the client device includes:

[0037] The mount management unit is used to mount the shared directories of the primary storage and secondary storage to local paths respectively;

[0038] The access control unit is used to automatically resolve and access the actual file in the secondary storage when accessing the symbolic link in the primary storage.

[0039] To achieve the above-mentioned purpose, a third embodiment of the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0040] The memory stores computer-executable instructions;

[0041] The processor executes the computer-executable instructions stored in the memory to implement the method as described in any one of the first aspects.

[0042] To achieve the above-mentioned purpose, the fourth embodiment of the present application proposes a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed by a processor, they are used to implement the method as described in any one of the first aspects.

[0043] To achieve the above-mentioned objectives, the fifth embodiment of the present application proposes a computer program product, which implements any one of the methods in the first aspect when executed by a processor.

[0044] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0046] Figure 1 A flowchart of a method for supporting transparent access to data archives provided in an embodiment of the present application;

[0047] Figure 2A schematic diagram of the system architecture of a method for supporting transparent access to data archiving provided by an embodiment of the present application;

[0048] Figure 3 A flowchart of a method for supporting transparent access to data archiving provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] The following describes in detail embodiments of the present application, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0050] like Figure 1 、 Figure 2 and Figure 3 As shown, the present invention provides a method for supporting transparent access to data archives, the core of which is to achieve dynamic access across storage levels through symbolic link technology. The method includes the following steps:

[0051] Step 101: Create a first mount directory and a second mount directory on the client, wherein the first mount directory mounts a shared directory of the primary storage, and the second mount directory mounts a shared directory of the secondary storage.

[0052] In the embodiment of the present application, the client first needs to create two mount directories and mount the shared directories of the primary storage and secondary storage respectively. Specifically, the client performs the following steps:

[0053] (1) Create two directories on the client system: / mnt / tier1client and / mnt / tier2client. These two directories are used to mount the shared directories of the primary storage and secondary storage, respectively.

[0054] (2) Mount the shared directory / share / tier1storage on the tier-1 storage to the client's / mnt / tier1client directory. The client can now access files and data on the tier-1 storage.

[0055] (3) At the same time, mount the shared directory / share / tier2storage on the secondary storage to the client's / mnt / tier2client directory, so that the client can access the files in the secondary storage.

[0056] This mount configuration allows clients to access data on both primary and secondary storage simultaneously. When a user or application needs to access data, it can be transparently retrieved from both storage tiers, ensuring that file access is unaffected by the storage hierarchy. This allows clients to access file data on both primary and secondary storage simultaneously. For example, a user can access files stored on primary storage through the / mnt / tier1client directory and archive files stored on secondary storage through the / mnt / tier2client directory.

[0057] The implementation of this step ensures that the client can easily access data in different storage levels, laying the foundation for symbolic link creation and transparent data access in subsequent steps.

[0058] Step 102: Create a dynamic symbolic link pointing to the secondary storage mount point in the client. The direction of the dynamic symbolic link can be dynamically adjusted as the mount point path changes.

[0059] In this embodiment of the present application, the client needs to create a dynamic symbolic link that points to the mount point of the secondary storage. The direction of the symbolic link is dynamic and can be adjusted according to actual needs and changes in the storage environment. The specific steps are as follows:

[0060] In the client's local file system, a symbolic link is created that points to the mount point path of the secondary storage. This path points to the actual data storage location on the secondary storage. Because different clients or storage clusters may use different path names, the symbolic link's location can be flexibly adjusted and does not need to be fixed to a specific path. When the mount point path needs to be modified, simply change the symbolic link's location, eliminating the need to manually modify each storage node, thus improving management convenience.

[0061] Furthermore, the paths of created dynamic symbolic links can be dynamically updated through a unified management method. For example, the symbolic link / mnt / tier2mountlink created on the client can point to the mount point / mnt / tier2client on the secondary storage. The symbolic link's location can be adjusted as needed in different environments.

[0062] As a possible implementation, assume that the following dynamic symbolic link is created on the client (where Apps & Users resides): / mnt / tier2mountlink-> / mnt / tier2client. In this example, / mnt / tier2mountlink is a dynamic symbolic link created on the client, pointing to the secondary storage mount point / mnt / tier2client. Note that the path / mnt / tier2client to which the symbolic link points is not fixed and can change dynamically based on actual conditions. For example, if the storage path changes, the client administrator only needs to update the symbolic link, without having to modify each file or storage node.

[0063] Therefore, when in use, clients can transparently access data on secondary storage by accessing / mnt / tier2mountlink, without being affected by path changes. This flexibility allows the system to adapt to different storage architectures and avoids the management complexity brought by fixed paths.

[0064] By creating and using dynamic symbolic links, this embodiment eliminates the need for manual management of individual files and storage nodes, simplifying storage system maintenance. Dynamic symbolic links can be flexibly adjusted to support a variety of storage clusters and client environments, improving system flexibility and scalability while reducing management costs associated with path changes.

[0065] Step 103: When migrating the target file from the primary storage to the secondary storage using the migration tool, a symbolic link of the target file is created on the primary storage.

[0066] In this embodiment of the present application, the migration tool is responsible for migrating files from primary storage to secondary storage and creating symbolic links on primary storage to point to the migrated files. This process involves multiple steps to ensure that files can be transparently accessed from primary storage to secondary storage. The specific steps are as follows:

[0067] The migration tool migrates files from primary storage to secondary storage according to pre-defined migration policies. Migration policies can be based on various criteria, such as file access frequency, file size, or file timestamp. Based on these policies, the migration tool automatically determines which files to migrate and moves them to secondary storage.

[0068] While migrating files, the migration tool also creates a symbolic link on primary storage that points to the target file's location on secondary storage. The path structure of the created symbolic link is consistent with the path structure of a dynamic symbolic link. For example, the symbolic link points to the file path under the secondary storage mount point.

[0069] It should be noted that the creation of symbolic links in the primary storage ensures that users can transparently access files migrated to the secondary storage through symbolic links when accessing the primary storage. The direction of the symbolic link depends on the dynamic symbolic link created previously, which is dynamically mapped to the actual path of the secondary storage.

[0070] Suppose a user creates a file named file1 on tier-1 storage. When the file is migrated, the migration tool migrates file1 from tier-1 storage to tier-2 storage according to the pre-set policy. Simultaneously, the migration tool creates a symbolic link for the file in the / share / tier1storage directory on tier-1 storage, pointing to the file path on tier-2 storage. For example, a symbolic link is created: file1-> / mnt / tier2mountlink / file1.

[0071] In this example, the symbolic link file1 points to / mnt / tier2mountlink / file1 on the secondary storage. / mnt / tier2mountlink is a previously created dynamic symbolic link that points to the actual storage location on the secondary storage. This way, when users access file1 on the primary storage, they automatically access the file on the secondary storage through the symbolic link, without having to worry about the physical storage location of the file.

[0072] This step makes the migration process transparent to users. Users don't need to manually adjust file paths; symbolic links ensure continuous and transparent data access. Furthermore, the migration tool can flexibly migrate files based on various policies, optimizing storage resource utilization. The combination of dynamic and symbolic links ensures efficient and seamless integration between primary and secondary storage.

[0073] Step 104, when a user or application accesses a file in the primary storage, if the file is a symbolic link, the actual path of the target file in the secondary storage is parsed based on the symbolic link, and the target file in the secondary storage is accessed through the dynamic symbolic link.

[0074] In an embodiment of the present application, the client accesses the symbolic link in the primary storage through the file system interface, and transparently accesses the actual file stored in the secondary storage based on the path information pointed to by the symbolic link.

[0075] When a user or application requests access to a file in the primary storage from a client, the embodiment of the present application first determines whether the file is a symbolic link. If the file is a symbolic link, the actual path of the target file in the secondary storage needs to be parsed through the symbolic link.

[0076] Next, the client parses the symbolic link through the file system interface and obtains the target file path pointed to by the symbolic link. Since the symbolic link points to a file in the secondary storage, the client needs to further access the corresponding file in the secondary storage based on the path.

[0077] It's important to note that the path pointed to by a symbolic link is managed using a dynamic symbolic link. Dynamic symbolic links automatically adjust their location based on changes in the mount point, ensuring that clients can always access the correct file on secondary storage. Regardless of how the mount point path changes, dynamic symbolic links always provide the correct target file location.

[0078] After the client resolves the symbolic link and obtains the actual file path in the secondary storage, it directly initiates a read request to the secondary storage device. Because the symbolic link's direction has been adjusted through dynamic symbolic links, the client can transparently access the target file in the secondary storage without the user noticing that the actual file storage location has changed.

[0079] For example, suppose a user or application attempts to read file file1 on primary storage. On primary storage, file1 is a symbolic link pointing to the file path / mnt / tier2mountlink / file1 on secondary storage. The client resolves the symbolic link using the file system interface to determine the actual location of the file on secondary storage. The client initiates a read request to the secondary storage path / mnt / tier2mountlink / file1. The data is returned directly from secondary storage to the client, and the user experiences the same file access as on primary storage. In this case, the client does not need to know the physical storage location of the file; the entire access process is transparent to the user.

[0080] This step allows clients to transparently access files migrated to secondary storage without being aware of changes to the storage hierarchy. The combination of symbolic links and dynamic symbolic links maximizes storage flexibility and transparency, allowing users and applications to access data in secondary storage directly, just as they would access files in primary storage, achieving efficient data storage and access management.

[0081] To implement the above embodiment, the present application also proposes a system supporting transparent access to data archives, including:

[0082] The client device is used to mount the shared directories of the primary storage and the secondary storage and create a dynamic symbolic link pointing to the secondary storage mount point;

[0083] a migration tool module, connected to the client device, for migrating files from the primary storage to the secondary storage according to a preset migration policy, and creating a symbolic link in the primary storage pointing to the file in the secondary storage;

[0084] a symbolic link management module, connected to the client device and the migration tool module, and configured to dynamically maintain the pointing direction of the dynamic symbolic link to adapt to changes in the secondary storage mount point path;

[0085] The file system interface module is used to respond to a user or application's access request to a file in the primary storage. If the file is a symbolic link, the module parses the symbolic link and accesses the actual file in the secondary storage based on the dynamic symbolic link.

[0086] Optionally, the migration tool module includes:

[0087] a hot and cold data identification unit, configured to determine whether a file should be migrated to secondary storage based on at least one of access frequency, file size, and timestamp;

[0088] The symbolic link generation unit is used to generate a symbolic link in the primary storage pointing to a target file in the secondary storage.

[0089] Optionally, the symbolic link management module includes:

[0090] Dynamic path configuration unit, used to configure dynamic symbolic links pointing to secondary storage mount points in the client;

[0091] A path updating unit is used to automatically update the pointing of the dynamic symbolic link when the mount point path changes.

[0092] Optionally, the file system interface module supports cross-cluster access, allowing the client to access data in multiple storage clusters, and the path of the dynamic symbolic link can be configured to point to secondary storage mount points in different clusters.

[0093] Optionally, the client device includes:

[0094] The mount management unit is used to mount the shared directories of the primary storage and secondary storage to local paths respectively;

[0095] The access control unit is used to automatically resolve and access the actual file in the secondary storage when accessing the symbolic link in the primary storage.

[0096] Regarding the apparatus in the above embodiment, the specific manner in which the various modules and units perform operations has been described in detail in the embodiment of the method, and will not be elaborated on here.

[0097] In order to implement the above embodiments, the present application also proposes an electronic device, comprising: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the method provided by the above embodiments.

[0098] In order to implement the above embodiments, the present application also proposes a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the methods provided by the above embodiments.

[0099] In order to implement the above embodiments, the present application also proposes a computer program product, including a computer program, which implements the methods provided by the above embodiments when executed by a processor.

[0100] The collection, storage, use, processing, transmission, provision and disclosure of user personal information involved in this application are in compliance with relevant laws and regulations and do not violate public order and good morals.

[0101] It is important to note that personal information collected from users should be used for legitimate and reasonable purposes and should not be shared or sold beyond these legitimate uses. Furthermore, such collection / sharing should be conducted only after receiving the user's informed consent, including but not limited to notifying the user to read the user agreement / user notice and sign an agreement / authorization that includes the relevant user information before using the feature. Furthermore, any necessary steps must be taken to safeguard and secure access to such personal information and ensure that others with access to personal information comply with its privacy policy and procedures.

[0102] This application contemplates providing implementations that allow users to selectively block the use or access of personal information data. Specifically, this disclosure contemplates providing hardware and / or software to prevent or block access to such personal information data. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. Furthermore, where applicable, such personal information can be de-identified to protect user privacy.

[0103] In the descriptions of the foregoing embodiments, the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" mean that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, unless they are mutually inconsistent.

[0104] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of the technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of such features. Throughout the description of this application, "plurality" means at least two, for example, two, three, etc., unless otherwise specifically defined.

[0105] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may be performed out of the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present application belong.

[0106] The logic and / or steps represented in the flowcharts or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing the logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (e.g., a computer-based system, a system including a processor, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device). For purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include the following: an electrical connection with one or more wires (electronic devices), a portable computer disk cartridge (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and programmable read-only memory (EPROM or flash memory), fiber optic devices, and a portable compact disc read-only memory (CDROM). Furthermore, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing it in another suitable manner if necessary, and then storing it in a computer memory.

[0107] It should be understood that various parts of the present application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used to implement: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0108] Those skilled in the art will understand that all or part of the steps in the method of the above embodiment can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0109] In addition, the functional units in the various embodiments of the present application may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into a module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0110] The storage medium mentioned above may be a read-only memory, a magnetic disk, or an optical disk, etc. Although the embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application. Persons skilled in the art may make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present application.

[0111] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this application can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of this application can be achieved. This is not limited herein.

[0112] The above specific embodiments do not constitute a limitation on the scope of protection of this application. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application shall be included within the scope of protection of this application.

Claims

1. A method for supporting transparent access to data archives, characterized in that: The following steps are involved: Create a first mount directory and a second mount directory on the client, where the first mount directory is mounted to the shared directory of the primary storage, and the second mount directory is mounted to the shared directory of the secondary storage; Creating a dynamic symbolic link pointing to the secondary storage mount point in the client, where the direction of the dynamic symbolic link can be dynamically adjusted as the mount point path changes; When migrating a target file from primary storage to secondary storage using the migration tool, a symbolic link of the target file is created on the primary storage; When a user or application accesses a file in the primary storage, if the file is a symbolic link, the actual path of the target file in the secondary storage is parsed based on the symbolic link, and the target file in the secondary storage is accessed through the dynamic symbolic link.

2. The method according to claim 1, wherein The process of creating the dynamic symbolic link includes: A dynamic symbolic link is created in the client's local file system, and the dynamic symbolic link points to the mount point path of the secondary storage; the mount point path is configured as different path names in different clients or different storage clusters, and the pointing of the dynamic symbolic link can be uniformly managed and dynamically updated.

3. The method according to claim 2, wherein The migration tool migrates the target file from the primary storage to the secondary storage according to a preset migration strategy, wherein the migration strategy is determined based on at least one of access frequency, file size, and timestamp.

4. The method according to claim 3, wherein The process of creating the symbolic link includes: A symbolic link is created in the primary storage, the symbolic link pointing to the target file under the secondary storage path mapped by the dynamic symbolic link; the path structure of the symbolic link is consistent with the path structure of the dynamic symbolic link.

5. The method according to claim 4, wherein When accessing the symbolic link in the primary storage, the client parses the symbolic link through the file system interface and accesses the actual file in the secondary storage according to the current pointing of the dynamic symbolic link.

6. A system supporting transparent access to data archives, characterized in that: include: The client device is used to mount the shared directories of the primary storage and the secondary storage and create a dynamic symbolic link pointing to the secondary storage mount point; a migration tool module, connected to the client device, for migrating files from the primary storage to the secondary storage according to a preset migration policy, and creating a symbolic link in the primary storage pointing to the file in the secondary storage; a symbolic link management module, connected to the client device and the migration tool module, and configured to dynamically maintain the pointing direction of the dynamic symbolic link to adapt to changes in the secondary storage mount point path; The file system interface module is used to respond to a user or application's access request to a file in the primary storage. If the file is a symbolic link, the module parses the symbolic link and accesses the actual file in the secondary storage based on the dynamic symbolic link.

7. The system according to claim 6, wherein: The migration tool module includes: a hot and cold data identification unit, configured to determine whether a file should be migrated to secondary storage based on at least one of access frequency, file size, and timestamp; The symbolic link generation unit is used to generate a symbolic link in the primary storage pointing to a target file in the secondary storage.

8. The system according to claim 7, wherein: The symbolic link management module includes: Dynamic path configuration unit, used to configure dynamic symbolic links pointing to secondary storage mount points in the client; A path updating unit is used to automatically update the pointing of the dynamic symbolic link when the mount point path changes.

9. The system according to claim 8, wherein The file system interface module supports cross-cluster access, allowing clients to access data in multiple storage clusters, and the path of the dynamic symbolic link can be configured to point to secondary storage mount points in different clusters.

10. The system according to claim 9, wherein: The client device includes: The mount management unit is used to mount the shared directories of the primary storage and secondary storage to local paths respectively; The access control unit is used to automatically resolve and access the actual file in the secondary storage when accessing the symbolic link in the primary storage.

11. An electronic device, characterized in that: include: a processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 5.

12. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 5 when executed by a processor.

13. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 5 when executed by a processor.

Images