The invention relates to controlling computer software processes in general.
Conventional data backup techniques as applied to computing resources typically involve taking a periodic “snapshot” to preserve the state and data of computers and virtual machines that are hosted by computers. When taking a snapshot, it is typically necessary to first perform application quiescing to ensure data consistency. For example, in the case of a virtual machine running the Microsoft Windows™ operating system, application quiescing may be performed using the “Freeze” event handler of the Volume Shadow Copy Service (VSS). After the snapshot is taken, VSS may again be used to terminate the quiescence period using the “Thaw” VSS event handler. Likewise, the “Complete” VSS event handler may be used to cause data to be purged where such data are not required for future data backup operations, thereby freeing up system resources. In some virtual machine environments a software process on a virtual machine may receive instructions from outside of the virtual machine to initiate application quiescing, whereas once quiescence has been achieved instructions may no longer be received from outside of the virtual machine, such as to terminate the quiescence period or perform other post-snapshot operations. Such communications restrictions present a challenge to backup systems that operate separately from their data backup targets.
In one aspect of the invention a method is provided for controlling a software process, the method including causing the execution of a first software process on a computer, wherein the first software process is configured to exclusively access a resource on the computer, causing the execution of a second software process on the computer when the first software process has exclusive access to the resource, wherein the second software process is configured to perform a first predefined action that is independent of the second software process accessing the resource, attempt to access the resource, and perform a second predefined action that is dependent on the second software process accessing resource, and causing the first software process to terminate its exclusive access to the resource, thereby causing the second software process to access the resource and perform the second predefined action.
Systems and computer program products embodying the invention are also provided.
The invention will be understood and appreciated more fully from the following detailed description taken in conjunction with the appended drawings in which:
The invention is now described within the context of one or more embodiments, although the description is intended to be illustrative of the invention as a whole, and is not to be construed as limiting the invention to the embodiments shown. It is appreciated that various modifications may occur to those skilled in the art that, while not specifically shown herein, are nevertheless within the true spirit and scope of the invention.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical data storage device, a magnetic data storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
Reference is now made to
The system of
Process initiator 100 and process controller 110 may be hosted by a computer 112 that is separate from computer 104, while software processes 102 and 108 may be hosted by computer 104, or by a virtual machine 114 that is itself hosted by computer 104. In this configuration process initiator 100 and process controller 110 affect software processes 102 and 108 as described above by transmitting instructions to computer 104 and/or virtual machine 114 from a point of origin that is external to computer 104 and/or virtual machine 114. In an alternative configuration, process initiator 100 and process controller 110 may be hosted by a virtual machine 116 that is itself hosted by computer 104, while software processes 102 and 108 may be hosted by virtual machine 114. In this configuration process initiator 100 and process controller 110 affect software processes 102 and 108 as described above by transmitting instructions to virtual machine 114 from a point of origin that is external to virtual machine 114.
Any of the elements shown in
Reference is now made to
The system of
In
In
Proxy_BA_Client 308 attempts to access resource 312, but is prevented from accessing resource 312 due to Dummy_BA_Proxy 310 still maintaining its exclusive access to resource 312. Proxy_BA_Client 308 enters an indefinite wait state until it successfully accesses resource 312.
In
Where BA client 304 is unable to communicate with Proxy_BA_Client 308, such as where VMware™ restricts communications with Proxy_BA_Client 308 while Proxy_BA_Client 308 is being executed where such communications originate outside of VM 300, BA client 304 cannot directly instruct Proxy_BA_Client 308 to “thaw” VM 300. Thus, in
In
Referring now to
As shown, the techniques for controlling access to at least one resource may be implemented in accordance with a processor 410, a memory 412, I/O devices 414, and a network interface 416, coupled via a computer bus 418 or alternate connection arrangement.
It is to be appreciated that the term “processor” as used herein is intended to include any processing device, such as, for example, one that includes a CPU (central processing unit) and/or other processing circuitry. It is also to be understood that the term “processor” may refer to more than one processing device and that various elements associated with a processing device may be shared by other processing devices.
The term “memory” as used herein is intended to include memory associated with a processor or CPU, such as, for example, RAM, ROM, a fixed memory device (e.g., hard drive), a removable memory device (e.g., diskette), flash memory, etc. Such memory may be considered a computer readable storage medium.
In addition, the phrase “input/output devices” or “I/O devices” as used herein is intended to include, for example, one or more input devices (e.g., keyboard, mouse, scanner, etc.) for entering data to the processing unit, and/or one or more output devices (e.g., speaker, display, printer, etc.) for presenting results associated with the processing unit.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
It will be appreciated that any of the elements described hereinabove may be implemented as a computer program product embodied in a computer-readable medium, such as in the form of computer program instructions stored on magnetic or optical storage media or embedded within computer hardware, and may be executed by or otherwise accessible to a computer.
While the methods and apparatus herein may or may not have been described with reference to specific computer hardware or software, it is appreciated that the methods and apparatus described herein may be readily implemented in computer hardware or software using conventional techniques.
While the invention has been described with reference to one or more specific embodiments, the description is intended to be illustrative of the invention as a whole and is not to be construed as limiting the invention to the embodiments shown. It is appreciated that various modifications may occur to those skilled in the art that, while not specifically shown herein, are nevertheless within the true spirit and scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
5377352 | Tanaka et al. | Dec 1994 | A |
5790851 | Frank et al. | Aug 1998 | A |
7603502 | Richter et al. | Oct 2009 | B2 |
7831977 | Shultz et al. | Nov 2010 | B2 |
8150936 | Liu et al. | Apr 2012 | B2 |
8166265 | Feathergill | Apr 2012 | B1 |
8209298 | Anglin et al. | Jun 2012 | B1 |
8516210 | Buragohain et al. | Aug 2013 | B2 |
20020004810 | Reneris | Jan 2002 | A1 |
20020133530 | Koning | Sep 2002 | A1 |
20060123210 | Pritchett et al. | Jun 2006 | A1 |
20100049929 | Nagarkar et al. | Feb 2010 | A1 |
20120158666 | Anglin et al. | Jun 2012 | A1 |
20140195759 | Gantman et al. | Jul 2014 | A1 |
20140351822 | Jandir et al. | Nov 2014 | A1 |
20150046402 | Peretz et al. | Feb 2015 | A1 |
20150052320 | Peretz et al. | Feb 2015 | A1 |
Number | Date | Country |
---|---|---|
2012-133768 | Jul 2012 | JP |
Entry |
---|
VMware Environments, “Veeam Backup & Replication”, Version 6.0, User Guide, VMware Environments, Jan. 2012. |
CA, “Agent for Virtual Machines Guide”, CA ARCserve Backup for Windows, r12.5, 2009. |
CA, “Microsoft Volume Shadow Copy Service”, CA ARCserve Backup for Windows, r16, 2011. |
U.S. Appl. No. 13/735,151. |
English Abstract for JP2012133768, published Jul. 12, 2012, Total 26 pages. |
Number | Date | Country | |
---|---|---|---|
20140351822 A1 | Nov 2014 | US |