CN101366006A - Simulation Components for Data Backup Applications - Google Patents

Abstract

An emulation component for a data backup system is provided. The emulation component represents a storage device, such as a flash memory device or a partition of a disk drive, as if it were an auto-launch device, that will trigger applications to execute automatically. Accordingly, other computing systems, such as personal computers, interact with the storage device, through the emulation component, as if the storage device were the auto-launch device. Because the emulation component makes this representation, merely connecting the emulation component between the storage device and the computing system can cause a backup application stored on the storage device to automatically execute on the computing system. A data backup appliance including an emulation component and a storage device is also provided. The backup system can also include an interface for connecting another removable device, such as a disk drive, for storing backup content from the data source.

Description

Simulation Components for Data Backup Applications

Cross References to Related Applications

This application claims U.S. Provisional Patent Application No. 60, filed on October 12, 2005, entitled "A Method, Apparatus and a System for Removable Media Device Emulation on an External Storage Device via an Emulation Component for the Purpose of an Electronic Data Backup Appliance" /725,225's interest, the entire contents of which are hereby incorporated by reference.

technical field

The present invention relates generally to the field of digital data management, and more particularly to a component of a data backup application configured to emulate a media device.

Background technique

Digital content represented by digital data files of various file types is rapidly replacing other forms of content. For example, documents, presentations, photographs, movies and music are increasingly produced and stored digitally. A problem encountered by many individuals and institutions is that digital content typically stored on computer hard drives is poorly organized and needs to be archived to prevent accidental loss. For example, digital photo files on a personal computer (PC) may be found in many folders—photos transferred from a digital camera are stored in one set of folders, photos received as e-mail attachments are stored in others , while photos downloaded from websites are stored in a separate folder.

One way to archive digital content is to periodically back up all data files on a computer and preserve the existing organizational structure. Although this technique is effective for protecting data content from accidental loss, this technique has several disadvantages. For example, the resulting copy is no better organized than the original, so misplaced or jumbled content remains misplaced or jumbled. Furthermore, backing up all data files requires a large amount of storage capacity to copy many files that would otherwise be kept elsewhere. For example, application-specific files that are originally loaded onto a computer from a compact disc (CD) are already archived on the CD and therefore do not need to be backed up.

The storage capacity required for a full backup can be obtained using a writable data storage medium such as a hard disk drive (HDD), however, this requires equipment assembly and software installation when first connected to the system. To complete these steps, the user may have to provide information about the existing system that the user may not readily know. Also, the user may have to make decisions regarding device and software configurations. The number of steps involved in installation and assembly, and the complexity of some steps, prevent many users from bothering with backup applications. The expense of writable data storage media with sufficient capacity to perform a full backup also discourages users from performing full backups. Furthermore, some users who have purchased and installed the required storage capacity do not perform backups very often because of the long time the system takes during the entire backup period.

Alternatively, the user may manually select a set of files from the directory and copy the selected files to the storage device. While this alternative allows the use of smaller storage devices that do not require installation and assembly steps, manual selection of files is time consuming. Also, manually selecting files has the potential to accidentally miss some files.

Therefore, what is needed is the ability to selectively back up data content in an economical and convenient manner.

Contents of the invention

An exemplary emulation component is provided for use between a storage device of a first device type and a data source running an operating system. Here, the emulation component includes logic configured to return a response to a query from a data source, wherein the response indicates that the storage device is a second device type that triggers an operating system to automatically A class of device types that load applications stored on storage devices. As discussed further herein, devices falling into this category are referred to herein as "autoloading devices."

Another exemplary emulation component for use between a data source and a first storage device is provided. In an exemplary embodiment, the emulation component includes logic configured to represent a first logical storage region of the first storage device as an autoload device; and to represent a second logical storage region of the first storage device as comprising Logical means of a second storage device writable to the data storage medium. In some embodiments, the emulation component further includes an autoload device command configured to receive an autoload device addressing the autoload device from the data source, translate the autoload device command into a first storage device command, and send the first storage device command to Logical device to the first logical storage area. Here, the emulation component further includes logic configured to receive the first storage device response from the first logical storage area, translate the first storage device response into an autoloader response, and send the autoloader response to the data source. In some embodiments, the emulation component further includes logic configured to receive a second storage device command from the data source addressing the second storage device and send the second storage device command to the second logical storage area, and configure Logical means for receiving a second storage device response from the second logical storage area and sending the second storage device response to the data source.

