HK1173870B - Method and system for storage device migration and redirection - Google Patents
Method and system for storage device migration and redirection Download PDFInfo
- Publication number
- HK1173870B HK1173870B HK13100905.9A HK13100905A HK1173870B HK 1173870 B HK1173870 B HK 1173870B HK 13100905 A HK13100905 A HK 13100905A HK 1173870 B HK1173870 B HK 1173870B
- Authority
- HK
- Hong Kong
- Prior art keywords
- storage device
- network
- client
- file
- storage
- Prior art date
Links
Description
Technical Field
The present invention relates to storage technology, and more particularly, to storage device migration and redirection.
Background
Many computer systems and networks have grown over time. In a business setting, documents may be generated as a business process progresses. In a home network setting, a user may generate a digital image or digital video of the consumable storage space. When storage space is exhausted, a user may add additional storage devices, such as a universal serial bus hard disk, additional hard disks, or other storage devices.
Disclosure of Invention
The network storage system may receive content of a storage device attached to a client device of the network storage system, and access to the content may then be redirected to the network storage system on the client device. The storage device may then be removed or repurposed. In embodiments, storage device management may be performed by a client device or a network storage system. The system may use policies to define under what circumstances the contents of the storage device may be moved to the network storage system, or the operation may be initiated by the user. The system may also retain any access permissions or other metadata associated with the files on the original storage device.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
Drawings
In the drawings:
FIG. 1 is a diagram illustration of an embodiment showing a system with a network attached storage mechanism.
FIG. 2 is a flowchart illustration of an embodiment showing a method for managing storage devices.
FIG. 3 is a flowchart illustration of an embodiment showing a method for reconnecting a storage device.
Detailed Description
The network storage device may receive files from a local storage device attached to the client device. The network storage device may store all files contained in the local storage device and then add a redirection mechanism on the client device to point to the network storage device.
The network storage device may serve as a mechanism to consolidate the various local storage devices on the client devices. For example, a user may have one or more attached hard disk storage devices connected through a Universal Serial Bus (USB) connection. The network storage device may move all data from the various hard disk devices and then create a link or other redirection mechanism so that the user may access the same data in the same manner, except that the data is stored on the network storage device rather than on the previous storage device.
The network storage device may incorporate local storage from multiple client devices. Each migrated client storage device may be migrated in such a way that: the full access permission may be maintained. Although all of the data is located on the network storage device, each client device may access their own data and may not access data associated with other client devices.
The network storage device may provide various data protection services, such as backup services, mirroring or replication services, or other functions that may protect data.
Throughout the description of the drawings, like reference numerals refer to like elements throughout.
When elements are referred to as being "connected" or "coupled," the elements can be directly connected or coupled together or one or more intervening elements may also be present. In contrast, when elements are referred to as being "directly connected" or "directly coupled," there are no intervening elements present.
The present subject matter may be embodied as devices, systems, methods, and/or computer program products. Accordingly, some or all of the inventive subject matter may be embodied in hardware and/or in software (including firmware, resident software, micro-code, state machines, gate arrays, etc.). Furthermore, the present subject matter may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media.
Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by an instruction execution system. Note that the computer-usable or computer-readable medium could be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other suitable medium, then compiled, interpreted, of otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal" may be defined as a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
When the subject matter is embodied in the general context of computer-executable instructions, the embodiment may comprise program modules, executed by one or more systems, computers, or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically, the functionality of the program modules may be combined or distributed as desired in various embodiments.
FIG. 1 is a diagram of an embodiment 100, illustrating a system including a storage device manager. Embodiment 100 is a simplified example of a local computer system with a local network storage device.
The diagram of fig. 1 shows the functional components of the system. In some cases, a component may be a hardware component, a software component, or a combination of hardware and software. Some components may be application level software, while other components may be operating system level components. In some cases, the connection of one component to another component may be a tight connection, where two or more components operate on a single hardware platform. In other cases, the connection may be made over a network connection that spans a long distance. Various embodiments may use different hardware, software, and interconnect architectures to achieve the described functionality.
Embodiment 100 may represent a conventional computer device having various local storage devices. In a typical usage scenario, a user may have a home computer and may purchase a digital camera. The user may start taking a picture and may quickly fill up the hard disk or other storage device on the home computer with the picture file. Due to the lack of storage space, the user may then purchase a hard disk or other storage device that may be attached through a Universal Serial Bus (USB) connection. Over time, the first USB storage device may become full, so another may be added.
In this scenario, each storage device may be accessed through a file system on the home computer. In some cases, the storage devices may be accessed through a drive name such as "c: \", or as a directory or device within the file system. At some point in the scenario, a user may purchase a network storage device having a large amount of storage capacity. The contents of the USB storage device may be moved to the network storage device and the file system of the home computer may redirect any calls directed to the USB storage device instead to the network storage device. In many embodiments, a user may access the file system by using a file system browser.
In some embodiments, the transfer and redirection of the file may occur without any user intervention. In one such embodiment, the network storage device may detect storage on the client system, move files, and redirect requests to the network storage device on an automated basis. A set of policies may define conditions under which the contents of a locally attached storage device may be moved to a network storage device.
The file transfer and redirection process may be performed on a removable storage device. In some embodiments, a storage device may be hot-dockable, meaning that the storage device may be added or removed while the client system is operational. Some embodiments may perform file transfers only on removable storage devices and not on fixed storage devices.
Examples of removable storage devices may include various solid state and hard disk storage devices. For example, a USB connection may be used to removably connect a hard disk storage device. In another example, solid state storage devices such as those used in cameras, cell phones, and other devices may be used. The removable storage device may include any type of computer storage media.
The file transfer and redirection process may be initiated by a user. For example, the application may give the user a choice to select one or more storage devices to migrate to the network storage device. In one such embodiment, the user may be able to select a local storage device from the graphical user interface and right click or perform other operations to bring up a menu option from which the file transfer and redirection process may begin.
In some embodiments, files on the storage device may be made unavailable during the file transfer process. In such embodiments, the storage device may be hidden or may be locked from access. Such an embodiment may check to determine that all files on the storage device are not being accessed by any application prior to the transfer.
The file transfer process may transfer the entire contents of the storage device. In some embodiments, the file migration process may be a bitwise copy of the storage device, where all information on the storage device may be copied on the network storage device. Such an embodiment may copy every detail of the storage device onto the network storage device. Such embodiments may be useful where hidden files, metadata, or other information related to invisible files may be transferred.
In other embodiments, the file transfer process may be a file-by-file transfer process. In such embodiments, each file may be transferred separately and may be recreated on the network storage device. Such an embodiment may be useful in situations where no invisible file-related information is available on the network storage device. Other such embodiments may be useful in situations where the file system of the storage device may be different from the file system of the network storage device. For example, some small solid-state storage devices used in cameras, cell phones, video cameras, or other devices may use one format to store files on the device and a second format to store on a network storage device.
The file transfer process may retain permissions and other metadata about the file. The permissions may be access permissions that define read, write, and other access restrictions. In some cases, the access permissions may define private permissions for different users.
In some embodiments, the network storage device may create a virtual hard disk on which to store the files transferred from the local storage device. The virtual hard disk may be an extensible virtual hard disk that may be expanded in size to accommodate additional files once the local storage device is near capacity. In such embodiments, the extensible virtual hard disk may allow the user to continue to place files in the same directory as for the local storage device, but without the storage limitations of the local storage device.
After the file is moved from the local storage device to the network storage device, a redirection mechanism may be placed within the local storage system to redirect any further read and write operations to the network storage device. In some embodiments, the redirection mechanism may be transparent to a user or application that may access the file.
In some embodiments, the removable storage device may be accessed through a file system on the local device. A file system may be a set of directories or folders through which various types of files may be organized and accessed. In some cases, files in the removable storage device may be accessed within the file system as folders or subfolders. In such embodiments, the redirection mechanism may redirect access requests for the contents of the folder to the volume on the network storage device containing the file.
In some embodiments, the local storage device may be accessed by a drive name. When the contents of the local storage device are moved to the network storage device, the drive name indicator may be mapped or redirected to a corresponding volume on the network storage device.
The network storage device may create a new logical volume for each storage device that may be moved. The network storage device may also create a name for each volume. In some embodiments, the name may be created from metadata derived from the local storage device. For example, the volume name on the network storage device may be generated using the manufacturer and model number of the local storage device.
A network storage device may provide storage services to multiple client devices. For each client device, one or more volumes may be created to store files on the local device, and then the respective client device may access the volumes over the network connection. In many embodiments, the network storage device may serve multiple client devices simultaneously and in parallel. When multiple client devices are serviced in parallel, each volume may be made available only to the client device for which it was created. In some such embodiments, the network storage device may allow an administrator to access all of the storage volumes on the network storage device.
The network storage device may have additional services such as backup, data redundancy, data consolidation, and other services that may be performed on the various volumes stored on the network storage device.
In some embodiments, the backup system may store a copy of the stored data in another location or on another device. The backup system may operate on all volumes stored on the network storage device or on a subset of the volumes. In some embodiments, a user may be able to specify individual volumes for different types of backup operations. For example, a user may be able to identify some volumes for one type of backup and other volumes for a different type of backup. In some embodiments, backup settings may change for a complete volume, a folder or directory within a volume, for all data associated with a client device, or globally for all volumes including volumes from multiple storage devices.
One type of backup operation may be a cloud-based backup. Cloud-based backups may have backup storage that is accessible through the internet or other network connection. In many cases, the cloud-based backup may be a remote backup in which the backup storage may be remote from the site.
Another type of backup operation may be a local backup and may use tape backup, optical storage, hard disk storage, or other storage mechanisms to store a second copy of some or all of the data.
The network storage device may provide data redundancy for some or all of the volumes. Data redundancy may place the data of a volume on two or more different storage devices within a network storage device. Data redundancy can minimize the risk of losing data if one of the storage devices (such as a hard disk) within a network storage device fails.
In some embodiments, the data redundancy settings may change for a complete volume, a folder or directory within a volume, for all data associated with a client device, or globally for all volumes including volumes from multiple storage devices.
Data consolidation may deduplicate information or compress data within volumes or between volumes. One mechanism for deduplication may be to identify identical data chunks and remove one of the data chunks from storage, free the chunk, and compress the overall size of the data on the network storage device. In some embodiments, a hash function may be performed on the data chunks to compare the data chunks and identify duplicates.
Data consolidation may be performed for multiple volumes. By comparing different volumes and removing duplicate blocks between volumes, a greater amount of space may be saved on the network storage device. In some such embodiments, volumes from one client may be compressed using volumes from other clients. Overall compression of the network storage device may be performed while maintaining access permissions and logical isolation between different volumes of different clients.
The network storage device may provide other services with respect to the data, including encryption, virus scanning, data integrity checking, or other services. In some embodiments, various services may change for a complete volume, a folder or directory within a volume, for all data associated with a client device, or globally for all volumes including volumes from multiple storage devices.
Client device 102 is shown having a hardware component 104 and a software component 106. The illustrated client device 102 represents a conventional computing device, but other embodiments may have different configurations, architectures, or components.
In many embodiments, the client device 102 may be a personal computer or a code development workstation. The client device 102 may also be a server computer, desktop computer, or similar device. In some embodiments, client device 102 may still further be a laptop computer, a netbook computer, a tablet or slate computer, a wireless handheld device, a cellular telephone, or any other type of computing device.
The hardware components 104 may include a processor 108, random access memory 110, and non-volatile storage 112. The hardware components 104 may also include a user interface 114 and a network interface 116. In some embodiments, the processor 108 may be comprised of several processors or processor cores. The random access memory 110 may be a memory that is easily accessed and addressed by the processor 108. The non-volatile storage 112 may be storage that persists after the device 102 is turned off. The non-volatile storage 112 may be any type of storage device, including hard disks, solid state memory devices, magnetic cassettes, optical storage, or other types of storage. The non-volatile storage 112 may be read-only or read/write capable.
The user interface 114 may be any type of hardware capable of displaying output and receiving input from a user. In many cases, the output display may be a graphical display monitor, but the output devices may include lights and other visual outputs, audio outputs, powered actuator outputs, and other output devices. Conventional input devices may include a keyboard and a pointing device, such as a mouse, stylus, trackball, or other pointing device. Other input devices may include various sensors, including biometric input devices, audio and video input devices, and other sensors.
The network interface 116 may be any type of connection to another computer. In many embodiments, the network interface 116 may be a wired ethernet connection. Other embodiments may include wired or wireless connections based on various communication protocols.
The client device 102 may have one or more external storage devices 118. The external storage device 118 may be a hard disk, solid state storage device, optical storage device, or other storage device. In many cases, the external storage device 118 may be hot-pluggable or hot-pluggable, meaning that the storage device 118 may be added or removed while the device 102 is operational.
The software components 106 may include an operating system 120, and various applications 122 and services may operate on the operating system 120. The operating system may provide a layer of abstraction between executing routines and executing hardware components 104, and may include various routines and functions that communicate directly with the various hardware components.
The operating system 120 may have a file system 122. File system 122 may be a mechanism for accessing data on various hardware storage devices, including storage devices 112 and 118. The file system 122 may be used by the application 122 to locate executable files as well as data files, and to create, delete, modify, edit files, change file properties, and perform other functions on files.
In some embodiments, the operating system 120 may assign drive numbers to different physical or logical storage devices. In such embodiments, a drive number, directory, or other identifier within file system 122 may be assigned to the physical storage device.
Some storage devices may contain two or more logical volumes. Each logical volume may have a different identifier or location within the file system 122. In such a case, the process of moving the file and redirecting access to the network storage device may involve moving all of the logical volumes on the local storage device, such that the process of moving the file and redirecting access may result in the local storage device being released or available for re-determination purposes.
In some embodiments, the network attached storage client application 126 may reside on the client device 102. Client application 126 may communicate with network storage device 130 and coordinate the configuration of volume creation, file movement, and redirection mechanisms on network storage device 130. In some embodiments, most of the operations may be performed by the client application 126, while in other embodiments, the network storage device 130 may perform most of the operations.
The network attached storage client application 126 may use a set of policies 127 to define when and how file transfers and redirections may be performed the policies 127 may determine under what conditions file transfers and redirections may be performed. In such embodiments, the client application 126 may cause the file transfer and redirection operations to be performed without any user intervention. Such embodiments may trigger the execution of file transfer and redirection operations, for example, when the storage device may be approaching a certain capacity.
The network storage device 130 may be accessible to the client device 102 over the network 128.
The network storage device 130 may have a hardware platform 132, which hardware platform 132 may be similar to the hardware platform 104 of the device 102. The hardware platform 132 may include a processor, random access memory, and storage. In many cases, the hardware storage of the hardware platform 132 may include mirrored hard disks, Redundant Array of Independent Disks (RAID) configurations, and other configurations that may have a higher fault tolerance than conventional storage media.
The network storage device 130 may have an operating system 134 and a file system 136, and various applications may execute on the operating system 134.
The network attached storage manager application 138 may perform some or all of the tasks of detecting a storage device attached to a client device, creating a new volume, and transferring the contents of the storage device to the new volume. The manager application 138 may also cause a redirection mechanism to be configured on the client device.
In some embodiments, the operations of the manager application 138 may be performed using a client application. The client application 140 may be an executable application or service that may be downloaded to a client device, installed, and when executed may respond to commands and requests from the manager application 138.
The backup system 142 may reside on the network storage device 130 and may backup the stored content on the network storage device 130 in various ways. In some cases, backup system 140 may backup data onto a local device, such as a tape backup, an optical storage medium, or another backup storage device. In some cases, the backup system 140 may store the data on a cloud storage system 150, the cloud storage system 150 being accessible through the local area network 128, the gateway device 146, and a wide area network 148, the wide area network 148 may include the internet.
In some embodiments, network storage 130 may have an externally attached storage 144. The externally attached storage 144 may connect to the network storage 130 and act as a primary storage or as a backup storage.
In some embodiments, the external storage device 144 may be a storage device that is generally attached to the client device 102. In such an embodiment, the user may plug into storage device 144, and network attached storage management application 138 may detect storage device 144, create volumes, and transfer files from storage device 144. In such embodiments, the user may be presented with a user interface, command line, or other input mechanism by which the user may select a device associated with storage device 144. The redirection mechanism may then be configured on the client device to access the contents of storage device 144 through network storage device 130.
In such an embodiment, the user may manually disconnect the storage device from the client 102 and then reconnect the storage device to the network storage system 130. Such embodiments may enable faster transfer times because file transfers may be performed locally rather than over a network connection.
The network attached storage management application 138 may use a set of policies 137 that may define when and how file transfers and redirections may occur. The policy may define under what conditions file transfer and redirection procedures may be implemented, as well as configuration settings for how such procedures may be performed. In some cases, policy 137 may define under what conditions the file transfer and redirection process may be performed without user intervention.
FIG. 2 is a flowchart illustration of an embodiment 200 showing a method for managing storage devices. The process of embodiment 200 is a simplified example of a basic process for transferring files from a locally attached storage device, configuring a redirection mechanism, and for the purpose of re-determination of the storage device.
Other embodiments may use different ordering, additional or fewer steps, and different nomenclature or terminology to accomplish similar functions. In some embodiments, various operations or sets of operations may be performed in parallel with other operations, in a synchronous or asynchronous manner. The steps selected here are chosen to illustrate some of the principles of operation in a simplified form.
In block 202, a storage device may be connected to a local system. In block 204, a connection may be detected. After the connection, the local system may operate with the storage device in block 206.
In block 208, a condition for transferring the contents of the local storage device may be satisfied. In some embodiments, the policy may indicate when the content may be moved. In other embodiments, the user may indicate when the content may be moved.
In block 210, a new volume may be established on the network storage device. In some embodiments, the new volume may be a virtual hard disk, while in other embodiments a logical volume or other mechanism may be used to manage data stored on the storage device.
In block 212, a name may be created for the volume. In some embodiments, the volume name may be automatically generated. In other embodiments, the user may be able to enter or edit the volume name.
In block 214, the contents of the storage device are transferred to the newly created volume. In block 216, the local file system may be configured to redirect the request to the newly created volume.
In some embodiments, the contents of the local storage device may be erased in block 218. In block 220, the local storage device may be repurposed.
FIG. 3 is a flowchart illustration of an embodiment 300 showing a method for reconnecting a storage device. The process of embodiment 300 is a simplified example of a one-way synchronization method that may be performed when a storage device is reconnected to a client device.
Other embodiments may use different ordering, additional or fewer steps, and different nomenclature or terminology to accomplish similar functions. In some embodiments, various operations or sets of operations may be performed in parallel with other operations, in a synchronous or asynchronous manner. The steps selected here are chosen to illustrate some of the principles of operation in a simplified form.
Embodiment 300 is an example of a reconnect process that may be performed when a storage device is reconnected to a client device after a file transfer has been performed. Embodiment 300 may be performed where storage devices may have their contents erased or not erased.
In block 302, the storage device may be reconnected. In block 304, a storage device may be detected.
If no updates or changes have occurred on the storage device since the contents of the storage device were transferred to the network storage device in block 306, then access to the storage device is not permitted in block 308.
If there is an update or change on the storage device in block 306, the update may be identified in block 310 and transferred to the network storage device using a one-way synchronization mechanism in block 312. In a one-way synchronization system, changes or updates from the local storage system may be moved to the network storage system, but any changes made to the network storage system may not be moved back to the local storage system.
The foregoing description of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the subject matter to the precise form disclosed, and other modifications and variations may be possible in light of the above teachings. The embodiment was chosen and described in order to best explain the principles of the invention and its practical application, to thereby enable others skilled in the art to best utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the appended claims be construed to include other alternative embodiments except insofar as limited by the prior art.
Claims (19)
1. A method performed on a computer processor, the method comprising:
detecting a storage device physically attached to a client device, the storage device being accessed through a first access mechanism;
determining to move contents of the storage device to a network storage device, wherein the network storage device is communicatively coupled to and capable of providing storage services to a plurality of client devices via a computer network;
creating a volume on the network storage device, the created volume being logically separate from other volumes of other client devices of the plurality of client devices and the created volume being limited to being available to the client device;
moving the content from the storage device to the created volume on the network storage device to free the storage device for physical removal from the client device, wherein the moving the content includes identifying a first access permission on a first file on the storage device and causing the first access permission on the first file to be copied on the network storage device;
the first access mechanism is configured to redirect access requests to the storage device to the network storage device such that the content remains accessible to the client device after the storage device is physically removed from the client device.
2. The method of claim 1, wherein the first access mechanism is a drive number indicator within a file system.
3. The method of claim 1, wherein the first access mechanism is a directory.
4. The method of claim 1, wherein the determining is performed by identifying a current condition defined in a policy.
5. The method of claim 1, wherein the determining is performed by receiving a transfer request from a user.
6. The method of claim 5, wherein the transfer request is an option available to the user while browsing the storage device in a file browser.
7. The method of claim 1, further comprising:
creating a volume name for the storage device on the network storage device.
8. The method of claim 7, wherein the volume name comprises metadata derived from the storage device.
9. The method of claim 1, further comprising:
changing a first file in the content on the network storage device from the client device;
removing the storage device from the client device;
reconnecting the storage device to the client device;
detecting that the storage device is reconnected;
analyzing the storage device to determine that a second file within the content of the storage device has been added since the move; and
moving the second file to the network storage device.
10. The method of claim 9, further comprising:
the storage device is not updated with changes to the first file.
11. A system for migrating files, comprising:
a processor;
network connection;
a storage system;
network attached storage manager:
detecting a storage device physically attached to a client device, the storage device being accessed through a first access mechanism;
determining to move contents of the storage device to a network storage device, wherein the network storage device is communicatively coupled to and capable of providing storage services to a plurality of client devices via a computer network;
creating a volume on the network storage device, the created volume being logically separate from other volumes of other client devices of the plurality of client devices and the created volume being limited to being available to the client device;
moving the content from the storage device to the created volume on the network storage device to free the storage device for physical removal from the client device, wherein the moving the content includes identifying a first access permission on a first file on the storage device and causing the first access permission on the first file to be copied on the network storage device; and
causing the first access mechanism to redirect access requests to the storage device to the network storage device such that the content remains accessible to the client device after the storage device is physically removed from the client device.
12. The system of claim 11, wherein the storage system comprises a hot-pluggable storage device.
13. The system of claim 11, wherein the storage system comprises at least a portion of data on the storage system replicated on a plurality of storage devices.
14. The system of claim 11, further comprising:
and backing up the system.
15. The system of claim 11, further comprising:
a connection client downloadable to the client device, the connection client changing the first access mechanism to redirect the access request upon receiving a communication from the network attached storage manager.
16. The system of claim 11, wherein the client device is connected to the system through a wide area network connection.
17. A method performed on a computer processor, comprising:
detecting a storage device physically attached to a client device, the storage device being accessed through a directory structure within an operating system;
determining to move contents of the storage device to a network storage device, wherein the network storage device is communicatively coupled to and capable of providing storage services to a plurality of client devices via a computer network;
creating a volume on the network storage device, the created volume being logically separate from other volumes of other client devices of the plurality of client devices and the created volume being limited to being available to the client device;
moving the content from the storage device to the created volume on the network storage device to free the storage device for physical removal from the client device, wherein the moving the content includes identifying a first access permission on a first file on the storage device and causing the first access permission on the first file to be copied on the network storage device;
the directory structure is configured to redirect access requests to the storage device to the network storage device so that the content remains accessible to the client device after the storage device is physically removed from the client device.
18. The method of claim 17, further comprising:
erasing the content from the storage device after the moving.
19. The method of claim 18, further comprising:
detecting that the storage device is reconnected to the client device and identifying a first set of new files on the storage device; and
moving the first set of new files to the network storage device.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/972,541 US8627033B2 (en) | 2010-12-20 | 2010-12-20 | Storage device migration and redirection |
US12/972,541 | 2010-12-20 |
Publications (2)
Publication Number | Publication Date |
---|---|
HK1173870A1 HK1173870A1 (en) | 2013-05-24 |
HK1173870B true HK1173870B (en) | 2016-07-15 |
Family
ID=
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8627033B2 (en) | Storage device migration and redirection | |
US11989101B2 (en) | Data storage management system for multi-cloud protection, recovery, and migration of databases-as-a-service (DBAAS) and/or serverless database management systems (DBMS) | |
US11080232B2 (en) | Backup and restoration for a deduplicated file system | |
US10372547B1 (en) | Recovery-chain based retention for multi-tier data storage auto migration system | |
US8904137B1 (en) | Deduplication system space recycling through inode manipulation | |
US8473462B1 (en) | Change tracking for shared disks | |
EP2731013B1 (en) | Backing up method, device, and system for virtual machine | |
US12032542B2 (en) | Systems and methods for optimizing storage and retention of deduplicated secondary copies at storage platforms that are write-once read-many (WORM) enabled | |
CN108369487B (en) | System and method for taking snapshots in a deduplicated virtual file system | |
US10241870B1 (en) | Discovery operations using backup data | |
US9037541B2 (en) | Metadata for data storage array | |
CN115098299B (en) | Backup method, disaster recovery method, device and equipment of virtual machine | |
US10108635B2 (en) | Deduplication method and deduplication system using data association information | |
US10146637B1 (en) | Intelligent snapshot rollbacks | |
US9734156B1 (en) | Systems and methods for leveraging data-deduplication capabilities of file systems | |
US9749193B1 (en) | Rule-based systems for outcome-based data protection | |
CN113795827B (en) | Garbage Collection for Deduplication Cloud Tiering | |
US9251020B1 (en) | Systems and methods for file-level replication | |
US20240045770A1 (en) | Techniques for using data backup and disaster recovery configurations for application management | |
US8799223B1 (en) | Techniques for data backup management | |
JP2013543179A (en) | Recovery by item | |
US10496493B1 (en) | Method and system for restoring applications of particular point in time | |
US11500813B2 (en) | Instant replay of a file to a cloud tier on a deduplication file system | |
US9830471B1 (en) | Outcome-based data protection using multiple data protection systems | |
US10592527B1 (en) | Techniques for duplicating deduplicated data |