This invention relates generally to information handling systems and, more particularly, to out-of-band backup and/or restore of information handling system components.
As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
Numerous solutions exist for backup and restore of data on an information handling system. Solutions that execute in the information handling system are deemed in-band solutions. Conventional in-band backup and restore operations are managed and performed by a software application executing with a host operating system on a host central processing unit (CPU).
Disclosed herein are systems and methods that may be implemented for out-of-band backup and/or restore of information handling system components. Such out-of-band backup and restore operations may be performed, in one embodiment, to backup and/or restore hardware profile information for an information handling system. In such an embodiment, hardware profile information may include firmware images and corresponding system configuration information (i.e., rather than system software such as host operating system (OS) and associated software applications and data), and the backup and restoration of the hardware profile information may be implemented using out-of-band processing devices (e.g., service processor/s, embedded processor/s, etc.). Following restoration of firmware images and configuration therefor, the restored system firmware may be booted to allow further operations. In one exemplary embodiment, the disclosed systems and methods may be implemented to provide hardware profile restoration checkpoints, e.g. to allow a return from a more recent firmware image and/or configuration settings for same to a previous system firmware image and configuration settings for the same. This checkpoint capability may be implemented, for example, to return a system hardware profile to a “bare-metal” system condition such as described further herein.
The disclosed out-of-band backup and restore operations may be performed in one embodiment using one or more out-of-band processing devices that are separate and independent from any in-band host central processing unit (CPU) that runs the host OS of the information handling system, and without management of any application executing with a host OS on the host CPU. Moreover, a remote system manager may also be provided with the ability to manage and control an out-of-band processing device from across an out-of-band network to perform out-of-band firmware backup and/or restore operations. Examples of system firmware information that may be backed up and/or restored using the disclosed systems and methods include, but are not limited to, firmware and configurations therefor, e.g., such as system platform basic input/output system (BIOS) firmware, motor control (MC) firmware, redundant array of independent disks (RAID) firmware, network interface card (NIC) firmware, Remote Access Controller firmware, etc. Thus, the disclosed out-of-band backup and restore operations may be implemented, for example, to restore hardware profile information and then load an operating system (OS) such a Linux, or configure/reconfigure RAID settings (e.g., back to RAID 1 configuration) on an information handling system. It will be understood that a restore request may also include a request to initially load hardware profile information for the first time, as well as request to reload previously backed up hardware profile information.
In one exemplary embodiment, the disclosed systems and methods may be implemented at a low level working layer to perform a full backup and restore of hardware profile information (e.g., firmware configurations) for an information handling system that exists in a “system down” or a “bare-metal” state. In system down state, an OS may be installed but the host CPU is down (e.g., halted or powered off). In such a system down state, an out-of-band processing device may be employed to control system hardware. A bare-metal system may be, for example, configured with an out-of-band processing device (e.g., service processor, embedded processor, etc.) that is not configured with proper firmware and/or firmware credentials for use. One example of a type of bare-metal information handling system is an information handling system configured with no host operating system (OS) to boot from (e.g., as may be provided from the factory or assembly plant with no host OS yet installed). A bare-metal information handling system may also be an information handling system that is configured with OS software and firmware, but that is not yet set up for use with proper firmware configurations and credentials for proper operation. A bare-metal system may also be, for example, a decommissioned system in which all firmware and user data, applications and the host OS has been removed (e.g., by secure delete) from the system drives. Another example of a bare-metal system is a redundant array of independent disks (RAID) system that does not have the proper RAID controller configuration yet installed (e.g., for virtual disk creation) to allow for OS installation. In one exemplary embodiment, such a bare-metal information handling system may have no applications or other user information resident on the main storage of the system (e.g., hard drive or solid state drive (SDD) containing no data and being only formatted or reformatted), and may in one example have only a hardware configuration agent and/or factory default firmware configurations stored (e.g., on system persistent storage).
The disclosed systems and methods may be advantageously employed to utilize a programmed out-of-band processor to perform full out-of-band firmware backup and restore operations for firmware and/or firmware configurations. Exemplary operations with which such a capability may be useful include, but are not limited to, out-of-band full firmware backup and restore during replacement of a motherboard of an information handling system e.g., where there is no OS, no agent, and no pre-installed software present on the system. In one exemplary embodiment, the disclosed systems and methods may be implemented to program and utilize an out-of-band processor to perform a full out-of-band firmware and firmware configuration backup in response to a single command, and then to restore the firmware and/or firmware configurations to its original state and/or settings as represented by the contents of the backup with a subsequent command.
The disclosed systems and methods may be implemented in one exemplary embodiment to enable users and field technicians to fully backup and restore BIOS and firmware in virtually any information handling system state, including “bare metal” or “system down” state. In one exemplary embodiment of a backup operation, at least an operable portion of the hardware profile configuration and payloads (e.g., BIOS firmware image, RAID controller firmware image, service processor firmware image, etc.) for information handling system hardware components may be saved to an image in a targeted save location, e.g., in embedded persistent storage of the information handling system and/or to external storage such as external non-volatile random access memory (e.g., such as removable vFlash) or a mounted (e.g., network) shared location (e.g., Windows network file system NFS, common Internet file system CIFS; HTTP webserver, etc.) A restore operation may be performed by using an operation that is performed in reverse to the backup operation in order to retrieve the configuration and payload information image from the targeted save location, and to place the retrieved image back on the source device/s and partition/s thereof.
In one respect, disclosed herein is an information handling system, including: one or more processing devices; operational storage coupled to the one or more processing devices, the operational storage configured to maintain hardware profile information for use by processing devices of the information handling system; and a backup and/or restore framework. The one or more processing devices may be configured (e.g., programmed) to execute the backup and/or restore framework to: receive a request from at least one of a local user or remote user for at least one of backup or restore of hardware profile information, and to provide the received backup or restore request to the one or more processing devices for processing. The one or more processing devices may also be configured to respond to the received backup or restore request in an out-of-band manner to at least one of: backup the hardware profile information by transferring the hardware profile information from an operational storage location on the information handling system to a backup storage location, or restore the hardware profile information by transferring the hardware profile information from a backup storage location to an operational storage location on the information handling system.
In another respect, disclosed herein is a method for backing up and/or restoring hardware profile information on an information handling system, the method including providing an information handling system that includes one or more processing devices, and operational storage coupled to the one or more processing devices, the operational storage configured to maintain hardware profile information for use by processing devices of the information handling system. The method may further include receiving a request in the information handling system from at least one of a local user or remote user for at least one of backup or restore of hardware profile information on the information handling system; and using the one or more processing devices to respond to the received backup or restore request in an out-of-band manner to at least one of: backup the hardware profile information by transferring the hardware profile information from an operational storage location on the information handling system to a backup storage location, or restore the hardware profile information by transferring the hardware profile information from a backup storage location to an operational storage location on the information handling system.
It will be understood that the embodiment of
The disclosed systems and methods may be implemented in one exemplary embodiment using a plug-in architecture framework to allow extension of system management functionalities (e.g., using Dell unified server configurator (“USC”) server management functionalities available from Dell Products L.P. of Round Rock, Tex.) in a unified extension firmware interface (“UEFI”) environment by leveraging available remote access controller core or optional flash memory space. Further information on implementation of USC functionalities in a UEFI environment may be found, for example, in U.S. patent application Ser. No. 12/587,001 filed Sep. 30, 2009, and incorporated herein by reference in its entirety for all purposes. Among other things, the disclosed systems and methods may be implemented to provide a hardware and software interface to allow use of a plug-in framework in the embedded system management that may be run under the BIOS firmware and the UEFI environment. The disclosed systems and methods may also be implemented to provide a USC management architecture that may be modified and enhanced over time, and/or that may also be employed to extend availability of the USC management framework to remote users 128.
Still referring to
In the embodiment of
As further shown, remote access controller 125 is coupled to remote access controller persistent storage 140 (e.g., embedded and partitioned flash memory, Electrically Erasable Programmable Read Only Memory—EEPROM, etc.), upon which one or more management applications forming part of a USC framework may be stored in addition to one or more components or applications forming part of out-of-band hardware profile backup and/or restore framework 142 and other functions, e.g., BIOS, unified extensible firmware interface (“UEFI”) modules, etc. In the embodiment of
As further shown in
Data manager/job control layer 308 may act to manage the queue of backup and restore jobs, and may include a data cache layer 310 that is present to allow backup and/or restore hardware profile parameters and data (e.g., firmware and firmware configurations) to be cached in memory before being committed to a storage location, e.g., in persistent partitioned file/s 330 on persistent storage 140 and/or to optional non-volatile memory device 392 (e.g., VFLASH, insertable and removable memory device such as USB key or thumbdrive, etc.), the latter which may be non-removable or which in one embodiment may be a removable device when present. Data manager/job control layer 308 may also be optionally configured to control the invocation and tracking of hardware profile backup and restoration configuration jobs. It will be understood that the particular configuration of data manager/job control layer 308 is exemplary, and that it is not necessary that layer 308 be present.
As shown in
Also shown in
As shown, in step 402 out-of-band processor 108 (e.g., acting as a backup and restore request processor) may receive a backup or restore client request command via WSMAN 302 from a remote user 128 via embedded remote out-of-band hardware profile backup and/or restore framework 142 which operates to process the request in the manner as previously described and illustrated. The backup or restore client request command may relate to backup or restoration of hardware profile information such as firmware (and firmware configurations therefor) including, but not limited to, system platform basic input/output system (BIOS) firmware, motor control (MC) firmware, redundant array of independent disks (RAID) firmware, network interface card (NIC) firmware, Remote Access Controller firmware, etc. In response to a backup request, such hardware profile information may be retrieved from a given operational storage location on information handling system 104 (e.g., such as persistent storage 140) for backup to a designated backup storage location (e.g., such as NVRAM 392 or external network shared storage 394). Operational storage locations may also be a file transfer protocol (FTP) site, network share site (network file system “NFS” or common internet file system “CIFS”), hypertext transfer protocol (HTTP) site, etc. In the case of a restore request, such hardware profile information may be retrieved from a given separate storage location (e.g., such as NVRAM 392 or external network shared storage 394) for transfer to a operational storage location on information handling system 104 (e.g., such as persistent storage 140).
The given received request of step 402 may be processed in step 404 by CIMOM 304, before invoking CIM provider 306 in step 406 to serve the WSMAN/CIMOM request, e.g., by sending a backup or restore request to data manager/job control layer 308 in order to create the given backup or restore job. The backup or restore request sent to data manager/job control layer 308 by CIM provider 306 in step 406 may include the address information required to either construct a new backup file (for a requested backup operation) or read the backup file (for a requested restore operation), and to access the designated storage location for the backup file. In step 408, data manager/job control layer 308 may then generate a new backup or restore job in the job store and validate the destination, as appropriate. In this regard, data manager/job control layer 308 may store the hardware profile parameters and data of the requested job in data cache 310 where it is preserved, e.g., in case of later job interruption. It is noted that WSMAN commands may be processed by the corresponding provider/s responsible for backup and restore functions. Thus, the WSMAN request may be sent via secure HTTP request and processed by the CIMON service and dispatched to corresponding provider/s with invoking methods and attributes.
As further shown in
Still referring to
As previously described, data manager/job control layer 308 may also track the status of each hardware profile backup or restore job in step 408. However, in the case of a local request from a local user, data manager/job control layer 308 may provide (e.g., copy) the job status to local storage (e.g., such as a removable USB key/thumb drive device or other suitable storage device) in step 416, and may additionally or alternatively report the job status to a local user (e.g., via graphical user interface on the screen of a local console using video/graphics 109) in step 418. Job status may also be additionally or alternatively reported through remote service method and returned as a query response. In any case, the provided job status information may be of similar form and content to that previously described in relation to step 407 of
Whether processing a local or remote hardware profile backup or restore request, methodology 400 proceeds from step 408 to step 420, where backup and restore orchestrator (BRO) layer 360 is launched on out-of-band processor 108. BRO layer 360 prepares to make the storage area available to remote access controller 125 that corresponds to the designated backup location address information stored in step 408, either as a destination for backup information or as a source/service for restore information. In this regard, all credentials and access may be checked in step 420 by download/share access event logging module 362 of BRO layer 360 for external network shares, e.g., where a designated backup location address corresponds to external network storage shares 394 of
After the tasks of step 420 are completed and the storage area corresponding to the designated backup location has been checked and verified according to the type of storage device involved, methodology 400 proceeds to step 422 where the storage device (e.g., external network shares 394 or NVRAM 392) and corresponding designated backup location address thereon is exposed by module 362 of BRO layer 360 to the remote access controller 125. Next, the backup hardware profile data, parameters, and payload for a requested backup job will then be optionally compressed and encrypted using data collection/restoration module 364 of BRO layer 360 running on the out-of-band processor of remote access controller 125 prior to storage by module 364 in the designated backup location address in step 424. In the case of a requested restore job, requested restore hardware profile data, parameters and payload may be retrieved by module 364 in optional compressed encrypted from the designated backup location address and optionally decompressed and decrypted by the out-of-band processor of remote access controller 125 in step 424. A retrieved backup image may also be optionally validated (e.g., by making sure that payload has not been tampered with) by BRO layer 360 before proceeding further than step 424. Methodology 400 may terminate upon backup image validation failure, e.g., with display of optional error message to the given requested remote or local user. With regard to the above discussion, it will be understood that data is used as a generic term, while parameter is a set of attributes or data, and a payload is a package of data that serves a specific purpose and that may be delivered in a chunk.
Next, in step 426 any external remote share network access open for remote access controller 125 may be closed by module 362 of BRO layer 360. Then in step 428, job control status module 366 of BRO layer 360 may check to verify what portion of the original requested backup or restore job has been completed, and update the job status of data manager/job control layer 308 to include this current status. In the case of a restore job task, such as installation of firmware like BIOS, multiple steps may be required. For example, module 366 of BRO layer 360 may verify in step 428 that a new BIOS image has been installed (e.g., restored from backup or initially installed) from an external source. Such a BIOS image may be, for example, an updated, new or replacement BIOS image. After verifying that the BIOS image has been installed, module 366 of BRO layer 360 may optionally reboot (power cycle) information handling system 104, prior to proceeding with configuration of the now installed (e.g., updated) BIOS image. However, it will be understood that reboot is not required, and that a restore operation may be initiated without requiring reboot.
Still referring to
Next, in step 522, firmware images and configuration therefor for any implicated devices of information handling system 104 other than out-of-band processor 108 (e.g., service processor) are updated using the restored data as applicable. In step 524 firmware images and configuration therefor for out-of-band processor 108 (e.g., service processor) are updated using the restored data as applicable. Out-of-band processor 108 (e.g., service processor) is then rebooted in step 526, followed by rebooting of the host system 104 (with in-band processor 106) in step 528.
It will be understood that methodology 400 of
For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system may be a personal computer, a PDA, a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include memory, one or more processing resources such as a central processing unit (CPU) or hardware or software control logic. Additional components of the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communications between the various hardware components.
It will be understood that one or more of the tasks, functions, or methodologies described herein (e.g., including those performed by remote access controller 125 and out of band processor/s 108) may be implemented by a computer program of instructions (e.g., computer readable code such as firmware code or software code) embodied in a non-transitory tangible computer readable medium (e.g., optical disk, magnetic disk, non-volatile memory device, etc.), in which the computer program comprising instructions are configured when executed (e.g., executed on a processing device of an information handling system such as CPU, controller, microcontroller, processor, microprocessor, FPGA, ASIC, or other suitable processing device) to perform one or more steps of the methodologies disclosed herein. A computer program of instructions may be stored in or on the non-transitory computer-readable medium residing on or accessible by an information handling system for instructing the information handling system to execute the computer program of instructions. The computer program of instructions may include an ordered listing of executable instructions for implementing logical functions in the information handling system. The executable instructions may comprise a plurality of code segments operable to instruct the information handling system to perform the methodology disclosed herein. It will also be understood that one or more steps of the present methodologies may be employed in one or more code segments of the computer program. For example, a code segment executed by the information handling system may include one or more steps of the disclosed methodologies.
While the invention may be adaptable to various modifications and alternative forms, specific embodiments have been shown by way of example and described herein. However, it should be understood that the invention is not intended to be limited to the particular forms disclosed. Rather, the invention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims. Moreover, the different aspects of the disclosed systems and methods may be utilized in various combinations and/or independently. Thus the invention is not limited to only those combinations shown herein, but rather may include other combinations.
Number | Name | Date | Kind |
---|---|---|---|
5603005 | Bauman et al. | Feb 1997 | A |
5717942 | Haupt et al. | Feb 1998 | A |
6108697 | Raymond et al. | Aug 2000 | A |
6144992 | Turpin et al. | Nov 2000 | A |
6298443 | Colligan et al. | Oct 2001 | B1 |
6336161 | Watts | Jan 2002 | B1 |
6408334 | Bassman et al. | Jun 2002 | B1 |
6470446 | Beelitz et al. | Oct 2002 | B1 |
6519679 | Devireddy et al. | Feb 2003 | B2 |
6763458 | Watanabe et al. | Jul 2004 | B1 |
6820214 | Cabrera et al. | Nov 2004 | B1 |
6854122 | Sheriff et al. | Feb 2005 | B1 |
6973587 | Maity et al. | Dec 2005 | B1 |
7028138 | Ali et al. | Apr 2006 | B2 |
7216200 | Zhang et al. | May 2007 | B2 |
7272815 | Eldridge et al. | Sep 2007 | B1 |
7360211 | Hyden et al. | Apr 2008 | B2 |
7409575 | Komarla et al. | Aug 2008 | B2 |
7426052 | Cox et al. | Sep 2008 | B2 |
7430592 | Schmidt et al. | Sep 2008 | B2 |
7526541 | Roese et al. | Apr 2009 | B2 |
7610575 | Sproule | Oct 2009 | B2 |
7660913 | Zimmer et al. | Feb 2010 | B2 |
7706369 | Roese et al. | Apr 2010 | B2 |
7739372 | Roese et al. | Jun 2010 | B2 |
7739402 | Roese et al. | Jun 2010 | B2 |
7765371 | Abels et al. | Jul 2010 | B2 |
7805533 | Burns et al. | Sep 2010 | B2 |
7877614 | Frenkiel et al. | Jan 2011 | B2 |
7895428 | Boland et al. | Feb 2011 | B2 |
7898977 | Roese et al. | Mar 2011 | B2 |
7945945 | Graham et al. | May 2011 | B2 |
8086834 | Brisky et al. | Dec 2011 | B2 |
8086838 | Harmer | Dec 2011 | B2 |
8099624 | Saxena et al. | Jan 2012 | B1 |
8191107 | Frattura et al. | May 2012 | B1 |
8260841 | Maity | Sep 2012 | B1 |
8261044 | Kinstler | Sep 2012 | B2 |
8407662 | Lam | Mar 2013 | B2 |
8510422 | Phung et al. | Aug 2013 | B2 |
20030216143 | Roese et al. | Nov 2003 | A1 |
20040162857 | Butts | Aug 2004 | A1 |
20050027837 | Roese et al. | Feb 2005 | A1 |
20050055688 | Barajas et al. | Mar 2005 | A1 |
20050066015 | Dandekar et al. | Mar 2005 | A1 |
20050076245 | Graham et al. | Apr 2005 | A1 |
20050166213 | Cromer et al. | Jul 2005 | A1 |
20050172280 | Ziegler et al. | Aug 2005 | A1 |
20050216664 | Taninaka et al. | Sep 2005 | A1 |
20050237996 | Sakuraba et al. | Oct 2005 | A1 |
20060018505 | Cherian et al. | Jan 2006 | A1 |
20060031936 | Nelson et al. | Feb 2006 | A1 |
20060036730 | Graham et al. | Feb 2006 | A1 |
20060048142 | Roese et al. | Mar 2006 | A1 |
20060075093 | Frattura et al. | Apr 2006 | A1 |
20060190532 | Chadalavada | Aug 2006 | A1 |
20060212143 | Nguyen et al. | Sep 2006 | A1 |
20070101077 | Evanchik et al. | May 2007 | A1 |
20070124407 | Weber et al. | May 2007 | A1 |
20070156263 | Gorzelic et al. | Jul 2007 | A1 |
20070162695 | Ali et al. | Jul 2007 | A1 |
20070168049 | Rao et al. | Jul 2007 | A1 |
20070168481 | Lambert et al. | Jul 2007 | A1 |
20070204105 | Lauffer et al. | Aug 2007 | A1 |
20080002694 | Brahmaroutu et al. | Jan 2008 | A1 |
20080033972 | Yin et al. | Feb 2008 | A1 |
20080126551 | Conner et al. | May 2008 | A1 |
20080155094 | Roese et al. | Jun 2008 | A1 |
20080201501 | Partani et al. | Aug 2008 | A1 |
20090037655 | Cherian et al. | Feb 2009 | A1 |
20100057987 | Liu | Mar 2010 | A1 |
20100268925 | Brisky et al. | Oct 2010 | A1 |
20100306773 | Lee et al. | Dec 2010 | A1 |
20110072280 | Chiasson et al. | Mar 2011 | A1 |
20110078293 | Phung et al. | Mar 2011 | A1 |
20110173427 | Merkin et al. | Jul 2011 | A1 |
20110264951 | Pratt et al. | Oct 2011 | A1 |
20110289350 | Andrews et al. | Nov 2011 | A1 |
20110296404 | Zhang et al. | Dec 2011 | A1 |
20120110262 | Zhang et al. | May 2012 | A1 |
20120198245 | Mundt et al. | Aug 2012 | A1 |
20120317633 | O'Donnell et al. | Dec 2012 | A1 |
Entry |
---|
IBM, “Navigator for I”, Printed From Internet May 26, 2009, 3 pgs. |
IBM, “IBM iSeries Navigator System Management Plug-In for SAP”, Printed From Internet May 26, 2009, 1 pg. |
Business Wire; Business Services Industry, “F5 and Oracle Collaborate to Release Big-Ip Load Balancer System Management Plug-In for Oracle Enterprise Manager 10g Grid Control”, Oct. 31, 2005, 10 pgs. |
Highbeam Research, “Nimsoft Team Up With Oracle”, Printed From Internet May 26, 2009, 4 pgs. |
All Business, “Oracle Releases F5 Management Plug-In Via iControl”, Printed From Internet May 26, 2009, 4 pgs. |
Warren Togami, “Remote Conversion to Linux Software RAID-1 for Crazy Sysadmins HOWTO”, 2004, 11 pgs. |
“Remote Raid/Mirror”, HTMICenter, Printed From Internet Jul. 22, 2010, 2 pgs. |
Power6 Information, “Installing an HA-two system RAID Configuration”, Printed From Internet Jul. 22, 2010, 4 pgs. |
Phung et al. “Systems and Methods for Extension of Server Management Functions”, U.S. Appl. No. 12/587,001; Office Action, Jun. 15, 2012, 13 pgs. |
Wikipedia, “License Manager” Printed from Internet Jun. 20, 2012, 2 pgs. |
McNeill, “Virtual Machine Asynchronous Patch Management”, U.S. Appl. No. 13/210,552, filed Aug. 16, 2011, 17 pgs. |
Karandikar et al., “System and Method for Providing an Image to an Information Handling System”, U.S. Appl. No. 13/174,221, filed Jun. 30, 2011, 35 pgs. |
Zhang et al., “Systems and Methods for Intelligent System Profile Unique Data Management”, U.S. Appl. No. 13/618,666, filed Sep. 14, 2012, 32 pgs. |
Phung et al. “Systems and Methods for Extension of Server Management Functions”, U.S. Appl. No. 12/587,001; Amendment, Oct. 15, 2012, 16 pgs. |
Phung et al., “Systems and Methods for Extension of Server Management Functions”, U.S. Appl. No. 13/898,991, filed May 21, 2013, Preliminary Amendment, Jun. 27, 2013, 18 pgs. |
Zhang et al., “Systems and Methods for Remote Raid Configuration in an Embedded Environment”, U.S. Appl. No. 12/925,673, filed Oct. 27, 2010, 31 pgs. |
Andrews et al., “System and Method for Removable Network Attached Storage Enabling System Recovery From Backup”, U.S. Appl. No. 13/187,219, filed Jul. 20, 2011, 30 pgs. |
Phung et al., “Systems and Methods for Extension of Server Management Functions”, U.S. Appl. No. 13/898,991, filed May 21, 2013, 25 pgs. |
Number | Date | Country | |
---|---|---|---|
20130205063 A1 | Aug 2013 | US |