US20070299891A1 - Data back-up utility - Google Patents
Data back-up utility Download PDFInfo
- Publication number
- US20070299891A1 US20070299891A1 US11/474,711 US47471106A US2007299891A1 US 20070299891 A1 US20070299891 A1 US 20070299891A1 US 47471106 A US47471106 A US 47471106A US 2007299891 A1 US2007299891 A1 US 2007299891A1
- Authority
- US
- United States
- Prior art keywords
- data
- copy
- file
- destination
- configuration parameter
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1461—Backup scheduling policy
Definitions
- Embodiments are related to backing-up data in a computing environment. More particularly, the disclosed subject matter is related to computer-implemented methods, configurations, systems, and computer program products for configuring and deploying a data back-up application for ensuring safety of data based on user selectable configuration(s).
- Computing devices operate by consuming internally or externally stored data. Because computing devices and storage media are prone to malfunction, various data back-up systems are utilized. In an enterprise environment, where multiple users can access, consume, and modify shared data, ensuring security of the data is especially critical. Loss of data due to a computer crash, network malfunction, and the like, may result in loss of productivity.
- Some available data back-up systems may create back-up copies of entire hard drives. Copying large amounts of data is not only time consuming, but it can also tie up valuable system resources. Furthermore, each user in an enterprise system may have a different data usage profile. For example, one user may go through large amounts of data and modify files during a particular time of day, while another user may modify a small amount of data. A one-size-fits-all type back-up system may not necessarily address the needs of such users with different profiles.
- Embodiments are directed to determining a source and a destination for data to be backed up applying a configuration parameter determined by a user.
- the configuration parameter may include a frequency of the back-up, a filter to be applied for selecting data, and the like.
- the configuration parameter(s) may be user selected among options provided in a configuration user interface or entered by the user. Formatting and/or naming of data in the back-up copy may be modified from the original data to preserve system resources or to identify the original data from the back-up copy.
- FIG. 1 is a block diagram of an example computing operating environment
- FIG. 2 illustrates a system where example embodiments may be implemented
- FIG. 3 illustrates an example data back-up utility architecture according to embodiments
- FIG. 4 illustrates a screenshot of an example data back-up application configuration user interface (UI);
- FIG. 5 illustrates a screenshot of an example data back-up application status UI
- FIG. 6 illustrates a logic flow diagram for a process of backing-up data based on user selectable configuration(s) according to one embodiment.
- a data back-up utility may be provided performing data back-up based on user selectable configurations.
- references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. These aspects may be combined, other aspects may be utilized, and structural changes may be made without departing from the spirit or scope of the present disclosure. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.
- FIG. 1 and the following discussion are intended to provide a brief, general description of a suitable computing environment in which the invention may be implemented. While the embodiments will be described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a personal computer, those skilled in the art will recognize that aspects may also be implemented in combination with other program modules.
- program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
- embodiments may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
- Embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
- program modules may be located in both local and remote memory storage devices.
- Embodiments may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media.
- the computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process.
- the computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process.
- one example system for implementing the embodiments includes a computing device, such as computing device 100 .
- Computing device 100 may typically include a main processing device 102 and system memory 104 .
- the system memory 104 may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two.
- System memory 104 typically provides an environment for an operating system 106 to be executed for controlling the operation of computing device 100 and execution of other programs (applications).
- Software applications 108 such as program modules and back-up application 120 are examples of programs or program modules that may be executed under the control of operating system 106 in system memory 104 . Additional operating systems or programs may also be executed within system memory 104 outside the control of operating system 106 .
- Back-up application 120 enables a user to back up data from specified sources to specified destinations such as internal or external hard drives, virtual drives, portable storage devices, and the like, based on user selectable configurations such as timing of the back-up process, filters to be applied, and the like.
- Back-up application 120 may be an integrated part of a file management application or a separate application. Back-up application 120 may communicate with other applications running on computing device 100 or on other devices. Furthermore, back-up application 120 may be executed in an operating system other than operating system 106 .
- the computing device 100 may have additional features or functionality.
- the computing device 100 may also include data storage devices 110 (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape.
- Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.
- System memory 104 and storage devices 110 are examples of computer storage media.
- Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computing device 100 . Any such computer storage media may be part of device 100 .
- Computing device 100 may also include input device(s) 112 such as a keyboard, a mouse, a pen, a voice input device, a touch input device, etc. Furthermore, output device(s) 114 such as a display, a speaker, a printer, etc. may also be included. These devices are well known in the art.
- Communication connections 116 may be included in computing device 100 to allow the device to communicate with other computing devices 118 , such as over a network in a distributed computing environment, for example, an intranet or the Internet.
- Communication connection 116 exemplifies various communication media.
- Communication media may be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and include any information delivery media.
- communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
- wired media such as a wired network or direct-wired connection
- wireless media such as acoustic, RF, infrared and other wireless media.
- computer readable media refers to both storage media and communication media.
- System 200 may comprise any topology of servers, clients, Internet service providers, and communication media. Also, system 200 may have a static or dynamic topology.
- client may refer to a client application or a client device employed by a user to perform business logic operations.
- Back-up service 202 may be one or more programs or a server machine executing programs associated with the server tasks. Both clients and application servers may be embodied as single device (or program) or a number of devices (programs).
- data sources may include one or more data stores, input devices, and the like.
- the back-up application 120 may be run centrally on back-up service 202 or in a distributed manner over several servers and/or client devices.
- Back-up service 202 may include implementation of a number of data management systems such as data storage, data refreshing, data maintenance scheduling, and the like, in addition to back-up application 120 .
- a number of other applications may also be configured, deployed, and shared in system 200 .
- the back-up application 120 may also be run in one or more client devices and information exchanged over network(s) 210 .
- Data store 212 is an example of a number of data stores that may be utilized to store back-up copies of the data.
- Data store 212 may be managed by data storage server 204 or directly accessed by back-up service 202 or any one of the clients.
- back-up service 202 running the back-up application 120 from client devices 222 , 224 , 226 , and 228 over network(s) 210 .
- portions or all of the back-up application 120 may reside on any one of the client devices 222 , 224 , 226 , and 228 .
- data may be stored in data store 212 without an involvement of back-up service 202 .
- users may be provided one or more user interfaces (“UIs”) to select and define configurations associated with backing up the data such as actions of back-up service 202 , data store 212 , and the like.
- UIs user interfaces
- User selectable configuration of the back-up service 202 may enable different users to configure the process for increased efficiency.
- Network(s) 210 may include a secure network such as an enterprise network, or an unsecure network such as a wireless open network. Network(s) 210 provide communication between the nodes described above.
- network(s) 210 may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
- Back-up application 120 may be executed in any topology of processing systems, storage systems, source systems, and configuration systems.
- back-up utility 314 A core of back-up application 120 is back-up utility 314 .
- Back-up utility 314 may be an integral or associated part of a data management application such as back-up application 120 .
- back-up application 120 may perform tasks in addition to those performed by the back-up utility 314 .
- back-up application 120 may also facilitate communication between various servers and clients, offer a calendar service, issue alerts based on back-up status, and the like.
- Back-up utility 314 may receive configuration input from user interface(s) 312 for user selectable options of the back-up application 120 .
- Such options may include, but are not limited to, source and destination information for data to be backed-up, a frequency of back-up, any filters to be applied, and the like.
- User configuration of the back-up application 120 is discussed in further detail below in conjunction with FIG. 4 .
- Back-up utility 314 may retrieve data to be backed up from files or directories 316 . Depending on the user selectable configuration(s), data may be retrieved in files or directories containing files. Data formats to be backed up are not limited to files or, directories, however. Other data types including, but not limited to, data streams (e.g. audio stream), data chunks, and the like may also be backed up by back-up utility 314 .
- data streams e.g. audio stream
- data chunks e.g. audio stream
- back-up utility 314 first determines whether or not a back-up copy of a particular piece of data (e.g. a file) exists in the destination storage. If the back-up copy exists, the back-up utility 314 performs a comparison to determine whether the source file is different from the back-up copy before attempting the back-up. If the back-up copy does not exist, no comparison is necessary.
- a next step in the operation of back-up application 120 includes the back-up utility 314 determining whether the source file is accessible. A file may not be accessible due to another application currently consuming the file, a network condition, and the like. To prevent an error and preserve system resources, the back-up utility program 314 may abort attempting to copy the source file if it is currently not accessible. The back-up utility 314 may continue backing up other files and check the inaccessible file(s) at predetermined intervals. The steps described above may be implemented in different orders as well.
- the back-up utility 314 stores the back-up data in a number of destinations.
- Storage destinations may include physical or virtual storage facilities such as hard drives, network drives, portable storage devices, other computing devices, CD-ROMs, tapes, and the like.
- the storage facilities may be internal or external.
- Internal storage 318 represents any storage medium that is an integral part of a computing device or system ( 310 ), which includes back-up utility 314 , and the data source.
- the data source may be external to system 310 .
- External storage destinations are represented in FIG. 3 by example devices external hard drive 322 , other computing device 324 , and portable storage 326 .
- many other storage media may be used to store the back-up data.
- the back-up data may be stored in the same format as the original data or it may be reformatted according to other embodiments. For example, data files may be combined or compressed for efficient use of storage resources.
- stored back-up data may be designated the same way as the original data (e.g. file names preserved) or a different designation used for ease of tracking, and the like (e.g. renaming the files using a time stamp associated with the back-up process).
- back-up application 120 may implement user credentials and/or permission levels based filtering to determine which files (or directories) can be backed up or which destinations can be used for back up purposes.
- a frequency of back-up may also be based on user credentials and/or permission levels to manage system resources. For example, programmers in an enterprise system may be allowed to back up all files associated with programming, while financial staff may be allowed to back up financial data files only.
- back-up utility 314 may interact with other applications that receive information associated with the back-up application 120 and provide services such as reports, analyses, alerts, and the like.
- Other applications may include a graphical representation application, a database application, a data analysis application, a communications application, an alerting application, and the like.
- FIG. 4 illustrates a screenshot of an example data back-up application configuration UI 400 .
- UI 400 includes path designations 402 and 404 for a user to define the paths for the source and destination of the back-up data, respectively.
- the paths may include directory paths within a computing device or network system, URLs, and the like.
- Portion 406 of UI 400 is an example of user options for defining a frequency of a back-up service.
- the frequency may be defined as on demand, when change is detected, at preset intervals (user may be given options for the interval), and the like. Other types of frequency definitions may also be implemented using the principles described herein.
- Filters 408 may be used to restrict data to be backed up. For example, the user may be prompted to specify or select from a set of file types to include only those selected file types in field 410 . Similarly, selected file types may also be specified in field 412 to be excluded from the list of data to be backed up.
- additional filters such as defining whole or partial file names to be included or excluded, defining date ranges for changes to files, defining persons who generated or modified the files, and the like, may be implemented as well.
- a filter such as the “Do Not Look In Sub-Directories” 414 may be used to limit source paths to top level directories only.
- the user may be provided an option to specify a number of directory levels for source data.
- FIG. 5 illustrates a screenshot of an example data back-up application status UI 500 according to embodiments.
- UI 500 includes a listing ( 512 ) of user defined data transfers or back-ups in transfers form 502 .
- a logs form 504 (only the tab is shown in the figure) may present a log of past back-ups an statistics associated with the past back-ups.
- the user may select a back-up service from the list (e.g. by clicking on the transfer) and be provided with the configuration UI associated with that transfer.
- a “New Transfer” icon 506 enables the user to start a new back-up process defining or using default values for configuration items discussed above.
- “Backup All” icon 508 enables the user to initiate a back-up of all data associated with the computing device 100 and/or the user to predefined destination(s).
- a “Shutdown Application” icon 510 is provided to terminate the back-up application 120 .
- a status UI may include additional information such as statistical information associated with the back-up(s), information associated with related applications such as those described in conjunction with FIG. 3 , and the like.
- FIGS. 4 and 5 are shown with example elements, embodiments are not so limited. Other elements such as additional filters, frequency definitions, and formats of presenting those elements may be implemented using the principles described herein.
- back-up application 120 back-up utility 314
- UIs in FIGS. 4 through 6 are intended for illustration purposes only and should not be construed as a limitation on embodiments. Other embodiments may be implemented without departing from a scope and spirit of the invention.
- FIG. 6 illustrates a logic flow diagram for a process 600 of backing-up data based on user selectable configuration(s) according to one embodiment.
- Process 600 may be implemented in a data management application such as a back-up application as described in FIGS. 1 and 2 .
- Process 600 begins with optional operation 602 , where back-up application 120 receives configuration information from a user interface.
- the configuration information may be predetermined based on the computing device, user credentials, and the like. Processing moves from optional operation 602 to operation 604 .
- the back-up application 120 compares the source data to the destination data. If a back-up copy of the source data does not exist at the back-up destination, no further investigation may be necessary. If a back-up copy does exist at the destination, a further comparison may be performed to determine if the source data is different from the back-up copy (e.g. file has been modified). Processing advances from operation 604 to decision operation 606 .
- the back-up application 120 determines whether the data is accessible. As described previously, source data may be temporarily or permanently inaccessible due to being consumed by another application, a source condition, a network condition, and the like. If data is not accessible, processing returns to operation 604 . If data is accessible, processing continues to optional operation 608 .
- the back-up application 120 applies one or more filters.
- a number and an order of filters to be applied may be user defined, based on a default set of rules, or a combination of the two. Processing moves from optional operation 608 to operation 610 .
- the back-up application 120 creates a back-up copy of the source data (transfer). As described previously, formatting, naming, and other properties of the source data may be modified in conjunction with the back-up application 120 . After operation 610 , processing moves to a calling process for further actions.
- process 600 is for illustration purposes. Backing up data based on user selectable configurations may be implemented by similar processes with fewer or additional steps, as well as in different order of operations using the principles described herein.
Abstract
Description
- Embodiments are related to backing-up data in a computing environment. More particularly, the disclosed subject matter is related to computer-implemented methods, configurations, systems, and computer program products for configuring and deploying a data back-up application for ensuring safety of data based on user selectable configuration(s).
- Computing devices operate by consuming internally or externally stored data. Because computing devices and storage media are prone to malfunction, various data back-up systems are utilized. In an enterprise environment, where multiple users can access, consume, and modify shared data, ensuring security of the data is especially critical. Loss of data due to a computer crash, network malfunction, and the like, may result in loss of productivity.
- Some available data back-up systems may create back-up copies of entire hard drives. Copying large amounts of data is not only time consuming, but it can also tie up valuable system resources. Furthermore, each user in an enterprise system may have a different data usage profile. For example, one user may go through large amounts of data and modify files during a particular time of day, while another user may modify a small amount of data. A one-size-fits-all type back-up system may not necessarily address the needs of such users with different profiles.
- Consistent with embodiments described herein, systems and methods are disclosed for providing a data back-up utility in computing systems. Key features or essential features of the claimed subject matter are not necessarily identified in this summary portion.
- Embodiments are directed to determining a source and a destination for data to be backed up applying a configuration parameter determined by a user. The configuration parameter may include a frequency of the back-up, a filter to be applied for selecting data, and the like. The configuration parameter(s) may be user selected among options provided in a configuration user interface or entered by the user. Formatting and/or naming of data in the back-up copy may be modified from the original data to preserve system resources or to identify the original data from the back-up copy.
- It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only, and should not be considered restrictive of the scope of the invention, as described and claimed. Further, features and/or variations may be provided in addition to those set forth herein. For example, embodiments of the invention may be directed to various combinations and sub-combinations of the features described in the detailed description.
-
FIG. 1 is a block diagram of an example computing operating environment; -
FIG. 2 illustrates a system where example embodiments may be implemented; -
FIG. 3 illustrates an example data back-up utility architecture according to embodiments; -
FIG. 4 illustrates a screenshot of an example data back-up application configuration user interface (UI); -
FIG. 5 illustrates a screenshot of an example data back-up application status UI; and -
FIG. 6 illustrates a logic flow diagram for a process of backing-up data based on user selectable configuration(s) according to one embodiment. - As briefly described above, a data back-up utility may be provided performing data back-up based on user selectable configurations. In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. These aspects may be combined, other aspects may be utilized, and structural changes may be made without departing from the spirit or scope of the present disclosure. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.
- Referring now to the drawings, aspects and an exemplary operating environment will be described.
FIG. 1 and the following discussion are intended to provide a brief, general description of a suitable computing environment in which the invention may be implemented. While the embodiments will be described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a personal computer, those skilled in the art will recognize that aspects may also be implemented in combination with other program modules. - Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that embodiments may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. Embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
- Embodiments may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process.
- With reference to
FIG. 1 , one example system for implementing the embodiments includes a computing device, such ascomputing device 100.Computing device 100 may typically include amain processing device 102 andsystem memory 104. Thesystem memory 104 may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two.System memory 104 typically provides an environment for anoperating system 106 to be executed for controlling the operation ofcomputing device 100 and execution of other programs (applications).Software applications 108 such as program modules and back-upapplication 120 are examples of programs or program modules that may be executed under the control ofoperating system 106 insystem memory 104. Additional operating systems or programs may also be executed withinsystem memory 104 outside the control ofoperating system 106. Back-upapplication 120 enables a user to back up data from specified sources to specified destinations such as internal or external hard drives, virtual drives, portable storage devices, and the like, based on user selectable configurations such as timing of the back-up process, filters to be applied, and the like. - Back-
up application 120 may be an integrated part of a file management application or a separate application. Back-upapplication 120 may communicate with other applications running oncomputing device 100 or on other devices. Furthermore, back-upapplication 120 may be executed in an operating system other thanoperating system 106. - The
computing device 100 may have additional features or functionality. For example, thecomputing device 100 may also include data storage devices 110 (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.System memory 104 andstorage devices 110 are examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed bycomputing device 100. Any such computer storage media may be part ofdevice 100. -
Computing device 100 may also include input device(s) 112 such as a keyboard, a mouse, a pen, a voice input device, a touch input device, etc. Furthermore, output device(s) 114 such as a display, a speaker, a printer, etc. may also be included. These devices are well known in the art. -
Communication connections 116 may be included incomputing device 100 to allow the device to communicate withother computing devices 118, such as over a network in a distributed computing environment, for example, an intranet or the Internet.Communication connection 116 exemplifies various communication media. Communication media may be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and include any information delivery media. - By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. The term computer readable media as used herein refers to both storage media and communication media.
- Referring to
FIG. 2 , asystem 200 where example embodiments may be implemented, is illustrated.System 200 may comprise any topology of servers, clients, Internet service providers, and communication media. Also,system 200 may have a static or dynamic topology. The term “client” may refer to a client application or a client device employed by a user to perform business logic operations. Back-upservice 202 may be one or more programs or a server machine executing programs associated with the server tasks. Both clients and application servers may be embodied as single device (or program) or a number of devices (programs). Similarly, data sources may include one or more data stores, input devices, and the like. - The back-up
application 120 may be run centrally on back-upservice 202 or in a distributed manner over several servers and/or client devices. Back-upservice 202 may include implementation of a number of data management systems such as data storage, data refreshing, data maintenance scheduling, and the like, in addition to back-upapplication 120. A number of other applications may also be configured, deployed, and shared insystem 200. In addition, the back-upapplication 120 may also be run in one or more client devices and information exchanged over network(s) 210. -
Data store 212 is an example of a number of data stores that may be utilized to store back-up copies of the data.Data store 212 may be managed bydata storage server 204 or directly accessed by back-upservice 202 or any one of the clients. - Users may interact with back-up
service 202 running the back-upapplication 120 fromclient devices application 120 may reside on any one of theclient devices data store 212 without an involvement of back-upservice 202. - According to some embodiments, users may be provided one or more user interfaces (“UIs”) to select and define configurations associated with backing up the data such as actions of back-up
service 202,data store 212, and the like. User selectable configuration of the back-upservice 202 may enable different users to configure the process for increased efficiency. - Network(s) 210 may include a secure network such as an enterprise network, or an unsecure network such as a wireless open network. Network(s) 210 provide communication between the nodes described above. By way of example, and not limitation, network(s) 210 may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
- Many other configurations of computing devices, applications, and data storage may be employed to implement a back-up system with user selectable configurations.
- Now referring to
FIG. 3 , example data back-up utility architecture of back-upapplication 120 according to embodiments is illustrated. Back-upapplication 120 may be executed in any topology of processing systems, storage systems, source systems, and configuration systems. - A core of back-up
application 120 is back-uputility 314. Back-uputility 314 may be an integral or associated part of a data management application such as back-upapplication 120. On the other hand, back-upapplication 120 may perform tasks in addition to those performed by the back-uputility 314. For example, back-upapplication 120 may also facilitate communication between various servers and clients, offer a calendar service, issue alerts based on back-up status, and the like. - Back-up
utility 314 may receive configuration input from user interface(s) 312 for user selectable options of the back-upapplication 120. Such options may include, but are not limited to, source and destination information for data to be backed-up, a frequency of back-up, any filters to be applied, and the like. User configuration of the back-upapplication 120 is discussed in further detail below in conjunction withFIG. 4 . - Back-up
utility 314 may retrieve data to be backed up from files ordirectories 316. Depending on the user selectable configuration(s), data may be retrieved in files or directories containing files. Data formats to be backed up are not limited to files or, directories, however. Other data types including, but not limited to, data streams (e.g. audio stream), data chunks, and the like may also be backed up by back-uputility 314. - According to one embodiment, back-up
utility 314 first determines whether or not a back-up copy of a particular piece of data (e.g. a file) exists in the destination storage. If the back-up copy exists, the back-uputility 314 performs a comparison to determine whether the source file is different from the back-up copy before attempting the back-up. If the back-up copy does not exist, no comparison is necessary. A next step in the operation of back-upapplication 120 includes the back-uputility 314 determining whether the source file is accessible. A file may not be accessible due to another application currently consuming the file, a network condition, and the like. To prevent an error and preserve system resources, the back-uputility program 314 may abort attempting to copy the source file if it is currently not accessible. The back-uputility 314 may continue backing up other files and check the inaccessible file(s) at predetermined intervals. The steps described above may be implemented in different orders as well. - Once data is retrieved, the back-up
utility 314 stores the back-up data in a number of destinations. Storage destinations may include physical or virtual storage facilities such as hard drives, network drives, portable storage devices, other computing devices, CD-ROMs, tapes, and the like. The storage facilities may be internal or external.Internal storage 318 represents any storage medium that is an integral part of a computing device or system (310), which includes back-uputility 314, and the data source. In some embodiments, the data source may be external tosystem 310. - External storage destinations are represented in
FIG. 3 by example devices externalhard drive 322,other computing device 324, andportable storage 326. As mentioned above, many other storage media may be used to store the back-up data. The back-up data may be stored in the same format as the original data or it may be reformatted according to other embodiments. For example, data files may be combined or compressed for efficient use of storage resources. Similarly, stored back-up data may be designated the same way as the original data (e.g. file names preserved) or a different designation used for ease of tracking, and the like (e.g. renaming the files using a time stamp associated with the back-up process). - Furthermore, back-up
application 120 may implement user credentials and/or permission levels based filtering to determine which files (or directories) can be backed up or which destinations can be used for back up purposes. According to further embodiments, a frequency of back-up may also be based on user credentials and/or permission levels to manage system resources. For example, programmers in an enterprise system may be allowed to back up all files associated with programming, while financial staff may be allowed to back up financial data files only. - In some embodiments, back-up
utility 314 may interact with other applications that receive information associated with the back-upapplication 120 and provide services such as reports, analyses, alerts, and the like. Other applications may include a graphical representation application, a database application, a data analysis application, a communications application, an alerting application, and the like. -
FIG. 4 illustrates a screenshot of an example data back-upapplication configuration UI 400.UI 400 includespath designations -
Portion 406 ofUI 400 is an example of user options for defining a frequency of a back-up service. The frequency may be defined as on demand, when change is detected, at preset intervals (user may be given options for the interval), and the like. Other types of frequency definitions may also be implemented using the principles described herein. -
Filters 408 may be used to restrict data to be backed up. For example, the user may be prompted to specify or select from a set of file types to include only those selected file types infield 410. Similarly, selected file types may also be specified infield 412 to be excluded from the list of data to be backed up. - In other embodiments, additional filters such as defining whole or partial file names to be included or excluded, defining date ranges for changes to files, defining persons who generated or modified the files, and the like, may be implemented as well.
- In a data structure comprising directories and files within the directories, a filter such as the “Do Not Look In Sub-Directories” 414 may be used to limit source paths to top level directories only. In further embodiments, the user may be provided an option to specify a number of directory levels for source data.
-
FIG. 5 illustrates a screenshot of an example data back-upapplication status UI 500 according to embodiments.UI 500 includes a listing (512) of user defined data transfers or back-ups in transfers form 502. A logs form 504 (only the tab is shown in the figure) may present a log of past back-ups an statistics associated with the past back-ups. - According to some embodiments, the user may select a back-up service from the list (e.g. by clicking on the transfer) and be provided with the configuration UI associated with that transfer. A “New Transfer”
icon 506 enables the user to start a new back-up process defining or using default values for configuration items discussed above. “Backup All”icon 508 enables the user to initiate a back-up of all data associated with thecomputing device 100 and/or the user to predefined destination(s). Finally, a “Shutdown Application”icon 510 is provided to terminate the back-upapplication 120. - A status UI according to embodiments may include additional information such as statistical information associated with the back-up(s), information associated with related applications such as those described in conjunction with
FIG. 3 , and the like. - While the UIs of
FIGS. 4 and 5 are shown with example elements, embodiments are not so limited. Other elements such as additional filters, frequency definitions, and formats of presenting those elements may be implemented using the principles described herein. - Furthermore, the example implementations of back-up
application 120, back-uputility 314, and UIs inFIGS. 4 through 6 are intended for illustration purposes only and should not be construed as a limitation on embodiments. Other embodiments may be implemented without departing from a scope and spirit of the invention. -
FIG. 6 illustrates a logic flow diagram for aprocess 600 of backing-up data based on user selectable configuration(s) according to one embodiment.Process 600 may be implemented in a data management application such as a back-up application as described inFIGS. 1 and 2 . -
Process 600 begins withoptional operation 602, where back-upapplication 120 receives configuration information from a user interface. In some embodiments, the configuration information may be predetermined based on the computing device, user credentials, and the like. Processing moves fromoptional operation 602 tooperation 604. - At
operation 604, the back-upapplication 120 compares the source data to the destination data. If a back-up copy of the source data does not exist at the back-up destination, no further investigation may be necessary. If a back-up copy does exist at the destination, a further comparison may be performed to determine if the source data is different from the back-up copy (e.g. file has been modified). Processing advances fromoperation 604 todecision operation 606. - At
decision operation 606, the back-upapplication 120 determines whether the data is accessible. As described previously, source data may be temporarily or permanently inaccessible due to being consumed by another application, a source condition, a network condition, and the like. If data is not accessible, processing returns tooperation 604. If data is accessible, processing continues tooptional operation 608. - At
optional operation 608, the back-upapplication 120 applies one or more filters. A number and an order of filters to be applied may be user defined, based on a default set of rules, or a combination of the two. Processing moves fromoptional operation 608 tooperation 610. - At
operation 610, the back-upapplication 120 creates a back-up copy of the source data (transfer). As described previously, formatting, naming, and other properties of the source data may be modified in conjunction with the back-upapplication 120. Afteroperation 610, processing moves to a calling process for further actions. - The operations included in
process 600 are for illustration purposes. Backing up data based on user selectable configurations may be implemented by similar processes with fewer or additional steps, as well as in different order of operations using the principles described herein. - The above specification, examples and data provide a complete description of the manufacture and use of the composition of the embodiments. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims and embodiments.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/474,711 US20070299891A1 (en) | 2006-06-26 | 2006-06-26 | Data back-up utility |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/474,711 US20070299891A1 (en) | 2006-06-26 | 2006-06-26 | Data back-up utility |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070299891A1 true US20070299891A1 (en) | 2007-12-27 |
Family
ID=38874690
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/474,711 Abandoned US20070299891A1 (en) | 2006-06-26 | 2006-06-26 | Data back-up utility |
Country Status (1)
Country | Link |
---|---|
US (1) | US20070299891A1 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070276789A1 (en) * | 2006-05-23 | 2007-11-29 | Emc Corporation | Methods and apparatus for conversion of content |
US20080115071A1 (en) * | 2006-10-19 | 2008-05-15 | Fair Thomas T | System And Methods For Zero-Configuration Data Backup |
US20120296867A1 (en) * | 2011-04-19 | 2012-11-22 | Iphion B.V. | Method and system for file synchronization |
WO2013177482A1 (en) * | 2012-05-25 | 2013-11-28 | Symantec Corporation | Backup image duplication |
US20170006096A1 (en) * | 2013-12-18 | 2017-01-05 | Hewlett Packard Enterprise Development Lp | Data block transmission |
US9977912B1 (en) * | 2015-09-21 | 2018-05-22 | EMC IP Holding Company LLC | Processing backup data based on file system authentication |
US10102080B1 (en) * | 2015-06-30 | 2018-10-16 | EMC IP Holding Company LLC | Accessing de-duplication services from an application using a file system filter driver for backup and restore |
US10832299B1 (en) * | 2015-02-27 | 2020-11-10 | State Farm Mutual Automobile Insurance Company | Data bank for managing streams of personal data |
US20210247993A1 (en) * | 2020-02-06 | 2021-08-12 | EMC IP Holding Company LLC | True zero rto eliminating os and app load times |
US11243844B2 (en) * | 2019-08-29 | 2022-02-08 | Jmicron Technology Corp. | Method for enhancing speed of incremental backup, bridge device, and storage system |
Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020056031A1 (en) * | 1997-07-18 | 2002-05-09 | Storactive, Inc. | Systems and methods for electronic data storage management |
US6460055B1 (en) * | 1999-12-16 | 2002-10-01 | Livevault Corporation | Systems and methods for backing up data files |
US6526418B1 (en) * | 1999-12-16 | 2003-02-25 | Livevault Corporation | Systems and methods for backing up data files |
US6611850B1 (en) * | 1997-08-26 | 2003-08-26 | Reliatech Ltd. | Method and control apparatus for file backup and restoration |
US20030177435A1 (en) * | 2002-03-18 | 2003-09-18 | Robin Budd | End-to-end checksumming for read operations |
US6625623B1 (en) * | 1999-12-16 | 2003-09-23 | Livevault Corporation | Systems and methods for backing up data files |
US20040088331A1 (en) * | 2002-09-10 | 2004-05-06 | Therrien David G. | Method and apparatus for integrating primary data storage with local and remote data protection |
US20040111389A1 (en) * | 2002-12-09 | 2004-06-10 | Microsoft Corporation | Managed file system filter model and architecture |
US20040117344A1 (en) * | 2001-03-15 | 2004-06-17 | Qing Yang | Remote online information back-up system |
US6779003B1 (en) * | 1999-12-16 | 2004-08-17 | Livevault Corporation | Systems and methods for backing up data files |
US6847984B1 (en) * | 1999-12-16 | 2005-01-25 | Livevault Corporation | Systems and methods for backing up data files |
US6892288B2 (en) * | 2001-02-20 | 2005-05-10 | Serichol Blasco Jose Maria | System for making automatic backup copies of computer files when a personal computer is switched off |
US6976140B2 (en) * | 2002-05-24 | 2005-12-13 | Hitachi, Ltd. | Computer system and a method of replication |
US20060117048A1 (en) * | 2004-11-30 | 2006-06-01 | Microsoft Corporation | Method and system of synchronizing filter metadata after a restore |
US20060140070A1 (en) * | 2003-12-04 | 2006-06-29 | Teruhiro Shiono | Optical information reproduction device |
US20060190505A1 (en) * | 2005-02-18 | 2006-08-24 | Microsoft Corporation | System and method for using a file system to automatically backup a file as a generational file |
-
2006
- 2006-06-26 US US11/474,711 patent/US20070299891A1/en not_active Abandoned
Patent Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020056031A1 (en) * | 1997-07-18 | 2002-05-09 | Storactive, Inc. | Systems and methods for electronic data storage management |
US6611850B1 (en) * | 1997-08-26 | 2003-08-26 | Reliatech Ltd. | Method and control apparatus for file backup and restoration |
US6460055B1 (en) * | 1999-12-16 | 2002-10-01 | Livevault Corporation | Systems and methods for backing up data files |
US6526418B1 (en) * | 1999-12-16 | 2003-02-25 | Livevault Corporation | Systems and methods for backing up data files |
US6625623B1 (en) * | 1999-12-16 | 2003-09-23 | Livevault Corporation | Systems and methods for backing up data files |
US6704755B2 (en) * | 1999-12-16 | 2004-03-09 | Livevault Corporation | Systems and methods for backing up data files |
US6847984B1 (en) * | 1999-12-16 | 2005-01-25 | Livevault Corporation | Systems and methods for backing up data files |
US6779003B1 (en) * | 1999-12-16 | 2004-08-17 | Livevault Corporation | Systems and methods for backing up data files |
US6892288B2 (en) * | 2001-02-20 | 2005-05-10 | Serichol Blasco Jose Maria | System for making automatic backup copies of computer files when a personal computer is switched off |
US20040117344A1 (en) * | 2001-03-15 | 2004-06-17 | Qing Yang | Remote online information back-up system |
US20030177435A1 (en) * | 2002-03-18 | 2003-09-18 | Robin Budd | End-to-end checksumming for read operations |
US7003702B2 (en) * | 2002-03-18 | 2006-02-21 | Emc Corporation | End-to-end checksumming for read operations |
US6976140B2 (en) * | 2002-05-24 | 2005-12-13 | Hitachi, Ltd. | Computer system and a method of replication |
US20040093361A1 (en) * | 2002-09-10 | 2004-05-13 | Therrien David G. | Method and apparatus for storage system to provide distributed data storage and protection |
US20040088331A1 (en) * | 2002-09-10 | 2004-05-06 | Therrien David G. | Method and apparatus for integrating primary data storage with local and remote data protection |
US7246140B2 (en) * | 2002-09-10 | 2007-07-17 | Exagrid Systems, Inc. | Method and apparatus for storage system to provide distributed data storage and protection |
US20040111389A1 (en) * | 2002-12-09 | 2004-06-10 | Microsoft Corporation | Managed file system filter model and architecture |
US20060140070A1 (en) * | 2003-12-04 | 2006-06-29 | Teruhiro Shiono | Optical information reproduction device |
US20060117048A1 (en) * | 2004-11-30 | 2006-06-01 | Microsoft Corporation | Method and system of synchronizing filter metadata after a restore |
US20060190505A1 (en) * | 2005-02-18 | 2006-08-24 | Microsoft Corporation | System and method for using a file system to automatically backup a file as a generational file |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070276789A1 (en) * | 2006-05-23 | 2007-11-29 | Emc Corporation | Methods and apparatus for conversion of content |
US20080115071A1 (en) * | 2006-10-19 | 2008-05-15 | Fair Thomas T | System And Methods For Zero-Configuration Data Backup |
US20120296867A1 (en) * | 2011-04-19 | 2012-11-22 | Iphion B.V. | Method and system for file synchronization |
US9798627B2 (en) | 2012-05-25 | 2017-10-24 | Veritas Technologies Llc | Backup image duplication |
WO2013177482A1 (en) * | 2012-05-25 | 2013-11-28 | Symantec Corporation | Backup image duplication |
US9183094B2 (en) | 2012-05-25 | 2015-11-10 | Symantec Corporation | Backup image duplication |
US9274897B2 (en) | 2012-05-25 | 2016-03-01 | Symantec Corporation | Backup policy migration and image duplication |
US20170006096A1 (en) * | 2013-12-18 | 2017-01-05 | Hewlett Packard Enterprise Development Lp | Data block transmission |
US10832299B1 (en) * | 2015-02-27 | 2020-11-10 | State Farm Mutual Automobile Insurance Company | Data bank for managing streams of personal data |
US11941675B2 (en) | 2015-02-27 | 2024-03-26 | State Farm Mutual Automobile Insurance Company | Data bank for managing streams of personal data |
US10102080B1 (en) * | 2015-06-30 | 2018-10-16 | EMC IP Holding Company LLC | Accessing de-duplication services from an application using a file system filter driver for backup and restore |
US9977912B1 (en) * | 2015-09-21 | 2018-05-22 | EMC IP Holding Company LLC | Processing backup data based on file system authentication |
US11243844B2 (en) * | 2019-08-29 | 2022-02-08 | Jmicron Technology Corp. | Method for enhancing speed of incremental backup, bridge device, and storage system |
US20210247993A1 (en) * | 2020-02-06 | 2021-08-12 | EMC IP Holding Company LLC | True zero rto eliminating os and app load times |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20070299891A1 (en) | Data back-up utility | |
US8121981B2 (en) | Database snapshot management | |
US7290002B2 (en) | System-wide selective action management | |
JP5147840B2 (en) | Declarative Management Framework (DECLARATIVEMAAGEENTENTRAMEWORK) | |
US7904913B2 (en) | Management interface for a system that provides automated, real-time, continuous data protection | |
US8671080B1 (en) | System and method for managing data loss due to policy violations in temporary files | |
KR101099297B1 (en) | Method for managing file replication in applications | |
US8290997B2 (en) | File handling for naming conflicts | |
US10289286B2 (en) | Thing modeler for internet of things | |
US8726234B2 (en) | User-customized extensions for software applications | |
US20010029517A1 (en) | Application specific rollback in a computer system | |
US20090150866A1 (en) | Enforcing legal holds of heterogeneous objects for litigation | |
US20070244897A1 (en) | Methods and systems for change management for a group policy environment | |
WO2007067725A2 (en) | User defined event rules for aggregate fields | |
US9547724B2 (en) | Providing rule based analysis of content to manage activation of web extension | |
US20080301299A1 (en) | Automatically targeting and filtering shared network resources | |
RU2586872C2 (en) | Removal of corrupted styles from extensible markup language documents | |
CN108255994A (en) | A kind of database version management method based on database snapshot | |
US11775474B2 (en) | Systems and methods for implementing content aware file management labeling | |
US20140046910A1 (en) | Smart content optimizations based upon enterprise portal content meta-model | |
EP3494470B1 (en) | Retain locally deleted content at storage service | |
US20150172402A1 (en) | Employment of presence-based history information in notebook application | |
Kumar et al. | Modern Big Data processing with Hadoop: Expert techniques for architecting end-to-end Big Data solutions to get valuable insights | |
US7856450B2 (en) | Apparatus and method for distributing information between business intelligence systems | |
US20190324945A1 (en) | Content preservation and policy lock features to provide immutability for regulated compliance |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BELLSOUTH INTELLECTUAL PROPERTY CORPORATION, DELAW Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JOPP, JOHN;AMMAY, FELIX;HARRELL, AARON D.;REEL/FRAME:018014/0875;SIGNING DATES FROM 20060621 TO 20060623 Owner name: BELLSOUTH INTELLECTUAL PROPERTY CORPORATION, DELAW Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JOPP, JOHN;AMMAY, FELIX;HARRELL, AARON D.;SIGNING DATES FROM 20060621 TO 20060623;REEL/FRAME:018014/0875 |
|
AS | Assignment |
Owner name: AT&T INTELLECTUAL PROPERTY I, L.P., NEVADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T DELAWARE INTELLECTUAL PROPERTY, INC. (FORMERLY KNOWN AS AT&T BLS INTELLECTUAL PROPERTY, INC., WHICH WAS FORMERLY KNOWN AS AT&T INTELLECTUAL PROPERTY, INC., WHICH WAS FORMERLY KNOWN AS BELLSOUTH INTELLECTUAL PROPERTY CORPORATION);REEL/FRAME:022056/0220 Effective date: 20081015 Owner name: AT&T INTELLECTUAL PROPERTY I, L.P., NEVADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T DELAWARE INTELLECTUAL PROPERTY, INC. (FORMERLY KNOWN AS AT&T BLS INTELLECTUAL PROPERTY, INC., WHICH WAS FORMERLY KNOWN AS AT&T INTELLECTUAL PROPERTY, INC., WHICH WAS FORMERLY KNOWN AS BELLSOUTH I;REEL/FRAME:022056/0220 Effective date: 20081015 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |