<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--Converted with LaTeX2HTML 2008 (1.71)
original version by: Nikos Drakos, CBLU, University of Leeds
* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>Migration and Copy</TITLE>
<META NAME="description" CONTENT="Migration and Copy">
<META NAME="keywords" CONTENT="main">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META NAME="Generator" CONTENT="LaTeX2HTML v2008">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="main.css">
<LINK REL="next" HREF="Backup_Strategies.html">
<LINK REL="previous" HREF="Automated_Disk_Backup.html">
<LINK REL="up" HREF="Bacula_Main_Reference.html">
<LINK REL="next" HREF="Backup_Strategies.html">
</HEAD>
<BODY >
<!--Navigation Panel-->
<A NAME="tex2html1692"
HREF="Backup_Strategies.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html1686"
HREF="Bacula_Main_Reference.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html1680"
HREF="Automated_Disk_Backup.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html1688"
HREF="Contents.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html1690"
HREF="Thanks.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html1693"
HREF="Backup_Strategies.html">Backup Strategies</A>
<B> Up:</B> <A NAME="tex2html1687"
HREF="Bacula_Main_Reference.html">Bacula Main Reference</A>
<B> Previous:</B> <A NAME="tex2html1681"
HREF="Automated_Disk_Backup.html">Automated Disk Backup</A>
<B> <A NAME="tex2html1689"
HREF="Contents.html">Contents</A></B>
<B> <A NAME="tex2html1691"
HREF="Thanks.html">Index</A></B>
<BR>
<BR>
<!--End of Navigation Panel-->
<!--Table of Child-Links-->
<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
<UL>
<LI><A NAME="tex2html1694"
HREF="Migration_Copy.html#SECTION002910000000000000000">Migration and Copy Job Resource Directives</A>
<LI><A NAME="tex2html1695"
HREF="Migration_Copy.html#SECTION002920000000000000000">Migration Pool Resource Directives</A>
<LI><A NAME="tex2html1696"
HREF="Migration_Copy.html#SECTION002930000000000000000">Important Migration Considerations</A>
<LI><A NAME="tex2html1697"
HREF="Migration_Copy.html#SECTION002940000000000000000">Example Migration Jobs</A>
</UL>
<!--End of Table of Child-Links-->
<HR>
<H1><A NAME="SECTION002900000000000000000"></A>
<A NAME="MigrationChapter"></A>
<BR>
Migration and Copy
</H1>
<A NAME="16222"></A>
<A NAME="16223"></A>
<P>
The term Migration, as used in the context of Bacula, means moving data from
one Volume to another. In particular it refers to a Job (similar to a backup
job) that reads data that was previously backed up to a Volume and writes
it to another Volume. As part of this process, the File catalog records
associated with the first backup job are purged. In other words, Migration
moves Bacula Job data from one Volume to another by reading the Job data
from the Volume it is stored on, writing it to a different Volume in a
different Pool, and then purging the database records for the first Job.
<P>
The Copy process is essentially identical to the Migration feature with the
exception that the Job that is copied is left unchanged. This essentially
creates two identical copies of the same backup. However, the copy is treated
as a copy rather than a backup job, and hence is not directly available for
restore. If bacula founds a copy when a job record is purged (deleted) from the
catalog, it will promote the copy as <I>real</I> backup and will make it
available for automatic restore.
<P>
The Copy and the Migration jobs run without using the File daemon by copying
the data from the old backup Volume to a different Volume in a different Pool.
<P>
The section process for which Job or Jobs are migrated
can be based on quite a number of different criteria such as:
<UL>
<LI>a single previous Job
</LI>
<LI>a Volume
</LI>
<LI>a Client
</LI>
<LI>a regular expression matching a Job, Volume, or Client name
</LI>
<LI>the time a Job has been on a Volume
</LI>
<LI>high and low water marks (usage or occupation) of a Pool
</LI>
<LI>Volume size
</LI>
</UL>
<P>
The details of these selection criteria will be defined below.
<P>
To run a Migration job, you must first define a Job resource very similar
to a Backup Job but with <B>Type = Migrate</B> instead of <B>Type =
Backup</B>. One of the key points to remember is that the Pool that is
specified for the migration job is the only pool from which jobs will
be migrated, with one exception noted below. In addition, the Pool to
which the selected Job or Jobs will be migrated is defined by the <B>Next Pool = ...</B> in the Pool resource specified for the Migration Job.
<P>
Bacula permits Pools to contain Volumes with different Media Types.
However, when doing migration, this is a very undesirable condition. For
migration to work properly, you should use Pools containing only Volumes of
the same Media Type for all migration jobs.
<P>
The migration job normally is either manually started or starts
from a Schedule much like a backup job. It searches
for a previous backup Job or Jobs that match the parameters you have
specified in the migration Job resource, primarily a <B>Selection Type</B>
(detailed a bit later). Then for
each previous backup JobId found, the Migration Job will run a new Job which
copies the old Job data from the previous Volume to a new Volume in
the Migration Pool. It is possible that no prior Jobs are found for
migration, in which case, the Migration job will simply terminate having
done nothing, but normally at a minimum, three jobs are involved during a
migration:
<P>
<UL>
<LI>The currently running Migration control Job. This is only
a control job for starting the migration child jobs.
</LI>
<LI>The previous Backup Job (already run). The File records
for this Job are purged if the Migration job successfully
terminates. The original data remains on the Volume until
it is recycled and rewritten.
</LI>
<LI>A new Migration Backup Job that moves the data from the
previous Backup job to the new Volume. If you subsequently
do a restore, the data will be read from this Job.
</LI>
</UL>
<P>
If the Migration control job finds a number of JobIds to migrate (e.g.
it is asked to migrate one or more Volumes), it will start one new
migration backup job for each JobId found on the specified Volumes.
Please note that Migration doesn't scale too well since Migrations are
done on a Job by Job basis. This if you select a very large volume or
a number of volumes for migration, you may have a large number of
Jobs that start. Because each job must read the same Volume, they will
run consecutively (not simultaneously).
<P>
<H1><A NAME="SECTION002910000000000000000">
Migration and Copy Job Resource Directives</A>
</H1>
<P>
The following directives can appear in a Director's Job resource, and they
are used to define a Migration job.
<P>
<DL>
<DT><STRONG>Pool = Pool-name</STRONG></DT>
<DD>The Pool specified in the Migration
control Job is not a new directive for the Job resource, but it is
particularly important because it determines what Pool will be examined
for finding JobIds to migrate. The exception to this is when <B> Selection Type = SQLQuery</B>, and although a Pool directive must still be
specified, no Pool is used, unless you specifically include it in the
SQL query. Note, in any case, the Pool resource defined by the Pool
directove must contain a <B>Next Pool = ...</B> directive to define the
Pool to which the data will be migrated.
<P>
</DD>
<DT><STRONG>Type = Migrate</STRONG></DT>
<DD><B>Migrate</B> is a new type that defines the job that is run as being a
Migration Job. A Migration Job is a sort of control job and does not have
any Files associated with it, and in that sense they are more or less like
an Admin job. Migration jobs simply check to see if there is anything to
Migrate then possibly start and control new Backup jobs to migrate the data
from the specified Pool to another Pool. Note, any original JobId that
is migrated will be marked as having been migrated, and the original
JobId can nolonger be used for restores; all restores will be done from
the new migrated Job.
<P>
</DD>
<DT><STRONG>Type = Copy</STRONG></DT>
<DD><B>Copy</B> is a new type that defines the job that is run as being a
Copy Job. A Copy Job is a sort of control job and does not have
any Files associated with it, and in that sense they are more or less like
an Admin job. Copy jobs simply check to see if there is anything to
Copy then possibly start and control new Backup jobs to copy the data
from the specified Pool to another Pool. Note that when a copy is
made, the original JobIds are left unchanged. The new copies can not
be used for restoration unless you specifically choose them by JobId.
If you subsequently delete a JobId that has a copy, the copy will be
automatically upgraded to a Backup rather than a Copy, and it will
subsequently be used for restoration.
<P>
</DD>
<DT><STRONG>Selection Type = Selection-type-keyword</STRONG></DT>
<DD>The Selection-type-keyword determines how the migration job
will go about selecting what JobIds to migrate. In most cases, it is
used in conjunction with a <B>Selection Pattern</B> to give you fine
control over exactly what JobIds are selected. The possible values
for Selection-type-keyword are:
<DL>
<DT><STRONG>SmallestVolume</STRONG></DT>
<DD>This selection keyword selects the volume with the
fewest bytes from the Pool to be migrated. The Pool to be migrated
is the Pool defined in the Migration Job resource. The migration
control job will then start and run one migration backup job for
each of the Jobs found on this Volume. The Selection Pattern, if
specified, is not used.
<P>
</DD>
<DT><STRONG>OldestVolume</STRONG></DT>
<DD>This selection keyword selects the volume with the
oldest last write time in the Pool to be migrated. The Pool to be
migrated is the Pool defined in the Migration Job resource. The
migration control job will then start and run one migration backup
job for each of the Jobs found on this Volume. The Selection
Pattern, if specified, is not used.
<P>
</DD>
<DT><STRONG>Client</STRONG></DT>
<DD>The Client selection type, first selects all the Clients
that have been backed up in the Pool specified by the Migration
Job resource, then it applies the <B>Selection Pattern</B> (defined
below) as a regular expression to the list of Client names, giving
a filtered Client name list. All jobs that were backed up for those
filtered (regexed) Clients will be migrated.
The migration control job will then start and run one migration
backup job for each of the JobIds found for those filtered Clients.
<P>
</DD>
<DT><STRONG>Volume</STRONG></DT>
<DD>The Volume selection type, first selects all the Volumes
that have been backed up in the Pool specified by the Migration
Job resource, then it applies the <B>Selection Pattern</B> (defined
below) as a regular expression to the list of Volume names, giving
a filtered Volume list. All JobIds that were backed up for those
filtered (regexed) Volumes will be migrated.
The migration control job will then start and run one migration
backup job for each of the JobIds found on those filtered Volumes.
<P>
</DD>
<DT><STRONG>Job</STRONG></DT>
<DD>The Job selection type, first selects all the Jobs (as
defined on the <B>Name</B> directive in a Job resource)
that have been backed up in the Pool specified by the Migration
Job resource, then it applies the <B>Selection Pattern</B> (defined
below) as a regular expression to the list of Job names, giving
a filtered Job name list. All JobIds that were run for those
filtered (regexed) Job names will be migrated. Note, for a given
Job named, they can be many jobs (JobIds) that ran.
The migration control job will then start and run one migration
backup job for each of the Jobs found.
<P>
</DD>
<DT><STRONG>SQLQuery</STRONG></DT>
<DD>The SQLQuery selection type, used the <B>Selection
Pattern</B> as an SQL query to obtain the JobIds to be migrated.
The Selection Pattern must be a valid SELECT SQL statement for your
SQL engine, and it must return the JobId as the first field
of the SELECT.
<P>
</DD>
<DT><STRONG>PoolOccupancy</STRONG></DT>
<DD>This selection type will cause the Migration job
to compute the total size of the specified pool for all Media Types
combined. If it exceeds the <B>Migration High Bytes</B> defined in
the Pool, the Migration job will migrate all JobIds beginning with
the oldest Volume in the pool (determined by Last Write time) until
the Pool bytes drop below the <B>Migration Low Bytes</B> defined in the
Pool. This calculation should be consider rather approximative because
it is made once by the Migration job before migration is begun, and
thus does not take into account additional data written into the Pool
during the migration. In addition, the calculation of the total Pool
byte size is based on the Volume bytes saved in the Volume (Media)
database
entries. The bytes calculate for Migration is based on the value stored
in the Job records of the Jobs to be migrated. These do not include the
Storage daemon overhead as is in the total Pool size. As a consequence,
normally, the migration will migrate more bytes than strictly necessary.
<P>
</DD>
<DT><STRONG>PoolTime</STRONG></DT>
<DD>The PoolTime selection type will cause the Migration job to
look at the time each JobId has been in the Pool since the job ended.
All Jobs in the Pool longer than the time specified on <B>Migration Time</B>
directive in the Pool resource will be migrated.
<P>
</DD>
<DT><STRONG>PoolUncopiedJobs</STRONG></DT>
<DD>This selection which copies all jobs from a pool
to an other pool which were not copied before is available only for copy Jobs.
<P>
</DD>
</DL>
<P>
</DD>
<DT><STRONG>Selection Pattern = Quoted-string</STRONG></DT>
<DD>The Selection Patterns permitted for each Selection-type-keyword are
described above.
<P>
For the OldestVolume and SmallestVolume, this
Selection pattern is not used (ignored).
<P>
For the Client, Volume, and Job
keywords, this pattern must be a valid regular expression that will filter
the appropriate item names found in the Pool.
<P>
For the SQLQuery keyword, this pattern must be a valid SELECT SQL statement
that returns JobIds.
<P>
</DD>
</DL>
<P>
<H1><A NAME="SECTION002920000000000000000">
Migration Pool Resource Directives</A>
</H1>
<P>
The following directives can appear in a Director's Pool resource, and they
are used to define a Migration job.
<P>
<DL>
<DT><STRONG>Migration Time = time-specification</STRONG></DT>
<DD>If a PoolTime migration is done, the time specified here in seconds (time
modifiers are permitted - e.g. hours, ...) will be used. If the
previous Backup Job or Jobs selected have been in the Pool longer than
the specified PoolTime, then they will be migrated.
<P>
</DD>
<DT><STRONG>Migration High Bytes = byte-specification</STRONG></DT>
<DD>This directive specifies the number of bytes in the Pool which will
trigger a migration if a <B>PoolOccupancy</B> migration selection
type has been specified. The fact that the Pool
usage goes above this level does not automatically trigger a migration
job. However, if a migration job runs and has the PoolOccupancy selection
type set, the Migration High Bytes will be applied. Bacula does not
currently restrict a pool to have only a single Media Type, so you
must keep in mind that if you mix Media Types in a Pool, the results
may not be what you want, as the Pool count of all bytes will be
for all Media Types combined.
<P>
</DD>
<DT><STRONG>Migration Low Bytes = byte-specification</STRONG></DT>
<DD>This directive specifies the number of bytes in the Pool which will
stop a migration if a <B>PoolOccupancy</B> migration selection
type has been specified and triggered by more than Migration High
Bytes being in the pool. In other words, once a migration job
is started with <B>PoolOccupancy</B> migration selection and it
determines that there are more than Migration High Bytes, the
migration job will continue to run jobs until the number of
bytes in the Pool drop to or below Migration Low Bytes.
<P>
</DD>
<DT><STRONG>Next Pool = pool-specification</STRONG></DT>
<DD>The Next Pool directive specifies the pool to which Jobs will be
migrated. This directive is required to define the Pool into which
the data will be migrated. Without this directive, the migration job
will terminate in error.
<P>
</DD>
<DT><STRONG>Storage = storage-specification</STRONG></DT>
<DD>The Storage directive specifies what Storage resource will be used
for all Jobs that use this Pool. It takes precedence over any other
Storage specifications that may have been given such as in the
Schedule Run directive, or in the Job resource. We highly recommend
that you define the Storage resource to be used in the Pool rather
than elsewhere (job, schedule run, ...).
</DD>
</DL>
<P>
<H1><A NAME="SECTION002930000000000000000">
Important Migration Considerations</A>
</H1>
<A NAME="16278"></A>
<UL>
<LI>Each Pool into which you migrate Jobs or Volumes <B>must</B>
contain Volumes of only one Media Type.
<P>
</LI>
<LI>Migration takes place on a JobId by JobId basis. That is
each JobId is migrated in its entirety and independently
of other JobIds. Once the Job is migrated, it will be
on the new medium in the new Pool, but for the most part,
aside from having a new JobId, it will appear with all the
same characteristics of the original job (start, end time, ...).
The column RealEndTime in the catalog Job table will contain the
time and date that the Migration terminated, and by comparing
it with the EndTime column you can tell whether or not the
job was migrated. The original job is purged of its File
records, and its Type field is changed from "B" to "M" to
indicate that the job was migrated.
<P>
</LI>
<LI>Jobs on Volumes will be Migration only if the Volume is
marked, Full, Used, or Error. Volumes that are still
marked Append will not be considered for migration. This
prevents Bacula from attempting to read the Volume at
the same time it is writing it. It also reduces other deadlock
situations, as well as avoids the problem that you migrate a
Volume and later find new files appended to that Volume.
<P>
</LI>
<LI>As noted above, for the Migration High Bytes, the calculation
of the bytes to migrate is somewhat approximate.
<P>
</LI>
<LI>If you keep Volumes of different Media Types in the same Pool,
it is not clear how well migration will work. We recommend only
one Media Type per pool.
<P>
</LI>
<LI>It is possible to get into a resource deadlock where Bacula does
not find enough drives to simultaneously read and write all the
Volumes needed to do Migrations. For the moment, you must take
care as all the resource deadlock algorithms are not yet implemented.
<P>
</LI>
<LI>Migration is done only when you run a Migration job. If you set a
Migration High Bytes and that number of bytes is exceeded in the Pool
no migration job will automatically start. You must schedule the
migration jobs, and they must run for any migration to take place.
<P>
</LI>
<LI>If you migrate a number of Volumes, a very large number of Migration
jobs may start.
<P>
</LI>
<LI>Figuring out what jobs will actually be migrated can be a bit complicated
due to the flexibility provided by the regex patterns and the number of
different options. Turning on a debug level of 100 or more will provide
a limited amount of debug information about the migration selection
process.
<P>
</LI>
<LI>Bacula currently does only minimal Storage conflict resolution, so you
must take care to ensure that you don't try to read and write to the
same device or Bacula may block waiting to reserve a drive that it
will never find. In general, ensure that all your migration
pools contain only one Media Type, and that you always
migrate to pools with different Media Types.
<P>
</LI>
<LI>The <B>Next Pool = ...</B> directive must be defined in the Pool
referenced in the Migration Job to define the Pool into which the
data will be migrated.
<P>
</LI>
<LI>Pay particular attention to the fact that data is migrated on a Job
by Job basis, and for any particular Volume, only one Job can read
that Volume at a time (no simultaneous read), so migration jobs that
all reference the same Volume will run sequentially. This can be a
potential bottle neck and does not scale very well to large numbers
of jobs.
<P>
</LI>
<LI>Only migration of Selection Types of Job and Volume have
been carefully tested. All the other migration methods (time,
occupancy, smallest, oldest, ...) need additional testing.
<P>
</LI>
<LI>Migration is only implemented for a single Storage daemon. You
cannot read on one Storage daemon and write on another.
</LI>
</UL>
<P>
<H1><A NAME="SECTION002940000000000000000">
Example Migration Jobs</A>
</H1>
<A NAME="16284"></A>
<P>
When you specify a Migration Job, you must specify all the standard
directives as for a Job. However, certain such as the Level, Client, and
FileSet, though they must be defined, are ignored by the Migration job
because the values from the original job used instead.
<P>
As an example, suppose you have the following Job that
you run every night. To note: there is no Storage directive in the
Job resource; there is a Storage directive in each of the Pool
resources; the Pool to be migrated (File) contains a Next Pool
directive that defines the output Pool (where the data is written
by the migration job).
<P>
<PRE>
# Define the backup Job
Job {
Name = "NightlySave"
Type = Backup
Level = Incremental # default
Client=rufus-fd
FileSet="Full Set"
Schedule = "WeeklyCycle"
Messages = Standard
Pool = Default
}
# Default pool definition
Pool {
Name = Default
Pool Type = Backup
AutoPrune = yes
Recycle = yes
Next Pool = Tape
Storage = File
LabelFormat = "File"
}
# Tape pool definition
Pool {
Name = Tape
Pool Type = Backup
AutoPrune = yes
Recycle = yes
Storage = DLTDrive
}
# Definition of File storage device
Storage {
Name = File
Address = rufus
Password = "ccV3lVTsQRsdIUGyab0N4sMDavui2hOBkmpBU0aQKOr9"
Device = "File" # same as Device in Storage daemon
Media Type = File # same as MediaType in Storage daemon
}
# Definition of DLT tape storage device
Storage {
Name = DLTDrive
Address = rufus
Password = "ccV3lVTsQRsdIUGyab0N4sMDavui2hOBkmpBU0aQKOr9"
Device = "HP DLT 80" # same as Device in Storage daemon
Media Type = DLT8000 # same as MediaType in Storage daemon
}
</PRE>
<P>
Where we have included only the essential information - i.e. the
Director, FileSet, Catalog, Client, Schedule, and Messages resources are
omitted.
<P>
As you can see, by running the NightlySave Job, the data will be backed up
to File storage using the Default pool to specify the Storage as File.
<P>
Now, if we add the following Job resource to this conf file.
<P>
<PRE>
Job {
Name = "migrate-volume"
Type = Migrate
Level = Full
Client = rufus-fd
FileSet = "Full Set"
Messages = Standard
Pool = Default
Maximum Concurrent Jobs = 4
Selection Type = Volume
Selection Pattern = "File"
}
</PRE>
<P>
and then run the job named <B>migrate-volume</B>, all volumes in the Pool
named Default (as specified in the migrate-volume Job that match the
regular expression pattern <B>File</B> will be migrated to tape storage
DLTDrive because the <B>Next Pool</B> in the Default Pool specifies that
Migrations should go to the pool named <B>Tape</B>, which uses
Storage <B>DLTDrive</B>.
<P>
If instead, we use a Job resource as follows:
<P>
<PRE>
Job {
Name = "migrate"
Type = Migrate
Level = Full
Client = rufus-fd
FileSet="Full Set"
Messages = Standard
Pool = Default
Maximum Concurrent Jobs = 4
Selection Type = Job
Selection Pattern = ".*Save"
}
</PRE>
<P>
All jobs ending with the name Save will be migrated from the File Default to
the Tape Pool, or from File storage to Tape storage.
<P>
<HR>
<!--Navigation Panel-->
<A NAME="tex2html1692"
HREF="Backup_Strategies.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html1686"
HREF="Bacula_Main_Reference.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html1680"
HREF="Automated_Disk_Backup.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html1688"
HREF="Contents.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html1690"
HREF="Thanks.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html1693"
HREF="Backup_Strategies.html">Backup Strategies</A>
<B> Up:</B> <A NAME="tex2html1687"
HREF="Bacula_Main_Reference.html">Bacula Main Reference</A>
<B> Previous:</B> <A NAME="tex2html1681"
HREF="Automated_Disk_Backup.html">Automated Disk Backup</A>
<B> <A NAME="tex2html1689"
HREF="Contents.html">Contents</A></B>
<B> <A NAME="tex2html1691"
HREF="Thanks.html">Index</A></B>
<!--End of Navigation Panel-->
<ADDRESS>
2012-01-24
</ADDRESS>
</BODY>
</HTML>
