Veritas-bu

[Veritas-bu] bpsched -predict

2005-08-24 10:39:29
Subject: [Veritas-bu] bpsched -predict
From: scottd AT HanoverDirect DOT com (Deiter Scott)
Date: Wed, 24 Aug 2005 10:39:29 -0400
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_000_01C5A8B9.A2650DF8
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It does work. It is confusing.
I've attached our showsched script.
This is a modified version of another script posted or discussed on =
this
list.

>From    Scott Deiter=20
        Hanover Direct, Inc.=20
        Tech services=20
        (717) 633-3298=20
        scottd AT hanoverdirect DOT com=20

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Stump, =
Robert
(Contractor) (J6B)
Sent: Wednesday, August 24, 2005 10:19 AM
To: Patrick Whelan; Veritas-Bu (E-mail)
Subject: RE: [Veritas-bu] bpsched -predict


bpredict can be confusing. Please read these technotes:
http://seer.support.veritas.com/docs/244103.htm
http://seer.support.veritas.com/docs/237286.htm




From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Patrick =
Whelan
Sent: Wednesday, August 24, 2005 9:56 AM
To: Veritas-Bu (E-mail)
Subject: [Veritas-bu] bpsched -predict


++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please read the disclaimer at the bottom of this e-mail.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Does anyone know the span of the bpsched -predict command.
if I run bpsched -predict 08/25/2005 10:00:00 at approximately 15:00 on =
the
24th it shows the jobs starting at 04:00, but nothing before that.
if I run it with bpsched -predict 08/25/2005 08:00:00 at approximately =
08:00
on the 24th it shows the jobs starting at midnight until approx 02:00 =
but
not the ones starting at 04:00. Is there a way to run one predict =
command to
predict what is going to run in, say, the next 24 hours?

Regards,

Patrick Whelan=20
Enterprise Systems Support (NetBackup)=20
LCHClearnet=20
+44 020 7426 7624=20


Those who give up essential liberties for temporary safety deserve =
neither
liberty nor safety.
~Benjamin Franklin
=20
... and by that time no one was left to speak up.
~Martin Niem=F6ller


**********************************************************************
This email is intended for the named recipient(s) only. Its contents
are confidential and may only be retained by the named recipient(s)
and may only be copied or disclosed with the consent of=20
LCH.Clearnet Limited. If you are not an intended recipient please
delete this e-mail and notify postmaster AT lchclearnet DOT com.

The contents of this email are subject to contract in all cases,=20
and LCH.Clearnet Limited makes no contractual commitment save where
confirmed by hard copy. LCH.Clearnet Limited accepts no liability,=20
including liability for negligence, in respect of any statement in=20
this email.

LCH.Clearnet Limited, Registered Office: Aldgate House,=20
33 Aldgate High Street, London EC3N 1EA. Recognised as a Clearing=20
House under the Financial Services & Markets Act 2000. Reg in England
No.25932=20
Telephone: +44 20 7426 7000 Internet: http://www.lchclearnet.com
**********************************************************************


------_=_NextPart_000_01C5A8B9.A2650DF8
Content-Type: text/plain;
        name="showsched.txt"
Content-Disposition: attachment;
        filename="showsched.txt"

#!/bin/ksh 

# See what is on the schedule for one day.
# which date do we want the schedule report.
# default is today

today=`date +%m/%d/%Y`
rptdate=$1  
rptdate=${rptdate:=$today}
echo  "\n Finding scheduled backups for the date "$rptdate"\n"


exec 2>/tmp/whaterr

hours='00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23'
       
for i in $hours; do
  bpschedreq  -predict $rptdate $i:00:00 >> /tmp/whatmp$$
done

cat /tmp/whatmp$$|sort -u| sort -k 7  >> /tmp/whatsorted$$

# # Format this ugly output
cat /tmp/whatsorted$$|nawk '{print \
  substr($2"                        ",1,15)  \
  substr($3"                        ",1,15)  \
  substr($4"                        ",1,20)  \
  substr($5"                        ",1,8)   \
  substr($6"                        ",1,10)  \
  substr($7"                        ",1,9)   \
  }'

rm /tmp/whatmp$$
rm /tmp/whatsorted$$

errnum=`wc -l /tmp/whaterr| nawk '{ print $1}'`
if (($errnum!=0)); then
  echo "\n\n There are "$errnum" errors in"
  echo " the error log file /tmp/whaterr"
fi

exit 

------_=_NextPart_000_01C5A8B9.A2650DF8--

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