A network-attached storage (nas) device comprises an operational state comprising first system settings; a network interface configured to couple to a network and a processor coupled to the network interface. The processor may be configured to identify a nas configuration image stored on an externally accessible storage device, the nas configuration image comprising second system settings created from an other nas device on the network; determine that the nas configuration image is compatible with the nas device; receive a copy of the nas configuration image; compare the second system settings with the first system settings to identify compatible system settings, and modify the first system settings based on the compatible system settings.
|
1. A network-attached storage (nas) device, comprising:
an operational state comprising first system settings;
a network interface configured to couple to a network;
a processor coupled to the network interface, the processor being configured to:
receive, from the network interface, a communication identifying an externally accessible storage device that a) is accessible from the network and that b) stores a nas configuration image created by a second nas device and comprising second system settings;
access, over the network, the identified nas configuration image stored on the externally accessible storage device;
determine that the accessed nas configuration image is compatible with the nas device;
compare the second system settings with the first system settings to identify compatible system settings; and
modify the first system settings based on the compatible system settings.
17. A computer-implemented method for a network attached storage (nas) device to migrate from a first operational state comprising first system settings to a second operational state comprising second system settings, the method comprising:
receiving over a network interface coupled to a network, a communication identifying an externally accessible storage device that is a) accessible from the network and that b) stores a nas configuration image that was created by an other nas device and that comprises the second system settings;
accessing, over the network, the nas configuration image stored on the identified externally accessible storage device;
determining that the nas configuration image is compatible with the nas device;
receiving, over the network, a copy of the nas configuration image;
comparing the second system settings with the first system settings to identify compatible system settings; and
modifying the first system settings based on the compatible system settings.
8. A network-attached storage (nas) device, comprising:
a second operational state comprising second system settings;
a network interface configured to couple to a network, and
a processor coupled to the network interface, the processor being configured to:
identify an externally accessible storage device accessible from the network; and
create a nas configuration image of the nas device; and
send the created nas configuration image to the identified externally accessible storage device for storage thereon, the nas configuration image comprising the second system setting;
wherein the nas configuration image is operative to enable a second nas device comprising a first operational state that comprises first system settings to receive, from the network interface, a communication identifying the identified externally accessible storage device that
a) is accessible from the network and that
b) stores the nas configuration image
to access, over the network, the nas configuration image stored on the externally accessible storage device;
to determine that the accessed nas configuration image is compatible with the second nas device;
to compare the second system settings with the first system settings to identify compatible system settings; and
to modify the first system settings based on the compatible system settings.
2. The nas device of
a remote server accessible over a network;
a cloud computing environment;
a network share;
a remote nas device accessible over a network; and
a secondary storage device accessible from the network.
3. The nas device of
4. The nas device of
5. The nas device of
6. The nas device of
7. The nas device of
9. The nas device of
a remotely server accessible over a network;
a cloud computing environment;
a network share;
a remote nas device accessible over a network; and
a secondary storage device accessible from to the network.
10. The nas device of
11. The nas device of
12. The nas device of
13. The nas device of
14. The nas device of
15. The nas device of
16. The nas device of
18. The computer-implemented method of
a remotely server accessible over a network;
a cloud computing environment;
a network share;
a remote nas device accessible over a network; and
a secondary storage device accessible from the network.
19. The computer-implemented method of
20. The computer-implemented method of
21. The computer-implemented method of
22. The computer-implemented method of
23. The computer-implemented method of
|
Online remote backup utilities exist that manage the remote backup of selected files and directories. Such backup utilities include, for example, “Time Machine” by Apple, Inc. (creates incremental backups of files that can be selectively restored at a later date), “CrashPlan” by codefortytwo software (continuously sends encrypted data to online cloud storage), “Carbonite” (online remote backup), “Dropbox” (folder synchronized across connected devices), and “Mozy” (online remote backup and synchronized folder). However, such backup utilities are not configured for Network Attached Devices (NAS) and do not enable a NAS device to migrate from a first state to a second state.
The NAS device 100, according to one embodiment, may comprise and/or define an operational state. According to one embodiment, the operational state of the NAS device 100 may comprises user data 124 and system settings 126. The system settings 126 of the operational state of the NAS device 100 may comprise, according to one embodiment, NAS settings that define the functionality of the NAS device. The system settings 126 of the operational state of the NAS device 100 may also comprise, according to one embodiment, user settings. The user settings may comprise, for example, user access credentials such as usernames and passwords, and user application settings for third party software such as iTunes® settings, Flickr® settings, Gmail® settings, settings for DLNA-enabled devices and the like. The NAS settings may comprise, for example, settings that configure the NAS device 100 such as, for example, RAID settings, permissions, authorized users, backup and refresh schedules, data versioning settings and/or any settings that would be effective, whether singly or in combination, to define the state and functionality of the NAS device 100. The user data 124 may comprise user directory structures and may be configured to be stored in a non-compressed and non-encrypted format that is readily accessible and readable by suitable user applications. Such user data 124 and system settings 126 are collectively and non-exclusively referred to herein as “operational state” and constitute a snapshot of the NAS device 100 as of the point in time at which the NAS configuration image 122 was created.
The NAS device 100 may also include one or more network interfaces 106, configured to enable the NAS device 100 to access one or more networks. For example, the network interface 106 of the NAS device 100 may be configured to enable the NAS device 100 to access the Internet, a Local Area Network (LAN), a Wide Area Network (WAN), a cloud computing environment 110, a remote NAS device 112, a network share 114, a personal computer 118 and/or a tablet 120. The NAS device 100 may also couple to a USB-connected device, such as a USB storage device 116. The NAS device 100 may also be configured to access any other external devices and/or services directly (e.g., locally) or indirectly coupled thereto, such as collectively suggested at reference 118 in
According to one embodiment, the processor(s) 104 may be configured to identify a NAS configuration image stored on an externally accessible storage device. This identification may comprise discovering available externally accessible storage devices. NAS configuration images 122 may be stored on and/or retrieved from any locally coupled externally accessible storage device as shown at 128, or from any storage device coupled to the network. Moreover, such externally accessible storage devices may comprise a USB storage device 116 coupled to the NAS device 100 and/or some other storage device that is otherwise accessible to the NAS device 100 over a network, such as another NAS device 112, a network share 114 or a cloud computing and storage environment, as shown at 110. The processor 104 of the NAS device 100 may (before or after the identification of the externally accessible storage device) create a NAS configuration image 122 of the NAS device 100 and thereafter store the created NAS configuration image 122 on one or more selected externally accessible storage device or media. That is, the created NAS configuration image 122 may be stored on any externally accessible storage device such as, for example, a remote server, a USB storage device 116, a network share 114, a remote cloud computing and storage environment 110, a locally connected storage device 128 and/or even on another NAS device, such as shown at 112 in
For illustrative purposes, the following assumes that the NAS device 112 is the other NAS device that is enabled, by the created and stored NAS configuration image 122, to migrate from its first operational to the operational state of the NAS device 100, which NAS device has created and stored a NAS configuration image on any one of the externally accessible storage devices shown in
The created and stored NAS configuration image 122 may be configured as a one-time NAS configuration image or updated or refreshed by the NAS device 100 over time. For example, the processor 104 may cause the NAS configuration image 122 stored on the externally accessible storage device to be updated, either through the creation and storage of an entirely new NAS configuration image 122 or through an incremental update process, through which only changed portions of the NAS configuration image 122 are updated.
According to one embodiment, the processor 104 of the NAS device 100 may be configured to create and store a plurality of versions of the NAS configuration image 122 on the externally accessible storage device or devices.
According to one embodiment, the NAS configuration image or NAS configuration to images 122 having been thus created, the NAS device 112 may be directed and configured to determine whether the NAS configuration image created by NAS device 100 is compatible with the NAS device 112. Assuming that the NAS configuration image is, in fact, compatible with the NAS device 112, the NAS device 112 may receive or otherwise access a copy of the stored NAS configuration image from the or a selected externally accessible storage device where the NAS configuration image 122 is stored. The system settings stored in the received copy of the NAS configuration image may then be compared to the system settings of the NAS device 112 to identify compatible system settings. Assuming that at least some of the system settings stored in the received copy of the NAS configuration image are compatible with the system settings of the NAS device 112, the system settings of the NAS device 112 may be modified based on the compatible system settings, to enable the NAS device 112 to migrate (e.g., re-configure itself) from its current operational state to an operational state defined by the received or otherwise accessed copy of the NAS configuration image 122.
In detail, the NAS device 112 may comprise or define a first operational state. The first operational state may (but need not) comprise system settings that comprise NAS settings and user data. The system settings may comprise user settings and/or NAS settings. In the case in which the NAS device 112 is a factory-fresh NAS device, there may not be any user data or user settings stored therein. Moreover, the NAS settings of the first operational state of the NAS device 112 may be the NAS settings of a factory fresh NAS device. As does the NAS device 100, the NAS device 112 may include a network interface configured to couple to a network. The NAS device 112 may be coupled, through its network interface, to the same and/or other externally accessible storage device as is the NAS device 100. The NAS device 112 may also comprise one or more processors coupled to the network interface of the NAS device 112. According to one embodiment, such a processor or processors may be configured to carry out the functionality described above to migrate from a first operational state to a second operational state. In so doing, the NAS device 112 may receive a communication that identifies at least a storage device that is accessible over the network and that stores the NAS configuration image 122 that comprises an operational state of the NAS device (such as NAS device 100) having created the NAS configuration image 122. For exemplary purposes only, and with continued reference to
The NAS device 112 may then migrate, based on the received NAS configuration image 122, from the first operational state (e.g., its current operational state, whatever that may be) to a second operational state, which may be a state that is the same or similar to the operational state of the NAS device 100 having created the NAS configuration image, as of the date and time at which the NAS configuration image 122 was created. To do so, the NAS device 112 may compare the system settings of the received copy of the NAS configuration image 122 with the system settings of its current operational state to identify compatible system settings. Such compatible system settings may comprise both compatible NAS settings and compatible user settings. To migrate from its current operational state to the operational state of the NAS device 100 having created the NAS configuration image, the NAS device 112 may modify its current system settings based on the identified compatible system settings. Such modifications may take the form of replacing the current system settings of the NAS device 112 with the identified compatible system settings. The first operational state of the NAS device 112 may, in like manner be saved on an externally accessible storage device, to enable the NAS device 112 to return to that first operational state, if such becomes desirable.
The NAS device 112 may then be configured according to the system settings in the received NAS configuration image 122 such that, functionally and logically, it assumes the operational state of the NAS device 100 or an operational state that is similar thereto, as of the date and time at which the NAS configuration image 122 was created. As the NAS configuration image 122 may also comprise user data 124, the migrated NAS device 112 may not only be configured according to the system settings 126 of the NAS device 100 that created the NAS configuration image 122, but may also comprise the user data 124 of the NAS device 100, as of the time when the NAS configuration image 122 was created. The thus migrated and configured NAS device 112 may then store the same user data or a subset of the data of the NAS device 100 did as of the date and time it created the NAS configuration image 122 and be configured and operate as did or similarly to the NAS device 110 (as not all system settings may be compatible with the NAS device 112), as of the time and data at which the NAS device 100 created the NAS configuration image 122. According to one embodiment, the identified storage device 114 may store a plurality of versions of the NAS configuration image 122 and the communication received by the NAS device 112 may identify which of the plurality of versions of the NAS configuration images 122 is to be selected and used to migrate the NAS device 112.
Upon selecting the create tab 408, the exemplary user interface 500 of
Continuing with the example developed herein above, in the event that a NAS configuration image of the NAS device has previously been created and stored on a selected externally accessible storage device and in the event that the NAS device 502 has failed (for example), the user may desire to configure another NAS device to assume the operational state of the NAS device 502, as of the time the NAS configuration image thereof was created.
As shown in
According to one embodiment, the software that generates the user interfaces shown in
It is to be noted that the NAS configuration image or NAS configuration images created and stored on one or more externally accessible storage device may be accessed outside of the operational state migration methods described herein. Indeed, as the system settings and user data of a stored NAS configuration image may be stored as unencrypted and uncompressed user-readable directories and files in one embodiment, such NAS configuration images provide a convenient off-line copy of directories, files and settings for use, for example, when the original files become lost or corrupted, or for any other reason. The NAS configuration image or NAS configuration images created and stored on one or more externally accessible storage device need not only be used when the NAS device having created the NAS configuration image fails. Indeed, the created NAS configuration image may also facilitate upgrades of NAS device, by enabling the user to conveniently migrate from one NAS platform to a newer or upgraded NAS platform, without having to re-configure the newer or upgraded NAS platform, or reduce the need to do so.
While certain embodiments of the inventions have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions. Indeed, the novel methods, devices and systems described herein may be embodied in a variety of other forms. Furthermore, various omissions, substitutions and changes in the form of the methods and systems described herein may be made without departing from the spirit of the inventions. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the inventions. For example, those skilled in the art will appreciate that in various embodiments, the actual structures may differ from those shown in the figures. Depending on the embodiment, certain of the steps described in the example above may be removed, others may be added. Also, the features and attributes of the specific embodiments disclosed above may be combined in different ways to form additional embodiments, all of which fall within the scope of the present disclosure. Although the present disclosure provides certain preferred embodiments and applications, other embodiments that are apparent to those of ordinary skill in the art, including embodiments which do not provide all of the features and advantages set forth herein, are also within the scope of this disclosure. Accordingly, the scope of the present disclosure is intended to be defined only by reference to the appended claims.
Patent | Priority | Assignee | Title |
10495711, | Aug 11 2016 | SIEMENS HEALTHINEERS AG | System and method for comparing system configurations for magnetic resonance tomography units |
10574745, | Mar 31 2015 | Western Digital Technologies, INC | Syncing with a local paired device to obtain data from a remote server using point-to-point communication |
10944630, | Nov 20 2018 | Cisco Technology, Inc. | Seamless automation of network device migration to and from cloud managed systems |
9009525, | Jun 07 2012 | Western Digital Technologies, Inc. | Methods and systems for NAS device pairing and mirroring |
9503436, | Jun 07 2012 | Western Digital Technologies, Inc. | Methods and systems for NAS device pairing and mirroring |
9569112, | Sep 25 2014 | SanDisk Technologies, Inc | Drive compatibility information maintenance |
9846621, | Jun 26 2015 | Western Digital Technologies, INC | Disaster recovery—multiple restore options and automatic management of restored computing devices |
Patent | Priority | Assignee | Title |
7240122, | Sep 09 2003 | Hitachi, LTD | File sharing device and inter-file sharing device data migration method |
7424547, | Sep 09 2003 | Hitachi, Ltd. | File sharing device and inter-file sharing device data migration method |
7668882, | Sep 27 2005 | Hitachi, Ltd. | File system migration in storage system |
7949635, | Oct 26 2007 | Acronis International GmbH | Backup server architecture |
8285965, | Nov 20 2009 | Western Digital Technologies, INC | Aligning data storage device partition to boundary of physical data sector |
20050055402, | |||
20060129654, | |||
20070073782, | |||
20080016311, | |||
20080126446, | |||
20090037560, | |||
20090089862, | |||
20090164608, | |||
20090300081, | |||
20100115008, | |||
20100293148, | |||
20110016093, | |||
20110167044, | |||
20120102011, | |||
20140082508, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Feb 29 2012 | Western Digital Technologies, Inc. | (assignment on the face of the patent) | / | |||
Mar 01 2012 | SADRY, NAUZAD | Western Digital Technologies, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 027800 | /0399 | |
May 12 2016 | Western Digital Technologies, INC | JPMORGAN CHASE BANK, N A , AS COLLATERAL AGENT | SECURITY AGREEMENT | 038722 | /0229 | |
May 12 2016 | Western Digital Technologies, INC | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | SECURITY AGREEMENT | 038744 | /0281 | |
Feb 27 2018 | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | Western Digital Technologies, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 045501 | /0714 | |
Feb 03 2022 | JPMORGAN CHASE BANK, N A | Western Digital Technologies, INC | RELEASE OF SECURITY INTEREST AT REEL 038744 FRAME 0481 | 058982 | /0556 | |
Aug 18 2023 | Western Digital Technologies, INC | JPMORGAN CHASE BANK, N A | PATENT COLLATERAL AGREEMENT - A&R LOAN AGREEMENT | 064715 | /0001 | |
Aug 18 2023 | Western Digital Technologies, INC | JPMORGAN CHASE BANK, N A | PATENT COLLATERAL AGREEMENT - DDTL LOAN AGREEMENT | 067045 | /0156 |
Date | Maintenance Fee Events |
Mar 23 2018 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Mar 16 2022 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Date | Maintenance Schedule |
Oct 07 2017 | 4 years fee payment window open |
Apr 07 2018 | 6 months grace period start (w surcharge) |
Oct 07 2018 | patent expiry (for year 4) |
Oct 07 2020 | 2 years to revive unintentionally abandoned end. (for year 4) |
Oct 07 2021 | 8 years fee payment window open |
Apr 07 2022 | 6 months grace period start (w surcharge) |
Oct 07 2022 | patent expiry (for year 8) |
Oct 07 2024 | 2 years to revive unintentionally abandoned end. (for year 8) |
Oct 07 2025 | 12 years fee payment window open |
Apr 07 2026 | 6 months grace period start (w surcharge) |
Oct 07 2026 | patent expiry (for year 12) |
Oct 07 2028 | 2 years to revive unintentionally abandoned end. (for year 12) |