In some embodiments, the emulation component can be configured to represent the first logical storage area as a CD drive or a digital video disc (DVD) drive. Likewise, in some embodiments, the emulation component can be configured to represent the second logical storage area as a HDD, Secure Digital (SD) memory card, Flash memory (CF) card, memory stick, or other storage including writable data storage media. equipment. It should be appreciated that the logic of the various exemplary simulation components described herein may be implemented in software, hardware, firmware, or a combination thereof.

A data backup system is also provided. In an exemplary embodiment, a data backup system includes a communication interface; a first storage device including a writable data storage medium; and an emulation component communicating between the first storage device and the communication interface. In this embodiment, the emulation component is configured to represent the first storage device as an autoload device. The emulation component is also configured to receive an autoloader command from the data source that addresses the autoloader, translate the autoloader command into a first storage device command, and send the first storage device command to the first storage device. The emulation component is also configured to receive a first storage device response from the first storage device, translate the first storage device response into an autoloader response, and send the autoloader response to the data source. Here, the communication interface may include, for example, a Universal Serial Bus (USB) communication interface or a FireWire (FireWire) communication interface. The first storage device may include, for example, an HDD, an SD memory card, or a CF memory card. Also, the emulation component can represent the first storage device as a CD drive or a DVD drive.

In some embodiments, the data backup system also includes a removable storage device interface to provide communication between the simulation component and the removable storage device. Accordingly, the emulation component of the data backup system may also be configured to receive and send removable storage device commands from the data source to the removable storage device, the removable storage device command pair interfacing with the removable storage device Addressable removable storage devices. The emulation component can also be configured to receive a removable storage device response from the removable storage device interfaced with the removable storage device and to send the removable storage device response to the data source.

Description of drawings

Figure 1 is a schematic representation of a data backup system according to an exemplary embodiment of the present invention;

Figure 2 is a schematic representation of a data backup system according to another exemplary embodiment of the present invention;

Fig. 3 is a flowchart of a method for backing up data files on a data source according to an exemplary embodiment of the present invention;

4 is a flowchart of a process by which a data source identifies a data backup system as two attached devices, according to an exemplary embodiment of the invention.

Detailed ways

Provides a data backup system for personal as well as business applications. The data backup system of the present invention allows files to be selectively copied from a data source such as a personal computer to a storage device based on some criteria such as file type. For example, the system may be configured to back up audio files with recognized music file extensions such as .mp3 and .wav or image files with recognized image file extensions such as .jpg, .pct and .GIF. According to some embodiments, the data backup system stores a backup application that is automatically loaded when the data backup system is connected to the data source. Backup applications can be configured to require little or no user input to perform the backup process.

Data backup systems can take many different forms. An example is a device that includes a backup application and has sufficient storage for copied files. Another example is to include a backup application and an interface to a storage device with sufficient storage capacity in the form of a storage device such as an external HDD or flash device. In both examples, the system includes simulation components. The emulation component makes the part of the data backup system that includes the backup application appear to be a data source with a specific device type. More specifically, the backup application portion of the data backup system is represented as one of a class of storage devices referred to herein as "automount devices." Emulating an autoloader device allows the data backup system to take advantage of the auto-execution capabilities of certain operating systems such that the backup application will automatically execute when the device is connected to a data source running the operating system.

FIG. 1 provides a schematic representation of an exemplary embodiment of a data backup system 100 connected to a data source 110 via a connection 120 . Data source 110 may be, for example, a personal computer (PC), a Macintosh computer (Mac), or a personal digital assistant (PDA) on which data is stored. Data sources 110 may also include servers, set-top boxes, televisions, cellular phones, smart phones, digital still or video cameras, scanners, digital music or video players, game consoles, or personal video recorders (PVRs). Preferably, data source 100 includes an operating system (OS), such as Windows XP, that includes the application autoloading functionality discussed in detail elsewhere herein. Other suitable operating systems include MacOS, PalmOS, Linux and Unix, for example. Connection 120 between backup system 100 and data source 110 may be virtually any digital transmission structure such as a fiber optic or electrical cable, wireless link, or network connection. Connection 120 is shown in dashed lines in FIG. 1 to indicate that connection 120 is only temporarily required.

As shown in FIG. 1 , the backup system 100 includes a communication interface 130 , an emulation component 140 and a storage device 150 , and the storage device 150 includes a first logical storage area 160 and a second logical storage area 170 . The communication interface 130 allows the data source 110 to communicate with the simulation component 140 of the backup system 100 according to a communication protocol. Communication interface 130 may be, for example, USB, FireWire or a wireless interface such as infrared, Bluetooth or WiFi.

