text:
A storage and data management system establishes a data transfer pipeline between an application and a storage media using a source data mover and a destination data mover. The data movers are modular software entities which compartmentalize the differences between operating systems and media types. In addition, they independently interact to perform encryption, compression, etc., based on the content of a file as it is being communicated through the pipeline. Headers and chunking of data occurs when beneficial without the application ever having to be aware. Faster access times and storage mapping offer enhanced user interaction.
1. A method for copying data from a source to a destination using a data pipe, the method comprising:
identifying at least a first characteristic of a first portion of the data;
identifying at least a second characteristic of a second portion of the data;
copying the first portion of the data through the data pipe in a first chunk in a first format based on the first characteristic;
generating a first header describing the contents of the first chunk, the first header including information relating to at least a first storage operation to be performed on the first chunk;
copying the second portion of the data through the data pipe in a second chunk in a second format based on the second characteristic, the second format being distinct from the first format; and
generating a second header describing the contents of the second chunk, the second header including information relating to at least a second storage operation to be performed on the second chunk.
2. The method as recited in
sending the first chunk with the first header to a first destination; and
sending the second chunk with the second header to a second destination.
3. The method as recited in
the first header indicates where to store the first chunk; and
the second header indicates where to store the second chunk.
4. The method as recited in
creating a first data pipe for sending the first chunk to the first destination; and
creating a second data pipe for sending the second chunk to the second destination.
5. The method as recited in
6. The method as recited in
7. The method as recited in
storing the first chunk in a first storage medium in the first format; and
storing the second chunk in a second storage medium in the second format, the second storage medium being distinct from the first storage medium.
8. The method as recited in
performing the first storage operation on the first chunk; and
performing the second storage operation on the second chunk.
9. The method as recited in
10. The method as recited in
11. The method as recited in
12. A method for copying data from a first storage device to a second storage device, the method comprising:
obtaining data from a first storage device;
parsing the data into at least a first chunk and a second chunk, said parsing being based on a first characteristic of the data in the first chunk and a second characteristic of the data in the second chunk;
generating a first header for the first chunk, the first header being indicative of a first storage operation to be performed on the first chunk;
generating a second header for the second chunk, the second header being indicative of a second storage operation to be performed on the second chunk;
sending the first header and the first chunk in a first format over a network to a first storage destination; and
sending the second header and the second chunk in a second format over the network to a second storage destination.
13. The method of
storing the first chunk in the first format in the first storage destination; and
storing the second chunk in the second format in the second storage destination, wherein the first format is different than the second format.
14. The method of
15. The method of
16. The method of
17. A system for transferring data between a source storage device and multiple destination storage devices, the system comprising:
a source storage device configured to store a piece of data;
a plurality of destination storage devices;
a first data mover module comprising:
a parsing module configured to divide the piece of data into a plurality of chunks based on different characteristics of the data,
a header module configured to generate and associate a header with each of the plurality of chunks, each header comprising information regarding a storage operation to be performed on the associated chunk, and
a interface module configured to transmit the plurality of chunks over a network; and
a second data mover module coupled to the network and configured to receive the plurality of chunks from the network, the second data mover module being further configured to send the plurality of chunks to the plurality of destination storage devices based on the storage operation information stored in each header.
18. The system of
19. The system of
20. The system of
This application is a continuation in part of U.S. patent application Ser. No. 09/038,440, filed Mar. 11, 1998, which is based on U.S. Provisional Application No. 60/063,831, filed on Oct. 30, 1997.
The invention relates to data transfer mechanisms, and in particular, to a software-based, high speed DataPipe for providing high speed and reliable data transfer between computers.
It is fairly obvious that data, in the process of being archived or transferred from one location to another, will pass through various phases where different operations such as compression, network transfer, storage, etc. will take place on it. There are essentially two approaches that can be taken when implementing such a transfer mechanism. One would be to split the archival process into sub-tasks, each of which would perform a specific function (e.g. Compression). This would then require copying of data between sub-tasks, which could prove processor intensive. The other method would be to minimize copies, and have a monolithic program performing all of the archival functions. The downside to this would be loss of parallelism. A third alternative would of course be to use threads to do these tasks and use thread-signaling protocols, however, it is realized that this would not be entirely practical since threads are not fully supported on many computing platforms.
Accordingly, it is highly desirable to obtain a high-speed data transfer mechanism implemented in software and developed for the needs of high speed and reliable data transfer between computers.
It is an object of the invention to disclose the implementation of the DataPipe in accordance with CommVault System's Vault98 backup and recovery product. While developing the DataPipe, it is assumed that data, as it moves from archiving source (backup client) to archiving destination (backup server as opposed to media), may undergo transformation or examination at various stages in between. This may be to accommodate various actions such as data compression, indexing, object wrapping etc. that need to be performed on data being archived. Another assumption is the data may be transmitted over the network to remote machines or transferred to a locally attached media for archival.
Both the sending and the receiving computers execute software referred to herein as the DataPipe. Although the DataPipe transfer mechanism to be described herein is operative as a key component of backup and recovery software product schemes, the DataPipe is not restricted to that use. It is a general purpose data transfer mechanism implemented in software that is capable of moving data over a network between a sending and a receiving computer at very high speeds and in a manner that allows full utilization of one or more network paths and the full utilization of network bandwidth. A DataPipe can also be used to move data from one storage device to another within a single computer without the use of a network. Thus, the DataPipe concept is not confined to implementation only in networked systems, but is operable to transfer data in non-networked computers as well.
It is an object of the invention to provide in a communications system having an origination storage device and a destination storage device, a data transfer pipeline apparatus for transferring data in a sequence of N stages, where N is a positive integer greater than 1, from the origination to the destination storage device. The apparatus comprises dedicated memory having a predetermined number of buffers dedicated for carrying data associated with the transfer of data from the origination device or process to the destination device or process; and master control module for registering and controlling processes associated with the data transfer apparatus for participation in the N stage data transfer sequence. The processes include at least a first stage process for initiating the data transfer and a last Nth stage process for completing data transfer. The first stage process is operative to allocate a buffer from the predetermined number of buffers available within the dedicated memory for collection, processing, and sending of the data from the origination device to a next stage process. The last Nth stage process is operative to receive a buffer allocated to the first stage process from the (N−1)th stage process in the data transfer sequence and to free the buffer upon processing completion and storage in the destination device to permit reallocation of the buffer. The master control process further includes a means for monitoring the number of buffers from the pool of buffers allocated or assigned to particular processes in the pipeline, wherein the monitor means is operative to prevent allocation of further buffers to a particular process when the number of buffers currently allocated exceeds a predetermined threshold.
The invention will be better understood with reference to the following drawings, in which:
Before embarking on a detailed discussion of the data transfer mechanism of the present invention, the following should be understood. The objective of the DataPipe according to the present invention is to move data as quickly as possible from point A to point B (which may be on the same or different computers within a network) while performing a variety of operations (compression, encryption, content analysis, etc.) on the data. In order to meet this objective, parallel processing must be fully exploited, network bandwidth must be fully utilized, and CPU cycles must be minimized. The DataPipe must be efficiently implemented on a wide variety of computer systems such that heterogeneous systems on a network can use a DataPipe to transfer data to each other.
A DataPipe comprises a named set of tasks executing within one or more computers that cooperate with each other to transfer and process data in a pipelined manner. Within a DataPipe, a pipeline concept is used to improve performance of data transfer across multiple computers in a network. However, within a DataPipe, any stage within the pipeline may have multiple instances, thus greatly increasing the scaleability and performance of the basic pipeline concept.
The DataPipe mechanism processes data by dividing its processing into logical tasks that can be performed in parallel. It then sequences those tasks in the order in which they are to act on the data. For example, a head task may extract data from a database, a second task may encrypt it, a third may compress it, a fourth may send it out over the network, a fifth may receive it from the network, and a sixth may write it to a tape. The latter two tasks may reside on a different computer than the others, for example.
All of the tasks that comprise a single DataPipe on a given computer have access to a segment of shared memory that is divided into a number of buffers. A small set of buffer manipulation primitives is used to allocate, free, and transfer buffers between tasks.
Semaphores (or other OS specific mutual exclusion or signaling primitives) are used to coordinate access to buffers between tasks on a given computer. Special tasks, called network agents, send and receive data across network connections using standard network protocols. These agents enable a DataPipe to connect across multiple computer systems. A single DataPipe can therefore reside on more than one computer and could reside on computers of different types.
Each task may be implemented as a separate thread, process, or as a procedure depending on the capabilities of the computing system on which the DataPipe is implemented.
The data exchange paradigm called the DataPipe has been fashioned to provide solutions to the problems associated and encountered in prior art data transfer systems. The salient features of this method are as follows:
Referring to
As shown in
From the preceding discussion and
A pipeline on a particular machine can be arranged to provide a feed to another different machine. A schematic diagram is illustrated in
In addition to the transferring of data from one computer to another, a unique capability of the datapipe invention is the ability to scale to enable full utilization of the bandwidth of a network, and to fully utilize the number of peripheral devices such as tape drives, or fully utilize other hardware components such as CPUs. The scaleability of a DataPipe is achieved by using multiple instances of each task in the pipeline.
For example, multiple head tasks operating in parallel may gather data from a database and deposit it into buffers. Those buffers may then be processed by several parallel tasks that perform a function such as encryption. The encryption tasks in turn may feed several parallel tasks to perform compression, and several parallel tasks may perform network send operations to fully exploit network bandwidth. On the target computer, several network reader tasks may receive data, which is written to multiple tape units by several tasks. All of these tasks on both computers are part of the same DataPipe and collectively perform the job of moving data from the database to tape units. They do this job extremely efficiently by fully utilizing all available bandwidth and hardware allocated to the DataPipe while also minimizing CPU cycles by avoiding unnecessary copying of the data as it moves from one stage of the DataPipe to the next.
In general, there could be N stages in a given DataPipe pipeline. At each stage of the pipeline, there could be p instances of a given module task. These N stages could all be on the local machine or could be split across two different machines in which case there are network writers and network readers (i.e. pseudo tail and head network agents) which work together to ensure continuity in the pipeline.
Referring to
Buffer Manipulation Primitives
Referring now to
Master_Monitor is connected to a predefined port, to enable it to communicate with its peers on other computer systems. Master_Monitor monitors the status of all DataPipes under its control at all times and is able to provide status of the DataPipe to the application software that uses the DataPipe.
To accomplish these above tasks, a master manager program called Master_Monitor executes in the preferred embodiment as a daemon on all process machines. The Master_Monitor program "listens" or receives control signal data on a port dedicated to receiving such control data from external processes. In this manner, the Master_Monitor program can serve the requirements of pipeline operations. Master_Monitor functions to monitor status of all pipelines under its control at all times and reports status of the pipeline to all its sub-modules. As shown in
DataPipe Initiation
Referring now to
Referring now to
The process responsible for initiation of the pipeline constructs a name for the pipeline using its own process Id, a time stamp, and the name of the machine where the initiator process is running. This pipeline name is passed along with both the Initiate-Pipe as well as the EXTEND_Pipe message so that the pipeline is identified with the same name on all computers on which it is operating (i.e. both the remote as well as the local machine). All shared memory segments and semaphores (reference numeral 85 of
Data Transfer Implementation
Allocation: Receive: Send: Free
Directing attention to
As shown in
All FreeBuf( ) calls free their buffers into the input queue of the first module. By the same rule, first stage modules are never permitted to do a ReceiveBuf( ) but are permitted to do AllocBuf( ). On the other hand, tail processes are permitted to perform only FreeBuf( ) and never permitted to perform a SendBuf( ). All other modules can Receive, Allocate, Send, and Free buffers. First stage modules always perform SendBuf( ) after they execute each AllocBuf( ). Note: Any module in the pipeline can allocate an available buffer if it requires to copy data during processing. Normally, however, data is not recopied within a given machine's pipeline segment.
As previously mentioned, each queue 95 is associated with a semaphore 50 to guarantee orderly access to shared memory and which gets triggered upon actions such as AllocBuf( ), ReceiveBuf( ), SendBuf( ) and FreeBuf( ). A second set of semaphores 80, each associated with a particular module in the pipeline, provide a mechanism to ensure that no bottlenecks occur. Dedicated network agents thus map themselves across any network interface on the system, as long as data propagation is ensured. The number of network agents per pipeline is a configurable parameter, which helps this mechanism exploit maximum data transfer bandwidth available on the network over which it is operating. A single dedicated parent network thread/process monitors performance and status of all network agents on that particular machine for a particular pipeline.
Referring again to
As the identification process is completed, all modules attach themselves to a specific shared memory space segment that is shared among modules on that machine for this particular pipeline. This shared memory segment has many data buffers, input queues for all stages on the pipeline, and their initial values. Each module identifies its own input queues and output queues depending on the stage that module is supposed to run at, and initial queue (first stage) is populated with number of data segments for sharing on this particular pipeline. Also all modules attach themselves to an allocator semaphore array, which controls the number of buffers allocated by a specific module that can be active in the pipeline.
Data Integrity
Integrity of the data passed along and the sequencing of data are maintained in part by a pair of special purpose modules termed sequencer and resequencer processes.
The purpose of the resequencer is to enforce the proper ordering of buffers. It insures this by making sure that it sends buffers to the next pipeline module in sequence number order. If a buffer is received out of order, it is held by the resequencer until all processor buffers are received and send to the next module. In this way, buffer ordering is guaranteed and buffers are never held longer than necessary. These steps are depicted in
Hence, in the preferred embodiment, all data pipe transfers employing multi-instance stages via the sequencer/resequencer processes ensure that the input sequence of sequence numbers are not violated for each instance of the module. Further, the restriction that all modules of a specific multi-instance stage should be of the same type eliminates the chances for preferential behavior.
The concept of fairness means that each task will be assured of getting the input buffers it needs to operate on without waiting longer than necessary. Fairness among the modules in a given DataPipe where no stage of the pipeline has more than one instance is automatic. As the tail task frees a buffer it enters the free buffer pool where it may enable the head task to allocate it and begin processing. All tasks in the DataPipe operate a maximum speed overlapping the processing done by other tasks int he preceding or following stage of the pipeline.
If a DataPipe has stages consisting of parallel instances of a task, fairness among those tasks is assured by using an allocator semaphore which counts from Max_Buffers/NA (where NA is the number of allocators for this DataPipe on this particular machine) downward to zero. All FreeBuf( )s increment this semaphore back, however, there could be only Max_Buffers/NA buffers allocated by any allocator module in this DataPipe. This ensures that all allocators get a fair share of the available total number of input buffers. If a particular process attempts to allocate more buffers than it is allowed, the master_monitor process prevents such allocation, causing the process to either terminate or wait until a buffer currently allocated to the process becomes freed thereby incrementing the semaphore back up to allow the process to allocate another buffer.
Control Messages
All instances of all modules have a control socket to Master_Monitor over which control messages are exchanged. All network readers/writers have an analogous control socket to their parent network agent. The parent network agent itself has a control socket to Master_Monitor. Each module periodically checks its control socket for any messages from Master_Monitor. Critical information such as a STOP_PIPE message is passed to Master_Monitor via this mechanism.
Status Monitoring
Each module initiated by Master_Monitor on a given machine is monitored by either a parent network process (in the case of network reader or writer), or by Master_Monitor itself, for states of execution. In case any module is reported as having terminated abnormally, Master_Monitor identifies this exception, and signals all the modules on that particular pipeline to stop. This is done by means of control messages through control sockets as described previously. Upon safely stopping all modules pertaining to this particular pipeline, it signals the remote machine's Master_Monitor to stop the remote side of this particular pipeline and the entire pipeline is shut down safely by means of control message signaling.
In a preferred embodiment, the DataPipe functions and processes are implemented as software function in the higher level 'C' program language on Sun Solaris or HP-UX operating systems and incorporated into Release 2.7 of CommVault System's Vault98 storage management product.
To set up the DataPipe the Master_Monitor is called and provided with the name of the DataPipe and the names of the modules that will use the pipe (module 10).
Master_Monitor (Initiate_Pipe(Sample_pipe,A,B,C)).
Within the logic of module A, Alloc_Buf( ) function is then called to obtain a buffer (20). The logic of module A may perform any actions it wants to fill the buffer with useful data. When it has completed its processing of the buffer (30), it calls SendBuf( ) to send the buffer to module B for processing (40). Module A then repeats its function by again calling Alloc_Buf( ) to obtain the next buffer.
The logic of module B calls ReceiveBuf( ) to obtain a buffer of data from module A (50). It then operates on the buffer by performing processing as required (60). When it is finished with the buffer it calls SendBuf( ) to send that buffer to module C (70).
Module B then repeats if function by again calling ReceiveBuf( ) to obtain the next buffer from module A.
Module C obtains a buffer of data from module B by calling ReceiveBuf( ) (80). When it has completed its processing of the data in that buffer (90), it calls FreeBuf( ) to release the buffer (100). Like the other two modules, it loops back to receive the next buffer form module B.
The primitives used to allocate, free, send, and receive buffers are synchronized by the use of semaphores. This ensures coordination between the modules so that the receiving module does not start processing data before the sending module has finished with it. If no buffer is available, the AllocBuf or ReceiveBuf primitives will wait until one is available. All three modules operate in parallel as separate tasks. The order of processing from A to B to C is established in the initial call to Master_Monitor that established the DataPipe.
Referring now to
Salient Features
From the foregoing discussion, numerous advantages of the data pipe pipeline data transfer system using semaphore signaled shared memory to produce a general purpose, flexible data transfer mechanism are apparent. Included among these advantages are:
The data mover 806 includes an operating system interface module 814 that interacts with an encryption module 816, a compression module 818 and a chunking manager 820. A header/footer support module 821 is used to record information that indicates what format the data has been placed into before moving to the data mover 810. The storage mapping 808 examines the data to determine where it will be sent. In the example of
As data is moved from the first operating system 802 to the storage media 812, a data pipe is created for passage of the data. For example, the data mover 806 may be considered to create a data pipe between the data mover 806 and the data mover 810. Although the data that is being transmitted could be parsed into multiple chunks by the chunking manager 820, and sent to different types of storage media 812, the data pipe may be considered to be the same data pipe for the data that is being sent. For example, if the data that is to be sent from the first operating system 802 to the storage media 812 is data that begins in a text format, changes to streaming video format, and then to audio format, the data could be separated into chunks which should be stored in different storage media and in different formats. However, the data will be considered to have traveled through a single data pipe. Each chunk of the data that is sent to the storage media 812 causes the storage management system 800 to identify the characteristics of the chunk that has been sent as well as characteristics of the next chunk that is to be sent, thereby allowing the storage management system 800 to keep the data pipe that has been established.
Any portion of the storage management system 800 may select the format for the data. For example, the software application 804 may select whether to encrypt, to compress, or to chunk data that is to be sent. The storage mapping 808 may also be the component that determines whether to encrypt, to compress, or to chunk the data. Also, the data mover 806 may make the decision of whether to encrypt, to compress, or to chunk the data. Numerous other decisions may be made by any one of these three components, such as the type of header, the transmission protocol, or other information necessary to transmit data from the first operating system 802 to the storage media 812.
The data movers 806 and 810 are illustrated having other support modules 838 and 840, respectively. These other support modules 838 and 840 are illustrated in dashed lines to indicate that they may or may not be present.
Another optional feature is an in-line snooping module 906 that is used for such purposes as anti-virus checking, as well as other security purposes. A header transfer module 908 is included to transfer special headers with the portions of data that include the header 900. A compression algorithm selector 910 is included to select the appropriate compression algorithm for the data that is about to be sent or has just been received. An offset and block tagging module 912 is included for purposes of tagging the offset block number of the data. The block number and offset of the data is useful in determining where to locate data that has been stored. An in-line CRC (cyclic redundancy check) generator 914 may also be included in the i-tag header 900. If the in-line CRC 914 is included, a discard duplicate CRC module 916 may be included for discarding duplicate CRC blocks that have been generated by the in-line CRC 914 generator. Also included is a restart from point of failure (POF) module 918 that is able to continue transmission of data regardless of failures in the transmission. Also, group blocks module 920 can be included to group multiple blocks of data together for more efficient data transfer.
The data mover 1026 includes a plurality of modules 1028, a media module 1030, and a data index 1032. The plurality of modules 1028 allows the data mover 1026 to store the data in a first storage media 1034, a second storage media 1036, down to an nth storage media 1038. The data that is sent from the computing system 1002 to the computing system 1006 may be compressed multiple times before being stored in one of the storage media 1034, 1036, 1038.
In addition, the computing system 1004 may transmit data to be stored. The computing system 1004 has a second operating system 1040, software application(s) 1042, an installed file system 1044, and a data mover 1046, having a plurality of modules 1048. As described in relation to the header 900, data is transmitted in various formats, and various potions of the storage management system may determine which formats to implement for the particular portion of the data transmission.
Of note, the computing systems 1002, 1004, and 1006 may include, as shown in dashed lines, respective storage managers 1050, 1052, and 1054. In this embodiment, the computing system 1008 may no longer be required.
The computing system 1104 is illustrated as including a second operating system 1136, and software applications 1138 that interact with an installed file system 1140. The installed file system 1140 may receive data from the software applications 1138 and transmit the data to a data mover 1142, where detailed information concerning transmission of the data is found in the computing system 1106 and its manager module 1144 and master map 1146. The data is then transmitted to the network attached storage 1110 where a destination data mover 1148 receives the data, and media module 1150 determines where the data will be stored in a storage media 1152.
As shown in dashed lines, the network 1112 could extend directly to the storage area network 1108. Also shown in dash lines, the network 1114 could extend directly to the network attached storage and the computing system 1106. These variations create greater flexibility in the storage management system 1100 and provide numerous variations to the system. Upon viewing the present disclosure, those skilled in the art will understand that numerous variations are desirable in certain circumstances.
Another method for transfer of data is where a single header 1261 begins the transmission of multiple chunks, i.e., chunk1 1263, chunk2 1265, chunk3 1267, . . . chunkN 1269. The chunks are followed by a footer 1271 that completes the transmission of the data in this particular embodiment.
Still another method which the header information storage 1211 may use to transmit data is shown by header1 1281, which is followed by chunk1 1283. Chunk1 1283 is then followed by a footer1 1285 to complete transmission of that particular chunk. The next chunk is sent in the same manner, i.e., a header2 1287 is followed by chunk2 1289, which is followed by a footer2 1291 to complete the transmission of a second chunk. This process continues until all chunks have been transmitted to the destination data mover 1233. Of course, the above three methods for transmission of data are exemplary only, and other alternatives could be used for transferring data between the source data mover 1231 and the destination data mover 1233.
Chunk 1330 is illustrated as including chunk1 1336, chunk2 1338, . . . chunkN 1340. Each of these individual chunks of the chunk 1330 is illustrated in greater detail to the right, and is represented by chunk 1350.
The chunk 1350 includes a chunk header 1352 and a chunk footer 1354. The chunk header 1352 is followed by a tag header 1356, which is then followed by data 1358. Another tag header 1360 follows the data 1358, and is followed by data 1362 and another tag header 1364. The tag header 1364 is followed by an options header 1366, which includes processing information, such as information indicating that the data should be stored on a different type storage media. The options header 1366 may be the only information following the tag header 1364, but data 1368 is illustrated in the event that other data is to be included after the data header 1364. A tag header 1370 is then illustrated and is followed by data 1372. This process continues until the chunk footer 1354 is sent from the source data mover 1310 to the destination data mover 1312.
While there has been shown preferred embodiments of the present invention, those skilled in the art will further appreciate that the present invention may be embodied in other specific forms without departing from the spirit of central attributes thereof. All such variations and modifications are intended to be within the scope of this invention as defined by the appended claims.
Patent Citations
Non-Patent Citations
Referenced by
Legal Events
Original Image


text:
Quick Links
Shop All Jewelry
RGZ11285 In Stock
Light up your outfit with our Triple Row Brilliant Cut CZ Eternity Band. Dozens of CZs, just under 2mm each, surround the entire band, bringing an elegant beauty to this classic style. The moderate 5mm band makes this cubic zirconia ring wearable for almost any occasion, and we're sure it will become one of your favorite styles! Available in whole sizes 5 through 9.
• Triple Row Design
• Middle Row of Tiny CZ Stones
• High Quality .925 Sterling Silver
• Sizes 5 to 9 Available
• Includes Free Gift Box
Eve's Addiction.com wants you to be a happy customer. We want you to be completely satisfied with the sterling silver jewelry that you receive from us, as we only sell high quality silver and cubic zirconia cz jewelry. We do understand that you may not like your purchase for some reason.
You may return or exchange your jewelry within 60 days of purchase if you are not satisfied with it. The jewelry must be returned in its original condition for a refund or exchange. Engraved, personalized, photo, monogram, name and initial, chocolate and clearance items are not returnable or exchangeable.

subset: commoncrawl


text:
The Financial Aid Office receives notification of scholarships offered through private sources. Private scholarships may be obtained through local or national industry, community clubs, organizations, and churches. Scholarship recipients are selected by the organization providing the scholarship funds. The Northeast State Foundation administers scholarship funds. In selecting recipients for these scholarships, emphasis is placed upon scholastic achievement, character, future promise, and/or financial need. Additional scholarships are established as funds are donated.
Students may explore scholarship opportunities by clicking each of the following sites:
Students and/or parents should beware of websites asking payment for their services. If a fee is required for the scholarship search or the legitimacy of the scholarship is questionable, check the following sites for information:


text:
Happy 100th Birthday, Rosa Parks
Kiara Jones says she feels sorry for what Rosa Parks had to go through.
"The bus driver kept yelling at her, asking her to move up out of her seat," said Kiara, a third-grader at Coleman Young Elementary School in Detroit, Michigan, in an interview with the Detroit News.
Parks, of course, is remembered for refusing to give up her seat to a white man on a racially segregated bus in Montgomery, Alabama.
("Segregated" means blacks and whites were separated.)
"I didn't want to be pushed around," she said years later, according to the Los Angeles Times.
The date was December 1st, 1955 – a time when discrimination against African-Americans was not only common in many places but also legal.
Parks' arrest led to a boycott of Montgomery buses by African-American riders – a boycott that lasted more than a year.
It also triggered a chain of court battles – battles that helped lead to the desegregation of public transportation nationwide.
(A "boycott" means refusing to buy or use something.)
February 4th, 2013, would have been Rosa Parks' 100th birthday.
On that Monday, the US Postal Service honored her by unveiling a new Rosa Parks postage stamp at the Charles H. Wright Museum of African-American History in Detroit.
"The values that Rosa Parks' stood for (and) fought for are values which we must fight for forever," US Senator Carl Levin of Michigan said at the unveiling ceremony.
Parks' birthday was also celebrated at the Henry Ford Museum in Dearborn, Michigan – the museum that's now home to the bus on which Parks was arrested.
You can even sit in the very same seat where she sat.
"It felt good — like Rosa Parks was right there on the bus," Coleman Young 3rd grader Ashaunna Jackson told the News.
A lot has changed in our nation since Rosa Parks refused to give up her seat – "a seat where the world was changed," as Levin said, according to the Associated Press.
Today, racial equality is the law of the land.
"Rosa Parks may not have been planning to make history," President Obama in a proclamation marking her 100th birthday. "But her defiance sparked a movement that advanced our journey toward justice and equality for all."


text:
FAIRFIELD, CONN. - Freshman Charlie Roche (Haverhill, Mass.) scored a goal in the 82nd minute of play, but it was not enough, as the University of New Hampshire men's soccer team fell to Fairfield University, 2-1, at Lessing Field on Wednesday night.
Roche would find the back of the net after heading the ball just under the cross bar, past a diving Michael O'Keeffe for his first collegiate goal on a pass from Brad Hilton (Merrimack, N.H.). Despite the late charge, the Wildcats still outshot the Stags 10 to eight, including a second half in which they compiled four shots, while the Stags totaled two.
Fairfield would draw first blood in the 14th minute of the action as Christian Uy found Matthew Uy on a free kick on the far side of the box, setting up a shot that found the left corner of the net, giving the home team the early 1-0 lead.
The Wildcats would respond by peppering the Stags with four shots in the remainder of the first half of play, but were turned away by O'Keeffe, who racked up three saves on all four attempts, compiling a total of seven saves in the game.
Jon Kaufman would add to Fairfield's lead in the second half as he set up Jack Burridge with a header that just got past the hands of Colin O'Connell (Springfield, Mass.) to give the Stags the 2-0 advantage with 33 minutes remaining in the game.
New Hampshire would have one last opportunity to find the back of the net late in the second half, as a yellow card gave the Wildcats a free kick just inside midfield. O'Connell put the ball into Fairfield's box as the ball deflected off a UNH player's head and was turned away by O'Keeffe as the horn sounded.
Chris Banks (Westborough, Mass.) led the Wildcats in shots, tallying five for the second straight game. Marcus Barr (Wallingford, Pa.) notched two shots of his own, while Alex Russell (Harisburg, Pa), Hilton and Roche each tallied one shot apiece.
The Wildcats return to action when they travel to Boston, Mass. to open up conference play against the Boston University Terriers, Wednesday, Oct. 7 at 7 p.m.


text:
Out of Office Replies
July 29th 2009 15:02
1. I am currently out at a job interview and will reply to you if I fail to get the position. I may be a little moody so be prepared.
2. You are receiving this automatic notification because I am out of the office.
If I was in, chances are you wouldn't have received anything at all.
4. I will be unable to delete all the unread, worthless emails you send me until I return from vacation on 18/4/10. Please be patient, and your mail will be deleted in the order it was received.
5. Thank you for your email.
Your credit card has been charged $5.99 for the first 10 words and $1.99 for each additional word in your message.
6. The e-mail server is unable to verify your server connection and is unable to deliver this message. Please restart your computer and try sending again.
(The beauty of this is that when you return, you can see how many in-duh-viduals did this over and over.)
7. Thank you for your message, which has been added to a queuing system. You are currently in 352nd place, and can expect to receive a reply in approximately 19 weeks.
8. Hi, I'm thinking about what you've just sent me. Please wait by your PC for my response.
9. I've run away to join a different circus.
10. I will be out of the office for the next 2 weeks for medical reasons. When I return, please refer to me as "Lisa" instead of "Les"
subscribe to this blog


text:
There will be a "huge push" next year to require nasal decongestant medicines like Sudafed to be prescription only, Tennessee Lt. Gov. Ron Ramsey told a Northeast Tennessee Association of Realtors legislative luncheon Wednesday in Gray.
"That's going to be tough," Ramsey, R-Blountville, said. "That's pushing government down on the people. All of us are going to have to balance that with what's best for society."
Medicine that contains pseudoephedrine — such as Sudafed, Actifed, Contac and Claritin-D — currently can only be sold in pharmacies and must be kept behind the counter in Tennessee.Read more at Times-News.net. comments powered by Disqus


text:
Accommodations near Cathedrale St. Michel are shown below in the order of their distance. Explore our favorite hotels to find accommodations near Cathedrale St. Michel (in Sainte-Catherine Belgium) for your personal or business trips.
We sell the best lodging close to Cathedrale St. Michel so you can review the discounted Sainte-Catherine Belgium accommodations below and securely reserve your ideal hotel. Need 5+ Rooms for a group? Save with a Sainte-Catherine Belgium discounted group rate
Lodging/Accommodations close by Cathedrale St. Michel
Next 20 Hotels > [1 - 20 of 25]
Next: Show All Available Cathedrale St. Michel Hotels with Pricing >


text:
So I know there are some Aussies on here. Anyone want to show me around from September 1st to September 15 2010??
Would love to meet you guys in person!
Have a great time. I, too, an envious of your trip. Let us know about all the great fiber finds - particulary what we cannot get in the US.
Wow, what fun. I know that you'll have a great time. Business, pleasure or both?
Color me green with EXTREME envy! Have a great time Down Under!
I second that emotion! Hope you have a great trip, Kenny. -- Books, knitting, cats, fountain pens...Life is Good.
I would be happy to meet up with you when you are in Sydney.


text:
1 Park near Scottsville, Kentucky
Glasgow, Kentucky 20.77 miles NE
Park City, Kentucky 21.48 miles NE
Bowling Green, Kentucky 22.75 miles NW
Scottsville, Kentucky (map) | (270) 622-7732
Sites: 49 | Latest Rate: $14.00 | 1 Reviews
|Clean Restrooms:
|Clean Showers:
This COE CG is part of Barren River Lake State Park in southcentral KY. It sits behind the dam along the Barren River. Great fishing sites along a lazy river. Sites are somewhat close together, but they are all gravel and level and include a lantern pole, picnic table, fire ring, and a table for your portable grill. Playground stuff for kids, and recreation of the lake is close by, including Barren River Lodge and beach. You can go to ReserveUSA to reserve your space, alathough at checkin I was told that the CG is rarely full. This seems to be a great CG! - Motorhome Madness


text:
During and immediately following World War II, the oil refining, petrochemical, and natural gas transportation industries in the United States grew extensively. This expansion led to the installation of numerous gas processing plants and, in particular, gas transmission compression facilities and pipelines. Machinery and piping for these facilities were sometimes hastily designed and installed. Because this equipment consisted primarily of reciprocating compressors and pumps, severe vibration problems often occurred. These vibration problems and the resulting potential piping failures presented grave safety concerns because of the flammable fluids flowing through the pipelines under high pressure.
Compression Systems Evaluations
The PCRC subsequently commissioned Southwest Research Institute (SwRI) to develop a tool that could evaluate these compression systems at the design stage so that corrective measures could be developed prior to installation and operation. The first analysis was performed in November 1954 for a gas transmission station in Refugio, Texas. Since then, more than 12,000 analyses have been performed for compressor stations, gas processing plants, refineries, and petrochemical complexes throughout the world. Although originally seen as a design tool to optimize new installations, this capability is also used to evaluate existing systems to develop corrective measures or to analyze new operating conditions.
For more information about our compressor piping system design capabilities, or how you can contract with SwRI, please contact Buddy Broerman at firstname.lastname@example.com or (210) 522-2555. We can offer you the best approach for solving your compressor system or pump system analysis problem.
| Fluids and Machinery Engineering Department | Mechanical Engineering Division | SwRI Home |
Southwest Research Institute® (SwRI®), headquartered in San Antonio, Texas, is a multidisciplinary, independent, nonprofit, applied engineering and physical sciences research and development organization with 10 technical divisions.
©Southwest Research Institute®
August 07, 2014