head     1.5;
branch   ;
access   ;
symbols  ;
locks    romig:1.5; strict;
comment  @# @;


1.5
date     93.01.07.13.15.48;  author romig;  state Exp;
branches ;
next     1.4;

1.4
date     92.05.12.15.16.30;  author romig;  state Exp;
branches ;
next     1.3;

1.3
date     92.04.21.16.53.57;  author romig;  state Exp;
branches ;
next     1.2;

1.2
date     92.04.17.11.01.37;  author romig;  state Exp;
branches ;
next     1.1;

1.1
date     92.03.18.16.53.22;  author romig;  state Exp;
branches ;
next     ;


desc
@Was the Notes file, is now named wishlist since that makes more sense.
@


1.5
log
@final version for 2.6beta
@
text
@General
	It would be nice to have a meta-all-backups that did some sort
	of scheduling, which could make guesses about what backups to
	start and so on.

	Deal with end of tape somehow.  Maybe use the DeeJay approach,
	create a special backend that can deal with multiple tapes, end
	of tape detection and so on transparently, so that you can use
	dump, tar, cpio with multiple tapes and real EOT detection.
	This should work with tape rollover as well as stackers and
	jukeboxes. 

	Add support for tape stackers and jukeboxes.

	Incorporate tape cleaning schedule in check-backups somehow?

add-tape
	ought to be a way to add N random tapes (rather than having to
	specify n-m)  

all-backups
	copy whole backup database to tape at end of each run

	recovery from reboots - if server running do-backups is
	booted, all-backups hangs forever (rsh screwed up).  this may
	be a problem with rsh - crops up elsewhere also.

	sort errors to the top of mail output? Or should we separate 
	the errors from the rest (somehow) and mail them to two separate
	lists?

	deal with parallel messages better in mail output?

	It would be cool if there were a way to scan a run for backups
	that failed, producing a list of chain, level, host and file
	systems, and pass that to all-backups to catch them up.   Maybe
	use a checklist as in Amanda.

	Add a way to do dumps that aren't recorded for restores in the
	database (and which do not update tardates or dumpdates).

show run
	host lists are often too long, and should be wrapped on the
	screen

move-tape
	would be nice to integrate it more closely with offsite, so 
	that it can keep you from moving tapes to the wrong offsite
	location. 

parallel backups
	deal with case where parallel incr backup fails from lack of
	space - mark as 'redo live', let all-backups do it straight
	onto tape at end of the whole mess. 

	Improve the copy to tape mechanism, make it faster.

backup-dump
	dump probably can't deal with level #'s > 9, maybe we should add
	limits to the stuff that reads backup.config?

	when we skip backups due to .chain problems, ought to note fact in 
	status in per host bu db.

backup-report
	create an ascii version?

getback
	It would be cool to be able to interactively search for a good
	backup sequence.  The program could give its best shot, and
	you could eliminate backups for whatever reason (like this
	one's offsite, or that one's on a tape that's lost) and have
	it deal.

	It would also be nice if it had a way of finding a backup
	sequence in multiple chains that "covers" the time elapsed
	between the full save and now, even if you couldn't use it for a
	real deleting style restore.

	Add ability to load several drives with tapes so that a full or
	interactive restore can run start to finish with no human
	assistance.  Should do some sort of locking so that restores on
	several file systems can proceed in parallel on the same host.

tape-check
	Make it more persistant.

Code
	use packages
	
	document expected globals

	Count arrays with @@foo instead of $#foo in case $[ changes.

installation
	installation checking script

new facilities
	write an analysis program - coverage ok, how many tapes needed?

	write an assessment program that tells, for each file system,
	where "up to date" sets of backups can be found (eg, do I have
	an complete and up to date set for host X stored offsite
	somewhere?)

	more error checking - tapes w/o types, ids with wrong formats, 
	stuff that contains bad characters

	Ought to construct dumpdates and eliminate tardates and use
	data from the backup database instead.  Otherwise, duplication
	of data can lead to problems - if we do a level 2, then reuse
	that tape, the database will not contain that level 2 backup,
	but dumpdates or tardates will retain it, and the next level 9
	will be done as though the level 2 were still around.  If we
	recreate things from the database and use that as the final
	authority, this problem would disappear.  It would also make
	things somewhat simpler, since we would never need to read
	dumpdates/tardates, just write a fake one.

	Ought to reconsider what's in global.defs and move some of that
	stuff to backup.config (like the online repositories and default
	keep values).

	It would be nice if you could type a ? at any prompt and get
	a list of available choices.
@


1.4
log
@misc. updates
@
text
@d1 4
a4 1
Ah, the wish list is finally getting shorter...:-)
d6 11
d28 3
a30 6
	tape rollover - get all pairs, then check all to see that they
	are mounted correctly, then complain and loop.  Should allow 
        user to give just drive names, in which case it should choose
	a tape for each drive, or allow them to specify a tape for
	each drive.  Would be nice if they could specify user names
	for use with rmt...
d32 15
a46 1
checkinout
d56 1
a56 2
clean-db
	Remove empty DB files and their associated sequence files.
d65 3
d69 5
a73 3
	There really ought to be a distinction between tape choice (best
	sequence or all) and restore mode (list of files, interactive or
	full restore).  
a74 8
	It would be nice to have some sort of GUI thing that gave you a
	list of backups and let you select backups and operations with a
	mouse and so on.  It would also be cool to be able to
	interactively search for a good backup sequence.  The program
	could give its best shot, and you could eliminate backups for
	whatever reason (like this one's offsite, or that one's on a
	tape that's lost) and have it deal.

d80 4
a83 2
	When doing a full restore, ought to tell that it is starting the
	restore after it skips to the correct file.
d85 4
a88 1
Misc
d93 3
d98 2
a99 1
	parameterize backup-init, backup-cleanup?
d101 4
a104 1
	analysis program - coverage ok, how many tapes needed?
a119 4
	If a sequence file is nuked, clean-db will fix it.  It would 
	be better to do away with the sequence files somehow - maybe
	by searching for the max id and adding 1.

d123 3
@


1.3
log
@misc updates
@
text
@d59 3
@


1.2
log
@Misc updates for 2.5 release
@
text
@d21 5
d42 3
a44 1
	deal with offsite tapes in a better fashion, whatever that means.
d46 13
d86 5
a90 1
	by searching for the max id and adding 1.
@


1.1
log
@Initial revision
@
text
@a9 3
	tape rollover - get all pairs, then check all to see that the
	are mounted correctly, then complain and loop.

d14 6
a19 3
	combine the -t and -f so we can specify a list of tapes and 
	drives for automatic rollover.  something like -f
	t#@@host:device...what about user names? 
d27 1
a27 3
	maybe need better db consistency checks
	    duplicate t#f# in BUDB
	    duplicate BUID in tape DB
d36 3
a49 2
	db reconstruction program

d63 4
@