It can be appreciated that backup system 100 may include multiple communication interfaces 130 of the same or different types to accommodate multiple and/or different data sources 110 . Depending on the type of communication interface 130 , communication interface 130 may include a communication port through which connection 120 to data source 110 is made. For example, USB communication interface 130 may include a USB communication port, and FireWire communication interface 130 may include a FireWire communication port. Alternatively, the communication interface 130 may include a wireless antenna or an infrared transmitter/receiver unit for transmitting and receiving infrared signals.

The storage device 150 includes a writable data storage medium, and may be, for example, an HDD that has been divided into at least two logical storage areas. In this example, each logical storage area is a partition of HDD. Suitable HDDs for storage device 150 include 1.0-inch, 1.8-inch, 2.5-inch, and 3.5-inch hard drives with capacities of 20 to 60 gigabytes (GB) or greater. Other suitable storage devices 150 including rewritable media are solid state storage devices such as SD memory cards and CF memory cards. Storage device 150 may also be an optical device such as a CD drive or DVD drive. The writable data storage medium within such optical storage device 150 may be a write-once medium such as a compact disc recordable (CD-R), or a rewritable medium such as a compact disc rewritable (CD-RW).

It is also possible to implement the storage device 150 by two different devices, one dedicated to one of the two logical storage areas 160,170. For example, the first logical storage area 160 can be implemented by a CD drive having any CD medium, and the second logical storage area 170 can be implemented by an HDD. It should be understood that the device types, form factors, and capacities presented herein are exemplary only and not limiting.

In some embodiments, the backup system 100 also includes a storage device interface 190 that allows the first and second logical storage areas 160 and 170 to communicate with the emulation component 140 . In these embodiments, storage device interface 190 is of a type appropriate for the type of storage device 150 . For example, an integrated drive electronics (IDE) interface 190 may be used with an IDE HDD storage device 150, and a small computer system interface (SCSI) type interface 190 may be used with a SCSI HDD storage device 150. Alternatively, when the storage device 150 is an SD memory card, the storage device interface 190 may be an SD memory card host interface. Interface 190 may also be a wireless interface such as infrared, WiFi, and Bluetooth. Storage device interface 190 may be implemented in backup system 100 through an integrated circuit (IC) chip or through the use of discrete components. In some embodiments, storage device interface 190 is integrated into storage device 150 . It should be appreciated that in the embodiments described above using multiple storage devices 150 , backup system 100 may suitably include multiple storage device interfaces 190 .

The first logical storage area 160 represents a logical area of the storage device 150 that is not accessible to a user of the storage device 150 and that is secure from accidental erasure. The first logical storage area 160 may include, for example, backup applications, system files, drivers, and other installation and configuration software. The first logical storage area 160 is represented to the data source 100 by the emulation component 140 as an autoloader. As used herein, autoloading devices are those devices that trigger the autorun function of a particular operating system, such as the autorun function of the Microsoft Windows operating system. Examples of device types that trigger Windows' autorun include CD and DVD drives.

The second logical storage area 170 represents a logical area of the storage device 150 dedicated to storing backup data. Correspondingly, the simulation component 140 represents the second logical storage area 170 to the data source as a device type including a writable data storage medium. For example, the second logical storage area 170 may represent a HDD, CF, or SD memory card. In some embodiments, the second logical storage area 170 may represent the same device type as the storage device 150 . In other embodiments, the second logical storage area 170 may be represented as a different device type than the storage device 150 .

The emulation component 140 provides specific functions to the backup system 100, and the emulation component 140 can be realized by a logic device such as software, firmware, hardware or any combination thereof. It should be understood that in the embodiments, different functions of the simulation component may be realized by different forms of logic devices. Thus, for example, while one function of the emulation component 140 is implemented, for example, by firmware, another function may be implemented by software.

In one embodiment, emulation component 140 includes an IC. For example, emulation component 140 may be implemented using software, firmware, hardware, or some combination thereof incorporated into a USB controller chipset. In some USB-specific embodiments, emulation component 140 implements some or all of multiple layered industry standards. Examples of such standards include USB Specification - Revision 2.0, USB Mass Storage Class - Bulk Transfer Only - Revision 1.0, SCSI Primary Command-3 (SPC-3), SCSI Block Command-2 (SBC-2), Multimedia Command-4 (MMC-4) and AT Attachment and Packet Interface-6 (ATA/ATAPI-6). It should be noted that in some embodiments, emulation component 140 may only support a subset of these industry standard commands.

