As I discovered, the STORE command only looks at the date to determine
whether a file qualifies for the nightly backup or not.

The scenario in my case that had me concerned was that I had a DB
last accessed on 7/27/08 at 1:02 a.m.

I started a full system backup at 7 a.m. on 7/27/08 which ran until 1 p.m

Immediately following this backup I fired up my partial nightly backup
only to discover the DB in question showed up on the nightly/partial backup.

I did not feel like this should have happened but it happened only because
the STORE command only looks at the date and does not include the time
in the qualification process.


So -- I came up with this front end program to the STORE command that 
will look at the date AND time to determine whether a file qualifies for the
backup. It is a COBOL/VPLUS app that produces two files (STOREOPT and
FILESET). 

It will read a file (NEWSDATE) containing a date/time combo which is used in
determining a file(s) qualification. The NEWSDATE file is updated at full 
system backup time plugging in the current system date/time.

The program will create a new store command which is written to the file
named STOREOPT. The qualifying fileset of files for the backup are written
to a file named FILESET.

The new STORE command line will read :

STORE ^fileset;user defined store parms here.....

A sample of the FILESET file is:

/APPCAL/DATABASE/APPCAL
/BANKING/PUB/BANKDB
/CONDOR/DATABASE/CONDOR
/DEV/CMDS/NEWSTORE
/DEV/COPYLIB/ALLPROC
/DEV/COPYLIB/ALLPROC2
/DEV/COPYLIB/DBSCHEMA
/DEV/COPYLIB/FETIDBWS
/DEV/COPYLIB/MACROFLE
/DEV/DATA/LOCKERCX
/DEV/DATABASE/AVENGR
/DEV/DATABASE/BANKDB
/DEV/DATABASE/CHATDB
/DEV/DATABASE/DONORS
/DEV/DATABASE/FANTAS
/DEV/DATABASE/FANTAS01
/DEV/DATABASE/FANTAS01.idx
/DEV/DATABASE/FANTAS02
/DEV/DATABASE/FANTAS02.idx
/DEV/DATABASE/FANTAS03
/DEV/DATABASE/FANTAS03.idx
/DEV/DATABASE/FANTAS04
/DEV/DATABASE/FANTAS04.idx
/DEV/DATABASE/FANTAS05
/DEV/DATABASE/FANTAS06
/DEV/DATABASE/FANTAS07
/DEV/DATABASE/LISTIM
/DEV/DATABASE/NEWDB
/DEV/DATABASE/PASMDC
/DEV/DATABASE/PASMON
/DEV/DATABASE/SNTINL
/DEV/DATABASE/SNTINL01
/DEV/DATABASE/SNTINL01.idx
/DEV/DATABASE/SNTINL02
/DEV/DATABASE/SNTINL03
/DEV/DATABASE/SNTINL03.idx
/DEV/DATABASE/SNTINL04
/DEV/DATABASE/SNTINL04.idx
/DEV/DATABASE/SNTINL05
/DEV/DATABASE/SNTINL05.idx
/DEV/DATABASE/SNTINL06
/DEV/DATABASE/SNTINL06.idx
/DEV/DATABASE/SNTINL07
/DEV/DATABASE/SNTINL07.idx
/DEV/DATABASE/SNTINL08
/DEV/DATABASE/SNTINL09
/DEV/DATABASE/SNTINL10
/DEV/DATABASE/SNTINL11
/DEV/DATABASE/SNTINL12
/DEV/DATABASE/SNTINL13
/DEV/DATABASE/TESTDB
/DEV/DATABASE/TRAKUA
/DEV/FASTFORM/LOCKERV2
/DEV/FORMS/LOCKERV2
/DEV/JOBS/DECRYPTJ
/DEV/JOBS/ENCRYPTJ
/DEV/NMOBJ/BIT2DEC
/DEV/NMOBJ/BIT64CNV
/DEV/NMOBJ/CALCTIME
/DEV/NMOBJ/DBLOGING
/DEV/NMOBJ/FETIACCT
/DEV/NMOBJ/FETISETP
/DEV/NMOBJ/LOADACSR
/DEV/NMOBJ/LOADTIDB
/DEV/NMOBJ/LOCKERV2
/DEV/NMOBJ/ORPHANDL
/DEV/NMOBJ/RESCUEME
/DEV/NMOBJ/UPDTFTDB
/DEV/NMPRG/LOCKERV2
/DEV/PUB/NEWSDATE
/DEV/PUB/STOREOPT
/DEV/PUB/XL
/DEV/SOURCE/DATETIME
/DEV/SOURCE/FETIACCT
/DEV/SOURCE/FETISETP
/E3K/DATABASE/CHATDB
/E3K/DATABASE/E3KSEC
/E3K/DATABASE/PASSCH
/ERUDITE/DATABASE/ERUDDB
/ERUDITE/DATABASE/TESTDB
/MUSICAT/DATABASE/MUSIC
/MUSICAT/DATABASE/MUSIDC
/ROBELLE/DEMO/STORE
/ROBELLE/QLIB/MENU
/SENTINEL/DATABASE/SNTINL
/SOCCER/DATABASE/SOCCER
/SPUTIL/DATABASE/SPUTIL
/SYS/JOB/DAILY
/SYS/JOB/FULSYS
/SYS/PUB/BRIANT
/SYS/PUB/FETIDB
/SYS/PUB/FETIDB01
/SYS/PUB/FETIDB01.idx
/SYS/PUB/FETIDB02
/SYS/PUB/FETIDB02.idx
/SYS/PUB/FETIDB03
/SYS/PUB/FETIDB03.idx
/SYS/PUB/FETIDB04
/SYS/PUB/FETIDB04.idx
/SYS/PUB/FETIDB05
/SYS/PUB/FETIDB05.idx
/SYS/PUB/FETIDB06
/SYS/PUB/FETIDB06.idx
/SYS/PUB/FETIDB07
/SYS/PUB/FETIDB07.idx
/SYS/PUB/FETIDB08
/SYS/PUB/FETIDB08.idx
/SYS/PUB/FETIDB09
/SYS/PUB/FETIDB10
/SYS/PUB/FETIDB11
/SYS/PUB/FETIPAS2
/SYS/PUB/LOCKERD2
/SYS/PUB/LOG1841
/SYS/PUB/LOG1842
/SYS/PUB/LOG1844
/SYS/PUB/NMLG2273
/SYS/PUB/NMLG2274
/SYS/PUB/NMLG2276
/SYS/PUB/TURBOGTX
/VEHOLD/DEMO/VEOPNT
/VESOFT/DEMO/VEOPNT
/WORLDCUP/DATABASE/SOCCER

