1460713877-f1f87d08-27b4-42ac-92f2-86a0209c80d3

1. A system for managing data in accordance with service level agreements (SLAs) that specify schedules on a calendar basis for performing prescribed data management functions and for reducing inter-function redundancy, said system comprising:
a data management engine for performing data management functions, including at least a snapshot function, and at least one back-up function, said data management engine including a service level policy engine that receives SLAs in electronic form and which controls the scheduling of the data management functions in accordance therewith,
wherein each electronic SLA is associated with a corresponding application that uses data, and wherein each SLA specifies at least one service level policy, each policy specifying a source pool for data, a destination pool where a copy should be made of the source pool data, copy frequency indicating the frequency of operation for that policy, retention period indicating how long a given copy should be retained before being allowed to expire, and schedule information indicating hours and days of operation when the policy is in place, such that a collection of policies within a SLA is capable of expressing a non-uniform schedule for when a given function should be performed and is capable of expressing multiple data management functions that should be performed on a given source of data, and
wherein said data management engine is operable to perform preparatory operations with the application and with the source pool so that the source pool of data has a coherent image of data to be copied and wherein said preparatory operations are performed once even if the SLA specifies multiple data management functions to be performed on that source pool at the current time.
2. The system of claim 1, wherein if two or more copy operations are scheduled to occur at the same instant between the same source pool and destination pool, only one of the two or more copy operations is performed by the data management engine and that copy is associated with the longest retention time corresponding to the two or more scheduled copy operations.
3. The system of claim 1, wherein preparatory operations include the data management engine collecting metadata about the application to store in conjunction with application data.
4. The system of claim 1, wherein preparatory operations include application quiescing operations.
5. The system of claim 4, wherein the application quiescing operations include freezing the application from further updating application data.
6. The system of claim 4, wherein the application quiescing operations include flushing the IO cache of the application server of application data.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A resist pattern thickening material comprising:
a resin; and
2-hydroxybenzyl alcohol.
2. A resist pattern thickening material according to claim 1, wherein the resist pattern thickening material exhibits at least one of water-solubility and alkali-solubility.
3. A resist pattern thickening material according to claim 1, wherein the resin exhibits at least one of water-solubility and alkali-solubility.
4. A resist pattern thickening material according to claim 1, wherein the resin is at least one selected from the group consisting of polyvinyl alcohol, polyvinyl acetal, and polyvinyl acetate.
5. A resist pattern thickening material according to claim 1, further comprising a surfactant.