The functionality provided by the emulation component 140 may include representing the first logical storage area 160 as an autoload device and the second logical storage area 170 as a device comprising a writable data storage medium. Thus, data source 110, when connected to backup system 100, recognizes data backup system 100 as two attached devices. It should be noted, however, that in some embodiments, the contents of these two devices are not accessible to the user of the data source, but are accessible through a backup application configured with appropriate application programming interface (API) calls. This serves to protect the contents of both the first and second logical storage areas from accidental modification or erasure. In some embodiments, to access the backup data from the second logical storage area 170, the data backup system 100 restores the data to the data source or copies the data to another device. In other embodiments, the virtual device representing the second logical region 170 is accessible to the user while the virtual device representing the first logical region 160 is not. In these embodiments, the user is allowed to directly access the contents of the second logical storage area 170 but not the contents of the first logical storage area 160 .

Another function that the emulation component 140 can provide is to translate between commands and responses in multiple formats, such as between HDD and CD drive command sets. Thus, when data source 110 sends a command to backup system 100 addressing an autoload device (as represented by first logical storage area 160 ), emulation component 140 sends the command to first logical storage area 160 before sending the command to Commands are translated from the autoloader format to the appropriate format for the storage device 150 . Similarly, a response from the first logical storage area 160 in the format of the storage device 150 is translated into the autoloader format and sent to the data source 110 so that the response appears to be from the autoloader.

It should be noted that the translation between the formats of the CD drive and the HDD is just one example, and in some embodiments, the emulation component 140 can implement one or more similar format translations. As used herein, a "storage device command" refers to a command in the appropriate format for a particular storage device, and a "storage device response" refers to a response in the same format. As a specific example, an "autoloader command" refers to a command in the appropriate format for a particular autoloader, and an "autoloader response" refers to a response in the same format.

Yet another function provided by the emulation component 140 is the transfer of commands and responses between the data source 110 and the second logical storage area 170 . When a command received by emulation component 140 is already in the appropriate format for storage device 150, emulation component 140 does not have to translate the command or the response. Here, the emulation component 140 receives a command to address a device including a writable data storage medium from the data source 110 and transmits the command to the second logical storage area 170 . In a similar manner, the response is relayed back to the data source 110 without translation. It should be appreciated that emulation component 140 may be configured to represent second logical storage area 170 as a different device type than that of storage device 150 . In some embodiments, emulation component 140 is configured to translate between the device type represented by second logical storage area 170 and the format of storage device 150 .

FIG. 2 provides a schematic representation of another exemplary embodiment of a data backup system 200 that, like data backup system 100 , is also connected to data source 110 via connection 120 . Like the data backup system 100 , the backup system 200 also includes a communication interface 130 and an emulation component 140 . In this embodiment, the backup system 200 also includes a storage device 210 comprising a writable data storage medium and a suitable storage device interface 220 . Because the writable data storage medium of storage device 210 need only include sufficient storage capacity to store backup applications, etc., backup system 200 may have a relatively small form factor, such as a pocket-sized or dongle, or may Embedded in some other device configuration such as a joint or bracket.

The backup system 200 may also include a removable storage device interface 230 to allow a removable storage device 240 including a writable data storage medium to be attached externally to the data backup system 200 through the communication port 250 . Removable storage device interface 230 provides communication between emulation component 140 and removable storage device 240 . In some embodiments, removable storage device interface 230 is configured to support removable devices with integrated media such as flash memory devices or HDDs. In other embodiments, the removable device may be a device that accepts removable media, such as a CD drive.

It should be appreciated that the removable storage device interface 230 is optional because the copied files do not necessarily have to be stored to a storage device associated with the data backup system 200 . Alternatively, the backup application may direct the copied files to be stored to an existing internal or external drive of the data source or to a network drive. In another option, the backup application can send the copied files over an Internet (Internet) connection for storage on a network-based storage device.

It should be noted that, for example, while some embodiments do not include a display to reduce cost and increase the durability of the backup system 100, 200, the backup system 100, 200 may include a display or other visual indicator such as a light emitting diode (LED) to show The output file is being copied. The backup system 100 , 200 may use batteries, an external power source (eg, an AC power outlet), or power provided by the data source 110 . In some embodiments, the connection 120 is a cable that is part of the backup system 100 , 200 . The backup system 100, 200 may also be configured as a cradle designed to accept a removable device 240 or a data source 110, where the data source 110 is a consumer electronic device such as a digital camera.

FIG. 3 is a flowchart of an exemplary method 300 for backing up data files from a data source. Method 300 includes providing a data backup system (310) including a storage device storing a backup application, connecting the data backup system to a data source to automatically load the backup application (320), and selectively copying data files from the data source ( 330).

Providing a data backup system ( 310 ) may include providing data backup system 100 or data backup system 200 , for example. In those embodiments that provide data backup system 200 , providing data backup system 200 ( 310 ) may include connecting removable storage device 240 to communication port 250 , for example. Where the removable storage device 240 is, for example, an SD or CF memory card, connecting the removable storage device 240 to the communication port 250 may include inserting the memory card into the communication port 250 . Alternatively, where removable storage device 240 is an HDD, connecting removable storage device 240 to communication port 250 may include coupling communication port 250 to removable storage device 240 using a connection such as a cable or a wireless link. .

Referring to data backup system 100 , 200 , connecting ( 320 ) data backup system 100 , 200 to data source 110 may include coupling communication interface 130 to data source 110 using connection 120 . Connecting (320) the data backup system to the data source also includes the data source identifying the data backup system as two new devices. For example, some operating systems periodically ask for unused ports for newly attached hardware. An exemplary process by which the data source 110 recognizes the data backup systems 100, 200 as two attached devices is described below with reference to FIG. 4 .

Connecting the data backup system to the data source (320) automatically loads the backup application. Operating systems that include auto-execute functionality, such as the autorun capability of the Windows operating system, can execute applications residing on autoloaded devices. Here, the auto-execute function of the operating system of the data source recognizes the backup application as an application to be loaded, and automatically loads the backup application to run on the data source.

As discussed above with respect to the functionality of the emulation component 140, as communications pass between the data source and the data backup system, connecting the data backup system to the data source (320) also includes translating between commands and responses in a variety of device formats . Thus, for example, a CD read command sent to the backup system 100 is translated into an HDD read command before being sent to the first logical storage area 160 .

Selectively copying (330) the data files from the data source may include running a backup application on the data source, where the backup application is configured to search one or more storage devices associated with the data source. In some embodiments, the backup application can search directories of internal storage devices, external storage devices, and network drives accessible by the data source. The backup application selectively copies the files to a storage device including a writable data storage medium such as the second logical storage area 170 or the removable storage device 240 .

The backup application selects files that meet certain predetermined criteria, such as file type (eg, .jpg) or content type (eg, audio files), and in some embodiments only copies files that were not previously copied. Other examples of content types include email, business application data (e.g., Accpac and Simple Accounting files), digital video files, eBook files, contacts files, calendar files, text files, task files, settings files, bookmark files, and passwords document. Selectively copying data files (330) may also include searching for files meeting predetermined criteria by searching email attachments and files embedded within other files such as compressed files within .zip files. In some embodiments, the backup application may create a file path or directory structure on the writable data storage medium of the data backup system to indicate the location of the copied files at the data source.

It should be appreciated that according to the method 300, user involvement can be reduced to simply establish a physical connection between the data backup system and the data source. While user involvement can be reduced to one or more simple operations, it should be appreciated that the options can be presented to the user on the display device of the data source through a graphical user interface (GUI) provided by the backup application. This allows the user to customize the backup process by specifying search criteria such as the type of content or the type of files to copy, if desired. Additionally, the user can limit the scope of the backup process by drive, directory, folder, file type, file size or date/time stamp, or the user can deselect the type of content or specific files, drives, directories or folders such as temporary or a folder of the Internet Explorer directory.

As mentioned, selectively copying data files (330) from a data source may include running a backup application on the data source. In addition to the above-described functions of the backup application, the backup application may be configured to perform the following functions as part of selectively copying data files (330). For example, as long as the backup system remains connected to the data source 110, the backup application may wait for a predetermined length of time and then repeat the backup process. The backup application can also perform self-diagnostic routines at predetermined intervals. The backup application can also be configured to wait a predetermined period of time before performing an automatic backup in order to provide the user with the opportunity to customize the backup process. Additionally, the backup application can be configured to selectively copy data files (330) only upon receipt of a user command rather than automatically and selectively copy data files (330). User commands may be entered through a GUI on the data source, or may be provided through buttons or switches on the data backup system. Alternatively, the backup application may be configured to selectively copy the data files whenever the removable storage device 240 is connected to the communication port 250 (330).

In some embodiments, copying the data file (330) includes determining whether the data source was previously paired with the data backup system (eg, the data source was previously backed up using the data backup system). For example, this may include searching for marks previously left on the data source, or comparing marks held on the data backup system with an identifier of the data source, such as a volume label. Tags allow backup applications to identify data sources. In some embodiments, the backup application determines the course of action based on whether the data source was previously paired with the data backup system, and if so, whether the data backup system has stored data associated with the data source. For example, the course of action may be an automatic full or incremental backup of the data source, restoring backed up data to the data source, or asking the user to choose between these or other alternatives.

4 is a flowchart of an exemplary method 400 by which, once a data backup system is detected, is identified by a data source as two attached devices. Although this exemplary method 400 is described with reference to the USB protocol, it should be understood that other protocols, such as FireWire, may be similarly processed. Method 400 includes the data source enumerating the data backup system (410), followed by initialization of a simulation component of the data backup system to represent two logical unit numbers (420).

An enumeration of the data backup systems is performed (410) to identify newly attached hardware, the data backup system in this case, and how to configure the hardware for communication. Enumeration (410) includes the data source assigning a unique device number and querying the data backup system for the device descriptor. The emulation component responds by providing the device descriptor to the data source. The enumeration (410) also includes the address of the data source setting data backup system. When the address has been set, the data backup system obtains the communication frame assigned to the address. Enumeration (410) may also include the data source requesting and receiving detailed device information, such as class, subclass, and protocol, from the data backup system, specifically from the simulation component, and from the data backup system, specifically from the simulation component.

Enumeration (410) also includes the data source starting a suitable USB mass storage class driver, which requests the LUN from the data backup system with a "get maximum logical unit number" (GET MAX LOGICALUNIT NUMBER) command number. The enumeration (410) also includes the data backup system and more specifically the emulation component responding to the "get max logical unit count" command by transferring two LUNs to the data source.

Representing the two LUNs by initialization (420) includes the emulation component receiving a plurality of SCSI commands directed to each LUN from the data source. The emulation component handles each LUN independently. The emulation component responds to those SCSI commands it recognizes, and generates standard error conditions in response to unrecognized SCSI commands. Each SCSI command and any resulting errors are normally processed before the next SCSI command is issued to each LUN. It should be appreciated that the sequence of SCSI commands sent to a LUN representing a storage device comprising a writable data storage medium may be different from the sequence of SCSI commands sent to a LUN representing an automount device. In addition, a SCSI command or a sequence of SCSI commands can be repeated multiple times by the data source, and a sequence of SCSI commands directed to two LUNs can be interleaved.

For both LUNs, the sequence of SCSI commands begins with the USB mass storage class driver issuing an "INQUIRY" command to identify the device type. The emulation component returns a response to represent a storage device, such as second logical storage area 170 (FIG. 1), as a storage device that includes a writable data storage medium. A response such as "0x00" indicates that the storage device is an HDD. Similarly, the emulation component returns a response to represent a storage device, such as first logical storage area 160 (FIG. 1), as an autoload device. A response such as "0x05" indicates that the autoload device is a CD drive. Storage devices including writable data storage media may also be marked as "removable" or "non-removable," while autoloading devices may be marked as "removable." After this, the sequence of SCSI commands for the two LUNs is separated. It should be appreciated that the order of the SCSI commands in the sequence described below is exemplary and that the order of the SCSI commands will vary with different data sources. Also, in some examples, one or more of the SCSI commands provided below may be omitted and/or other SCSI commands may be included.

The exemplary sequence of SCSI commands directed to a storage device comprising a writable data storage medium continues with a "READ FORMAT CAPACITIES" request by the data source to determine whether the writable data storage medium is unformatted. Typically, the medium of the represented storage device has been formatted, and the emulation component responds accordingly. Otherwise, the data source will attempt to format the storage device's media. Next, the data source issues a READ CAPACITY request to identify the capacity of the writable data storage medium and its block size, and the emulation component returns this information as well. A "READ(10)" command is issued to read the first block on the writable data storage medium. The first block has a Logical Block Addressing (LBA) value of zero (LBA=0) and includes a Master Boot Record (MBR), which itself includes the partition table of the writable data storage medium. The simulation component responds with the contents of the requested chunk.

Then, use the "mode read (6)" (MODE SENSE (6)) command to extract the capabilities of the storage device including the writable data storage medium, such as whether the storage device includes a disk cache. The emulation component responds appropriately to the capabilities of the represented storage device. Issue another "read(10)" command to restore the first block of the file system including the root directory. The first block of the file system may be located at LBA=0x3F, for example, but may vary depending on the particular type of file system represented. The emulation component returns the first block of the file system. Finally, the data source can issue a "TEST UNIT READY" request before reading the entire contents of the root directory, etc. Here, the emulation component responds affirmatively, such that the data source considers the storage device including the writable data storage medium operational. Thereafter, the data source issues more read/write requests as needed.

The exemplary sequence of SCSI commands directed to an autoloader continues to a "Get Configuration" (GET CONFIGURATION) request to obtain information about the capabilities of the autoloader and its support for e.g. CD-R, CD-RW, recordable digital video The ability to read or write to different types of optical media such as compact disc (DVD+R), DVD-RW, etc. The simulation component responds with the appropriate capabilities for the autoload facility represented by the data source. This is followed by a "read capacity" request to show if media is present in the autoloader. The emulation component is configured to respond by failing the initial attempt. In response, the data source will issue a "request read" (REQUEST SENSE) command to access extended error information. In response, the emulation component sets the "readout key" to "UNITATTENTION" and the "additional readout code" to "POWER ON". The data source will then repeat the "read capacity" request, and the emulation component responds with a capacity such as the size of the first logical storage area 160 (FIG. 1).

To learn the types of state change events supported by a read-only media device, the data source issues an initial GET EVENT STATUS NOTIFICATION request, and the emulation component responds with a set of encoded status fields. Then, the data source can repeat the "get notified of event status" request in case a field that is set as a status entry is to be checked. For example, if the operational status field is enabled, the simulation component responds with an operational change event and a status code indicating a feature change. This response may trigger the data source to issue a further "get configure" request to show which feature changes, if any.

The data source can also issue a "MODESENSE (10)) request for the page code (0x2A), known as the "MM Capabilities and Mechanical Status Page". The emulation component will respond with information representative of a simple autoloader including read-only support for CD-R and CD-RW media. This is in response to information returned in response to a "get configured" request.

Here, the data source can issue a "test unit ready" command. This triggers two sequences of request/response events in a simulation component that can support the autoexecution functionality of different operating systems. Commands in the two sequences can be interleaved, and events will remain pending until the simulation component has passed through all desired states. As outlined below, these two sequences are typical for operating systems such as Windows XP. In the following, the sequence does not specify the number of times the request or the sequence of requests may be repeated. Also, the specific sequence of events may vary depending on the type and version of the operating system executing on the data source. Additional or alternative commands may also be issued.

The first sequence consists of a series of "test unit ready" commands from the data source to the autoloader. The emulation component is configured to fail the first request. The data source then sends a "request read" command to get extended error information, and in case of an additional read code of "no medium present", the emulation component sets the read key to "NOT READY" . The data source then repeats the "test cell ready" command, which the simulation component fails again. The data source again issues a "request read" command and the simulation component responds with a read key set to "unit attention" and an additional read code of "MEDIUM MAY HAVE CHANGED". All subsequent "test unit ready" commands normally respond without errors.

The second sequence consists of a series of "get event status notification" requests from the data source to the autoloading device. After triggering the first "test cell ready" command of the first sequence, the data source issues a "get event status notification" request with the operation change field enabled. The simulated components respond with status codes and operational change events that represent feature changes. For subsequent "Get Notified of Event Status" requests, the Media Status field is enabled. The emulation component responds with a media event, a status code indicating new media, and a flag set to indicate the presence of media. For all subsequent "get event status notification" requests when the media status field is enabled, the emulation component responds with a media event and the media present flag is set, but the status code does not indicate new media. In the case of a "Get Notified of Event Status" request and the desired status field is not enabled, the simulation component responds appropriately to the current status of the event.

At the end of either or both of these sequences, the data source can send a "READ TOC/PMA/ATIP" (READ TOC/PMA/ATIP) request to read content from the autoloader's media Table of Contents (TOC). The TOC includes information about the number of tracks on the medium and the starting position of each track. The simulation component responds with a default configured entry of a single data track that starts immediately after being brought into the region. The default TOC states that the first block of data on the media starts at address zero. The location of the last track is fixed in the emulation component and represents the space allocated for data on autoloaded devices such as backup applications.

When a data source makes an autoloader read request, the emulation component automatically translates the logical address into the corresponding physical address of the storage device represented as the autoloader (eg, the first logical storage area 160 (FIG. 1)). In addition, when the block size of a storage device (such as a HDD partition) represented as an autoloader device (such as a CD drive) is different, the emulation component also translates the amount of autoloader data required into blocks on the storage device Appropriate number.

After method 400 ends, the data source identifies one LUN as an automount device and the other LUN as a storage device comprising a writable data storage medium, and is appropriately configured to communicate with each device independently. Thereafter, selective copying of data files from the data source can begin (330). As mentioned above, this may include the operating system of the data source automatically loading the backup application from the LUN denoted as automount device, and writing selected data from the data source to the storage device denoted as storage device comprising writable data storage media LUNs.

In the foregoing specification, the invention has been described with reference to specific embodiments, but those skilled in the art will recognize that the invention is not limited to the disclosed embodiments. The various features and aspects of the invention described above can be used alone or in combination. Furthermore, the present invention may be employed in any environment and application other than those described herein without departing from the broad spirit and scope of this specification. Accordingly, the specification and drawings are to be regarded as illustrative rather than restrictive. It should be recognized that the terms "including", "comprising" and "having" used herein should be specifically understood as open-ended technical terms.

Claims (25)

1. emulation component that between the data source of the memory device of first device type and operation system, uses, described emulation component comprises:

Be configured to return the logical unit of response from the inquiry of described data source, it is second device type that described memory device is indicated in described response, and described second device type belongs to trigger the kind equipment type of described operating system with the application program of automatic load store on described memory device when being connected to described data source.

2. emulation component according to claim 1, wherein said inquiry are the small computer system interface inquiry commands.

3. emulation component according to claim 1, wherein said first device type is a hard disk drive.

4. emulation component according to claim 3, wherein said second device type is a CD drive.

5. emulation component according to claim 3, wherein said second device type is the digital video disk driver.

6. emulation component according to claim 1, wherein said logical unit comprises firmware.

7. emulation component that between the data source and first memory device, uses, described emulation component comprises:

Be configured to first logical storage with described first memory device and be expressed as logical unit from moving loading equipment; And

Be configured to second logical storage of described first memory device is expressed as the logical unit of second memory device that comprises writable data storage medium.

8. emulation component according to claim 7 also comprises:

Be configured to receive from described data source to described from moving loading equipment carry out addressing from the moving loading equipment order, become first storage device commands and send the logical unit of described first storage device commands from the moving loading equipment command translation to described first logical storage with described; And

Be configured to receive first memory device response, will described first memory device response translate into and respond and send the described logical unit that responds described data source from moving loading equipment from moving loading equipment from described first logical storage.

9. emulation component according to claim 8 also comprises:

Be configured to receive described second memory device is carried out second storage device commands of addressing and sends the logical unit of described second storage device commands to described second logical storage from described data source; And

Second memory device that is configured to receive from described second logical storage responds and sends the logical unit that described second memory device responds described data source.

10. emulation component according to claim 7 wherein is configured to first logical storage with described first memory device and is expressed as described logical unit from moving loading equipment described first logical storage is expressed as CD drive.

11. emulation component according to claim 7 wherein is configured to first logical storage with described first memory device and is expressed as described logical unit from moving loading equipment described first logical storage is expressed as the digital video disk driver.

12. emulation component according to claim 7 wherein is configured to the logical unit that second logical storage with described first memory device is expressed as described second memory device described second logical storage is expressed as hard disk drive.

13. emulation component according to claim 7 wherein is configured to the logical unit that second logical storage with described first memory device is expressed as described second memory device described second logical storage is expressed as the secure digital storage card.

14. emulation component according to claim 7 wherein is configured to the logical unit that second logical storage with described first memory device is expressed as described second memory device described second logical storage is expressed as flash-storing card.

15. a data backup system comprises:

Communication interface;

First memory device that comprises writable data storage medium; And

The emulation component that between described first memory device and described communication interface, communicates, and described emulation component is configured to:

Described first memory device is expressed as from moving loading equipment;

Reception from data source to described from moving loading equipment carry out addressing from the moving loading equipment order, become first storage device commands with described from the moving loading equipment command translation, and send described first storage device commands to described first memory device; And

Reception is from the response of first memory device of described first memory device, will described first memory device response translates into from moving loading equipment to respond, and sends and describedly respond described data source from moving loading equipment.

16. data backup system according to claim 15 also comprises the movable memory equipment interface.

17. data backup system according to claim 16, wherein said emulation component also is configured to:

Reception is from the movable memory equipment order of described data source and send described movable memory equipment order to movable memory equipment, and the described movable memory equipment order pair described movable memory equipment that engages with described movable memory equipment interface carries out addressing; And

Reception send described movable memory equipment to respond described data source from the movable memory equipment response concurrent of described movable memory equipment.

18. data backup system according to claim 15, wherein said communication interface comprises the USB (universal serial bus) communication interface.

19. data backup system according to claim 15, wherein said communication interface comprises the live wire communication interface.

20. data backup system according to claim 15, wherein said first memory device comprises hard disk drive.

21. data backup system according to claim 15, wherein said first memory device comprises the secure digital storage card.

22. data backup system according to claim 15, wherein said first memory device comprises flash-storing card.

23. data backup system according to claim 15, wherein said emulation component is expressed as CD drive with described first memory device.

24. data backup system according to claim 15, wherein said emulation component is expressed as the digital video disk driver with described first memory device.

25. an emulation component that uses between the data source of the memory device of first device type and operation system, described emulation component comprises:

Be used for return the device of response from the inquiry of described data source, it is second device type that described memory device is indicated in described response, and described second device type belongs to trigger the kind equipment type of described operating system with the application program of automatic load store on described memory device when being connected to described data source.

Images