Veritas-bu

[Veritas-bu] OTM Cached files entry

2001-12-19 05:01:39
Subject: [Veritas-bu] OTM Cached files entry
From: BrochF AT europe.stortek DOT com (Brochart, Fabrice)
Date: Wed, 19 Dec 2001 10:01:39 -0000
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C18874.27443590
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

        Well,

Did you take a look really at this files before saying that ?

In the first url : 207 if you look at the end of this document (maybe =
not
all of them but...).

I copy you this keys but...

More OTM Registry info from Veritas Support:

OTM Settings

Open Transaction Manager Registry Settings

These are located in HKEY_LOCAL_MACHINE - Software - Veritas - =
Netbackup -
CurrentVersion - Config:

=B7 OTM_USE (if this is not present the default setting is YES and Open
Transaction Manager is enabled) =B7 Applicable Settings: "NO" =3D =
disabled "YES"
=3D enabled=20

=B7 OTM_Cache_File =B7 If this is not present the cache file defaults =
to c:\temp
If this is specified it must be specified down with the full path down =
to
the FILENAME. Data type of Reg_SZ (eg. e:\temp\otm.tmp where otm.tmp is =
a 0
byte file)

=B7 OTM_Cache_Size_Init =B7 NetBackup Properties Specifies the initial =
size of
the cache file (in megabytes). If a specific value is not set, =
NetBackup
sets it to 10 megabytes. If the value is set to 0, NetBackup sets it to =
10%
of the used disk space. (Patch 326 or higher should be used for the =
Initial
Cache Size =3D 0 setting)

=B7 OTM_Cache_Size_Max =B7 Specifies the maximum cache size (in =
megabytes) of
the cache file. If the cache file reaches this size and more cache is
required, Open Transaction Manager is turned off and the backup =
continues.
However, relationships between the backed up files can be lost because =
the
snapshot is not used. The default maximum cache size is 50 megabytes. =
This
can also be set this to 0 and NetBackup will dynamically allocate =
space.

=B7 OTM_Current =B7 Applicable settings are: "YES" =3D Individual Drive =
Snapshots
Specifies that Open Transaction Manager take a snapshot of each drive =
and
back it up before proceeding to the next drive. For example, assume =
that
drives C and D are being backed up. Here, Open Transaction Manager: 1. =
Takes
a snapshot of drive C, backs it up, and discards the snapshot. 2. Takes =
a
snapshot of drive D, backs it up, and discards the snapshot. Open
Transaction Manager is enabled on only one drive at a time, depending =
on
which one is being backed up. This mode is useful when it is not =
necessary
to maintain relationships between files on the different drives.
"NO" =3D Global Drive Snapshots: Specifies that Open Transaction =
Manager take
a snapshot that includes all drives that are part of the backup and =
then
back up the drives. For example, assume that drives C and D are being =
backed
up. Here, Open Transaction Manager: 1. Takes a snapshot of C and D. 2. =
Backs
up C and then backs up D. 3. Discards the snapshot. Open Transaction =
Manager
remains enabled on both the C and the D drives for the entire duration =
of
the backup. This mode is useful when it is necessary to maintain the
relationships between files on the different drives.
"ALL_AVAILABLE" Specifies that Open Transaction Manager be enabled on =
all
drives, regardless of which ones are being backed up. If backing up =
clients
in a class that is using "Allow Multiple Data Streams", this setting =
ensures
that all the backups can use Open Transaction Manager. For example, =
assume
the following: * A client has four drives: C, D, E, and F. * The class =
file
list contains directives that split the client backup into two streams, =
each
of which is an independent backup. Drives C and D are in one backup and
drives E and F are in the other backup. * The server attempts to start =
both
backups at the same time. If Individual drive snapshots or Global drive
snapshots are selected, the following occurs: 1. The drive C and D =
backup
starts. 2. NetBackup enables Open Transaction Manager for drives C and =
D. 3.
The drive E and F backup starts. However, NetBackup cannot enable open
transaction management for drives E and F. When open transaction =
management
is active, another enable attempt succeeds only if the set of drives =
are the
same as the active set. In this example, the sets are different. 4. The
drive E and F backup continues, but without Open Transaction Manager. =
If
"Use all available drives" is selected, the following occurs: 1. The =
drive C
and D backup starts. 2. NetBackup enables Open Transaction Manager for =
all
drives (even though E and F are not part of the current backup). 3. The
drive E and F backup starts. 4. NetBackup enables transaction =
management for
all drives. This attempt succeeds because the set of drives is the same =
as
the one that is already using Open Transaction Manager. 5. Both backups =
use
Open Transaction Manager.

=B7 OTM_Exclude: =B7 The Exclude tab allows you to create and modify =
the exclude
lists on Microsoft Windows clients. An exclude=20
list names files and folders that you want to exclude from automatic
backups. The Files/Directories box shows the lists for clients that =
were
selected when the dialog box was opend. If multiple clients were =
selected, a
scroll bar is present at the bottom of the list box. Move the bar to =
display
the list for the desired client (only one list at a time can be =
modified). *
To add a file or directory to the list that is being displayed, click =
Add
List Item. * To modify a file or directory entry, select it in the =
list,
click Edit List Item, and make the change. * To Delete a file or =
directory
entry, select it in the list and click the Delete key.

=B7 OTM_Quiescent_Timeout: =B7 Busy File Timeout Specifies the duration =
(in
seconds) of the quiet period that must occur so the snap can be taken. =
The
default is 60 seconds. This a 60 second time period in which the
quiescent_wait must occur.

=B7 OTM_Quiescent_Wait: =B7 Busy File Wait Specifies how many seconds =
to wait
for a quiet period to occur. If this time expires, the backup proceeds =
but
without backing up the file. The quiet period is a period of time =
during
which no writes are being performed on the drives or volumes to be =
backed
up. The default is 5 seconds.

=B7 OTM_Error_Control (Controls how OTM reacts when it encounters an =
error.)
The default is abort. The applicable values are listed below. Data type =
is
Reg_Dword:
0 =3D Abort on Error 1 =3D Disable OTM 2 =3D Retry OTM=20

Regards

Fabrice

-----Message d'origine-----
De : mander47 AT sca.csc DOT com [mailto:mander47 AT sca.csc DOT com]
Envoy=E9 : mercredi 19 d=E9cembre 2001 10:57
=C0 : Brochart, Fabrice; veritas-bu AT mailman.eng.auburn DOT edu
Objet : RE: [Veritas-bu] OTM Cached files entry




Thanks, but these dosn't show the registry key.

Regards
Michael







"Brochart, Fabrice" <BrochF AT europe.stortek DOT com> on 19-12-2001 10:46:18

To:   Michael G Andersen/SCA/[email protected], veritas-bu AT mailman.eng.auburn DOT edu
cc:
Subject:  RE: [Veritas-bu] OTM Cached files entry



------_=_NextPart_001_01C18874.27443590
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] OTM Cached files entry</TITLE>
</HEAD>
<BODY>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>Well,</FONT>
</P>

<P><FONT SIZE=3D2>Did you take a look really at this files before =
saying that ?</FONT>
</P>

<P><FONT SIZE=3D2>In the first url : 207 if you look at the end of this =
document (maybe not all of them but...).</FONT>
</P>

<P><FONT SIZE=3D2>I copy you this keys but...</FONT>
</P>

<P><FONT SIZE=3D2>More OTM Registry info from Veritas Support:</FONT>
</P>

<P><FONT SIZE=3D2>OTM Settings</FONT>
</P>

<P><FONT SIZE=3D2>Open Transaction Manager Registry Settings</FONT>
</P>

<P><FONT SIZE=3D2>These are located in HKEY_LOCAL_MACHINE - Software - =
Veritas - Netbackup - CurrentVersion - Config:</FONT>
</P>

<P><FONT SIZE=3D2>=B7 OTM_USE (if this is not present the default =
setting is YES and Open Transaction Manager is enabled) =B7 Applicable =
Settings: &quot;NO&quot; =3D disabled &quot;YES&quot; =3D enabled =
</FONT></P>

<P><FONT SIZE=3D2>=B7 OTM_Cache_File =B7 If this is not present the =
cache file defaults to c:\temp If this is specified it must be =
specified down with the full path down to the FILENAME. Data type of =
Reg_SZ (eg. e:\temp\otm.tmp where otm.tmp is a 0 byte file)</FONT></P>

<P><FONT SIZE=3D2>=B7 OTM_Cache_Size_Init =B7 NetBackup Properties =
Specifies the initial size of the cache file (in megabytes). If a =
specific value is not set, NetBackup sets it to 10 megabytes. If the =
value is set to 0, NetBackup sets it to 10% of the used disk space. =
(Patch 326 or higher should be used for the Initial Cache Size =3D 0 =
setting)</FONT></P>

<P><FONT SIZE=3D2>=B7 OTM_Cache_Size_Max =B7 Specifies the maximum =
cache size (in megabytes) of the cache file. If the cache file reaches =
this size and more cache is required, Open Transaction Manager is =
turned off and the backup continues. However, relationships between the =
backed up files can be lost because the snapshot is not used. The =
default maximum cache size is 50 megabytes. This can also be set this =
to 0 and NetBackup will dynamically allocate space.</FONT></P>

<P><FONT SIZE=3D2>=B7 OTM_Current =B7 Applicable settings are: =
&quot;YES&quot; =3D Individual Drive Snapshots Specifies that Open =
Transaction Manager take a snapshot of each drive and back it up before =
proceeding to the next drive. For example, assume that drives C and D =
are being backed up. Here, Open Transaction Manager: 1. Takes a =
snapshot of drive C, backs it up, and discards the snapshot. 2. Takes a =
snapshot of drive D, backs it up, and discards the snapshot. Open =
Transaction Manager is enabled on only one drive at a time, depending =
on which one is being backed up. This mode is useful when it is not =
necessary to maintain relationships between files on the different =
drives.</FONT></P>

<P><FONT SIZE=3D2>&quot;NO&quot; =3D Global Drive Snapshots: Specifies =
that Open Transaction Manager take a snapshot that includes all drives =
that are part of the backup and then back up the drives. For example, =
assume that drives C and D are being backed up. Here, Open Transaction =
Manager: 1. Takes a snapshot of C and D. 2. Backs up C and then backs =
up D. 3. Discards the snapshot. Open Transaction Manager remains =
enabled on both the C and the D drives for the entire duration of the =
backup. This mode is useful when it is necessary to maintain the =
relationships between files on the different drives.</FONT></P>

<P><FONT SIZE=3D2>&quot;ALL_AVAILABLE&quot; Specifies that Open =
Transaction Manager be enabled on all drives, regardless of which ones =
are being backed up. If backing up clients in a class that is using =
&quot;Allow Multiple Data Streams&quot;, this setting ensures that all =
the backups can use Open Transaction Manager. For example, assume the =
following: * A client has four drives: C, D, E, and F. * The class file =
list contains directives that split the client backup into two streams, =
each of which is an independent backup. Drives C and D are in one =
backup and drives E and F are in the other backup. * The server =
attempts to start both backups at the same time. If Individual drive =
snapshots or Global drive snapshots are selected, the following occurs: =
1. The drive C and D backup starts. 2. NetBackup enables Open =
Transaction Manager for drives C and D. 3. The drive E and F backup =
starts. However, NetBackup cannot enable open transaction management =
for drives E and F. When open transaction management is active, another =
enable attempt succeeds only if the set of drives are the same as the =
active set. In this example, the sets are different. 4. The drive E and =
F backup continues, but without Open Transaction Manager. If &quot;Use =
all available drives&quot; is selected, the following occurs: 1. The =
drive C and D backup starts. 2. NetBackup enables Open Transaction =
Manager for all drives (even though E and F are not part of the current =
backup). 3. The drive E and F backup starts. 4. NetBackup enables =
transaction management for all drives. This attempt succeeds because =
the set of drives is the same as the one that is already using Open =
Transaction Manager. 5. Both backups use Open Transaction =
Manager.</FONT></P>

<P><FONT SIZE=3D2>=B7 OTM_Exclude: =B7 The Exclude tab allows you to =
create and modify the exclude lists on Microsoft Windows clients. An =
exclude </FONT></P>

<P><FONT SIZE=3D2>list names files and folders that you want to exclude =
from automatic backups. The Files/Directories box shows the lists for =
clients that were selected when the dialog box was opend. If multiple =
clients were selected, a scroll bar is present at the bottom of the =
list box. Move the bar to display the list for the desired client (only =
one list at a time can be modified). * To add a file or directory to =
the list that is being displayed, click Add List Item. * To modify a =
file or directory entry, select it in the list, click Edit List Item, =
and make the change. * To Delete a file or directory entry, select it =
in the list and click the Delete key.</FONT></P>

<P><FONT SIZE=3D2>=B7 OTM_Quiescent_Timeout: =B7 Busy File Timeout =
Specifies the duration (in seconds) of the quiet period that must occur =
so the snap can be taken. The default is 60 seconds. This a 60 second =
time period in which the quiescent_wait must occur.</FONT></P>

<P><FONT SIZE=3D2>=B7 OTM_Quiescent_Wait: =B7 Busy File Wait Specifies =
how many seconds to wait for a quiet period to occur. If this time =
expires, the backup proceeds but without backing up the file. The quiet =
period is a period of time during which no writes are being performed =
on the drives or volumes to be backed up. The default is 5 =
seconds.</FONT></P>

<P><FONT SIZE=3D2>=B7 OTM_Error_Control (Controls how OTM reacts when =
it encounters an error.) The default is abort. The applicable values =
are listed below. Data type is Reg_Dword:</FONT></P>

<P><FONT SIZE=3D2>0 =3D Abort on Error 1 =3D Disable OTM 2 =3D Retry =
OTM </FONT>
</P>

<P><FONT SIZE=3D2>Regards</FONT>
</P>

<P><FONT SIZE=3D2>Fabrice</FONT>
</P>

<P><FONT SIZE=3D2>-----Message d'origine-----</FONT>
<BR><FONT SIZE=3D2>De : mander47 AT sca.csc DOT com [<A =
HREF=3D"mailto:mander47 AT sca.csc DOT com">mailto:mander47 AT sca.csc DOT 
com</A>]</F=
ONT>
<BR><FONT SIZE=3D2>Envoy=E9 : mercredi 19 d=E9cembre 2001 10:57</FONT>
<BR><FONT SIZE=3D2>=C0 : Brochart, Fabrice; =
veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Objet : RE: [Veritas-bu] OTM Cached files =
entry</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Thanks, but these dosn't show the registry =
key.</FONT>
</P>

<P><FONT SIZE=3D2>Regards</FONT>
<BR><FONT SIZE=3D2>Michael</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>&quot;Brochart, Fabrice&quot; =
&lt;BrochF AT europe.stortek DOT com&gt; on 19-12-2001 10:46:18</FONT>
</P>

<P><FONT SIZE=3D2>To:&nbsp;&nbsp; Michael G Andersen/SCA/[email protected], =
veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>cc:</FONT>
<BR><FONT SIZE=3D2>Subject:&nbsp; RE: [Veritas-bu] OTM Cached files =
entry</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C18874.27443590--

<Prev in Thread] Current Thread [Next in Thread>