The program uses the LISTFILE command ("/") to get a list of all files on the
system and then looks at the MODIFY date/times in the file label to determine
if it qualifies for the nightly backup or not.

It seems to work quite well for me, so I will offer it up to anyone out there
who thinks it may be useful for them.

The program is only meaningful for daily/nightly/partial backups and does not
really mean anything for a full system backup. 

You can contact me offline if need be or you can reply to this posting.

Run the program with parm=0 and it will take you into the VPLUS screens.
Run it with parm=1 and it will prompt you for all the options for the STORE
command and write the new store command line to the STOREOPT file.
Run it with parm=2 and it will prompt you to enter the fileset for the STORE
writing the results to the FILESET file.

The contents of these files can be pasted into your nightly backup stream
file.


Brian.

On Sun, 27 Jul 2008 15:56:03 -0400, Brian Donaldson <[log in to unmask]> wrote:

>Today, 07/27/2008, I did a full system backup  thus:
>
>!STORE @[log in to unmask]@;*T;SHOW;PROGRESS=15;INTER;STATISTICS;DIRECTORY;&
>!ONLINE=START;PARTIALDB;COMPRESS=LOW
>
>Worked just fine (I'm just a bit concerned about the time it takes tho -- 7+
>hours)
>
>After the backup was done I immediately did a nightly backup thus --
>STORE
>@[log in to unmask]@;*T;SHOW;PROGRESS=5;DATES>=07/27/2008;INTER;STATISTICS;DIRECTORY;ONLINE=START;PARTIALDB;COMPRESS=LOW
>
>This partial backup had a bunch of files on it that shouldn't have been on
>it -- two or three different TurboIMAGE databases that had not been accessed
>since 07/26/2008 or before. 
>
>No other users on the box except for me....
>
>
>Can anyone tell me why these files were on this partial backup?
>
>TIA,
>Brian Donaldson.
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *