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_01C171FB.926706C0
Content-Type: text/plain;
charset="iso-8859-1"
Max,
Thanks for the bpdbm tip. I think I am interpreting the output correctly.
I believe the 1024 occurs with the default buffer settings. You can see the
entry in the example below near the bottom.
Client: client-name
Backup ID: clientName_0991688539
Class: Server_D_Drives
Class Type: MS-Windows-NT (13)
Proxy Client: (none specified)
Creator: root
Name1: (none specified)
Sched Label: Full
Schedule Type: FULL (0)
Retention Level: infinity (9)
Backup Time: 06/04/01 17:02:19 (991688539)
Elapsed Time: 4713 second(s)
Expiration Time: 01/18/38 22:14:07 (2147483647)
Compressed: yes
Encrypted: no
Kilobytes: 807372
Number of Files: 44187
Number of Copies: 1
Number of Frags: 1
Histogram: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
DB Compressed: yes
Files File Name: Server_D_Drives_0991688539_FULL.f
SW Version: (none specified)
Options: 0x0
MPX: 0
TIR Info: 0
TIR Expiration: 12/31/69 19:00:00 (0)
Keyword: (none specified)
Ext Security Info: no
File Restore Raw: no
Image Dump Level: 0
File System Only: no
Object Descriptor: (none specified)
Previous BI Time: 12/31/69 19:00:00 (0)
BI Full Time: 12/31/69 19:00:00 (0)
Request pid: 0
Backup status: 0
Primary Copy: 1
Image Type: 0 (Regular)
Copy number: 1
Fragment: 1
Kilobytes: 807372
Remainder: 0
Media Type: Media Manager (2)
Density: 8mm (16)
File Num: 1
ID: A00025
Host: res-labex
Block Size: 1024
Offset: 2
Media Date: 06/04/01 17:02:19 (991688539)
Dev Written On: 0
Flags: 0x0
f_unused1: ?
Expiration Time: 01/18/38 22:14:07 (2147483647)
MPX: 0
i_unused3: 0
i_unused2: 0
i_unused1: 0
-----Original Message-----
From: Max.Booth AT ubsw DOT com [mailto:Max.Booth AT ubsw DOT com]
Sent: Tuesday, November 20, 2001 12:01
To: Brett.R.Osiewicz AT irs DOT gov; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Building a baseline for monitoring write speed
& C onverting Verit as's timestamp
Brett,
The command bpdbm -ctime <seconds_since_1970> will output the more
readable date and time format:
i.e.
hostname:root$bpdbm -ctime 1006193320
1006193320 = Mon Nov 19 18:08:40 2001
I always thought that the blocksize NT uses when writing data is
fixed and
not variable... Though I may be wrong here..
Regards,
max
-----Original Message-----
From: Brett.R.Osiewicz
Sent: 20 November 2001 15:24
To: veritas-bu
Cc: Brett.R.Osiewicz
Subject: [Veritas-bu] Building a baseline for monitoring write speed
& Converting Verit as's timestamp
I am tweaking my Veritas buffer sizes on my NT network (master
servers and clients.) I have already researched previous posts about
the 3 buffer size configuration files on the master server. In order
to compare scenarios, I need a report that provides the following
information:
Backup ID
Backup Time (in m/d/y h/m/s formats preferably)
Class
Elapsed Time
Number of Files
MPX status
Block size
BPimagelist is very close and provides much, much data. However,
when using the -l option, the report seperates data about specific
fragments (the very critical Block Size) onto a seperate line. That
requires I do a whole lot of formatting.
Specifically, I need from discussion participants:
*Additional factors that I should be looking at
*One command that provides the above information
*A simple way to compare Veritas' seconds from 1970 date format to
day and time format.
I realize that this is a bad week to send this out, but I need to get
this done while things are slow during the holidays..
Thanks, Brett
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
------_=_NextPart_001_01C171FB.926706C0
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] Building a baseline for monitoring write speed =
& C onverting Verit as's timestamp</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Max, </FONT>
</P>
<P><FONT SIZE=3D2>Thanks for the bpdbm tip. I think I am =
interpreting the output correctly. I believe the 1024 occurs with =
the default buffer settings. You can see the entry in the example =
below near the bottom.</FONT></P>
<P><FONT =
SIZE=3D2>Client: &n=
bsp; client-name</FONT>
<BR><FONT SIZE=3D2>Backup =
ID: =
clientName_0991688539</FONT>
<BR><FONT =
SIZE=3D2>Class: &nb=
sp; Server_D_Drives</FONT>
<BR><FONT SIZE=3D2>Class =
Type: MS-Windows-NT =
(13)</FONT>
<BR><FONT SIZE=3D2>Proxy Client: (none =
specified)</FONT>
<BR><FONT =
SIZE=3D2>Creator: &=
nbsp; root</FONT>
<BR><FONT =
SIZE=3D2>Name1: &nb=
sp; (none specified)</FONT>
<BR><FONT SIZE=3D2>Sched Label: =
Full</FONT>
<BR><FONT SIZE=3D2>Schedule Type: FULL =
(0)</FONT>
<BR><FONT SIZE=3D2>Retention Level: infinity (9)</FONT>
<BR><FONT SIZE=3D2>Backup =
Time: &=
nbsp; 06/04/01 17:02:19 (991688539)</FONT>
<BR><FONT SIZE=3D2>Elapsed Time: 4713 =
second(s)</FONT>
<BR><FONT SIZE=3D2>Expiration =
Time: 01/18/38 =
22:14:07 (2147483647)</FONT>
<BR><FONT =
SIZE=3D2>Compressed: =
yes</FONT>
<BR><FONT =
SIZE=3D2>Encrypted: =
no</FONT>
<BR><FONT =
SIZE=3D2>Kilobytes: =
807372</FONT>
<BR><FONT SIZE=3D2>Number of Files: 44187</FONT>
<BR><FONT SIZE=3D2>Number of Copies: 1</FONT>
<BR><FONT SIZE=3D2>Number of Frags: 1</FONT>
<BR><FONT =
SIZE=3D2>Histogram: -1 =
-1 -1 -1 -1 -1 -1 -1 -1 -1</FONT>
<BR><FONT SIZE=3D2>DB Compressed: yes</FONT>
<BR><FONT SIZE=3D2>Files File Name: =
Server_D_Drives_0991688539_FULL.f</FONT>
<BR><FONT SIZE=3D2>SW =
Version: (none =
specified)</FONT>
<BR><FONT =
SIZE=3D2>Options: &=
nbsp; 0x0</FONT>
<BR><FONT =
SIZE=3D2>MPX:  =
; 0</FONT>
<BR><FONT SIZE=3D2>TIR =
Info: 0</FONT>
<BR><FONT SIZE=3D2>TIR =
Expiration: =
12/31/69 19:00:00 (0)</FONT>
<BR><FONT =
SIZE=3D2>Keyword: &=
nbsp; (none specified)</FONT>
<BR><FONT SIZE=3D2>Ext Security Info: no</FONT>
<BR><FONT SIZE=3D2>File Restore Raw: no</FONT>
<BR><FONT SIZE=3D2>Image Dump Level: 0</FONT>
<BR><FONT SIZE=3D2>File System Only: no</FONT>
<BR><FONT SIZE=3D2>Object Descriptor: (none specified)</FONT>
<BR><FONT SIZE=3D2>Previous BI =
Time: 12/31/69 19:00:00 =
(0)</FONT>
<BR><FONT SIZE=3D2>BI Full =
Time: &=
nbsp; 12/31/69 19:00:00 (0)</FONT>
<BR><FONT SIZE=3D2>Request pid: =
0</FONT>
<BR><FONT SIZE=3D2>Backup status: 0</FONT>
<BR><FONT SIZE=3D2>Primary Copy: 1</FONT>
<BR><FONT SIZE=3D2>Image =
Type: 0 =
(Regular)</FONT>
<BR><FONT SIZE=3D2>Copy number: =
1</FONT>
<BR><FONT =
SIZE=3D2> Fragment: =
1</FONT>
<BR><FONT =
SIZE=3D2> Kilobytes: =
807372</FONT>
<BR><FONT =
SIZE=3D2> Remainder: =
0</FONT>
<BR><FONT SIZE=3D2> Media =
Type: Media Manager (2)</FONT>
<BR><FONT =
SIZE=3D2> Density: &=
nbsp; 8mm (16)</FONT>
<BR><FONT SIZE=3D2> File =
Num: 1</FONT>
<BR><FONT =
SIZE=3D2> ID: =
A00025</FONT>
<BR><FONT =
SIZE=3D2> Host: &nbs=
p; res-labex</FONT>
<BR><FONT SIZE=3D2> Block =
Size: 1024</FONT>
<BR><FONT =
SIZE=3D2> Offset: &n=
bsp; 2</FONT>
<BR><FONT SIZE=3D2> Media =
Date: &=
nbsp; 06/04/01 17:02:19 (991688539)</FONT>
<BR><FONT SIZE=3D2> Dev Written On: 0</FONT>
<BR><FONT =
SIZE=3D2> Flags: &nb=
sp; 0x0</FONT>
<BR><FONT =
SIZE=3D2> f_unused1: =
?</FONT>
<BR><FONT SIZE=3D2> Expiration =
Time: 01/18/38 22:14:07 =
(2147483647)</FONT>
<BR><FONT =
SIZE=3D2> MPX:  =
; 0</FONT>
<BR><FONT =
SIZE=3D2> i_unused3: =
0</FONT>
<BR><FONT =
SIZE=3D2> i_unused2: =
0</FONT>
<BR><FONT =
SIZE=3D2> i_unused1: =
0 =
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
</FONT></P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Max.Booth AT ubsw DOT com [<A =
HREF=3D"mailto:Max.Booth AT ubsw DOT com">mailto:Max.Booth AT ubsw DOT
com</A>]</FONT>=
<BR><FONT SIZE=3D2>Sent: Tuesday, November 20, 2001 12:01</FONT>
<BR><FONT SIZE=3D2>To: Brett.R.Osiewicz AT irs DOT gov; =
veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Building a baseline for =
monitoring write speed</FONT>
<BR><FONT SIZE=3D2>& C onverting Verit as's timestamp</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Brett,</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>The command bpdbm -ctime <seconds_since_1970> =
will output the more</FONT>
<BR><FONT SIZE=3D2>readable date and time format:</FONT>
<BR><FONT SIZE=3D2>i.e.</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>hostname:root$bpdbm -ctime 1006193320</FONT>
<BR><FONT SIZE=3D2>1006193320 =3D Mon Nov 19 18:08:40 2001</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>I always thought that the blocksize NT uses when =
writing data is </FONT>
<BR><FONT SIZE=3D2>fixed and</FONT>
<BR><FONT SIZE=3D2>not variable... Though I may be wrong here..</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>Regards,</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>max</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Brett.R.Osiewicz </FONT>
<BR><FONT SIZE=3D2>Sent: 20 November 2001 15:24</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu</FONT>
<BR><FONT SIZE=3D2>Cc: Brett.R.Osiewicz</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Building a baseline for =
monitoring write speed </FONT>
<BR><FONT SIZE=3D2>& Converting Verit as's timestamp</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>I am tweaking my Veritas buffer sizes on my NT =
network (master </FONT>
<BR><FONT SIZE=3D2>servers and clients.) I have already =
researched previous posts about </FONT>
<BR><FONT SIZE=3D2>the 3 buffer size configuration files on the master =
server. In order </FONT>
<BR><FONT SIZE=3D2>to compare scenarios, I need a report that provides =
the following </FONT>
<BR><FONT SIZE=3D2>information:</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>Backup ID </FONT>
<BR><FONT SIZE=3D2>Backup Time (in m/d/y h/m/s formats =
preferably)</FONT>
<BR><FONT SIZE=3D2>Class</FONT>
<BR><FONT SIZE=3D2>Elapsed Time</FONT>
<BR><FONT SIZE=3D2>Number of Files</FONT>
<BR><FONT SIZE=3D2>MPX status</FONT>
<BR><FONT SIZE=3D2>Block size</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>BPimagelist is very close and provides much, much =
data. However, </FONT>
<BR><FONT SIZE=3D2>when using the -l option, the report seperates data =
about specific </FONT>
<BR><FONT SIZE=3D2>fragments (the very critical Block Size) onto a =
seperate line. That </FONT>
<BR><FONT SIZE=3D2>requires I do a whole lot of formatting.</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>Specifically, I need from discussion =
participants:</FONT>
<BR><FONT SIZE=3D2>*Additional factors that I should be looking =
at</FONT>
<BR><FONT SIZE=3D2>*One command that provides the above =
information</FONT>
<BR><FONT SIZE=3D2>*A simple way to compare Veritas' seconds from 1970 =
date format to </FONT>
<BR><FONT SIZE=3D2>day and time format.</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>I realize that this is a bad week to send this out, =
but I need to get </FONT>
<BR><FONT SIZE=3D2>this done while things are slow during the =
holidays.. </FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>Thanks, Brett</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>Visit our website at <A =
HREF=3D"http://www.ubswarburg.com"; =
TARGET=3D"_blank">http://www.ubswarburg.com</A></FONT>
</P>
<P><FONT SIZE=3D2>This message contains confidential information and is =
intended only </FONT>
<BR><FONT SIZE=3D2>for the individual named. If you are not the =
named addressee you </FONT>
<BR><FONT SIZE=3D2>should not disseminate, distribute or copy this =
e-mail. Please </FONT>
<BR><FONT SIZE=3D2>notify the sender immediately by e-mail if you have =
received this </FONT>
<BR><FONT SIZE=3D2>e-mail by mistake and delete this e-mail from your =
system.</FONT>
</P>
<P><FONT SIZE=3D2>E-mail transmission cannot be guaranteed to be secure =
or error-free </FONT>
<BR><FONT SIZE=3D2>as information could be intercepted, corrupted, =
lost, destroyed, </FONT>
<BR><FONT SIZE=3D2>arrive late or incomplete, or contain viruses. =
The sender therefore </FONT>
<BR><FONT SIZE=3D2>does not accept liability for any errors or =
omissions in the contents </FONT>
<BR><FONT SIZE=3D2>of this message which arise as a result of e-mail =
transmission. If </FONT>
<BR><FONT SIZE=3D2>verification is required please request a hard-copy =
version. This </FONT>
<BR><FONT SIZE=3D2>message is provided for informational purposes and =
should not be </FONT>
<BR><FONT SIZE=3D2>construed as a solicitation or offer to buy or sell =
any securities or </FONT>
<BR><FONT SIZE=3D2>related financial instruments.</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C171FB.926706C0--
|
