Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!uakari.primate.wisc.edu!aplcen!haven!udel!burdvax!gvlv2!gvlf9-e!tim
From: tim@gvlf9-e.gvl.unisys.com (Timothy Scharping)
Newsgroups: comp.sys.apollo
Subject: Re: Tar Backups
Message-ID: <503@gvlv2.GVL.Unisys.COM>
Date: 18 Jan 90 14:59:53 GMT
References: <1990Jan17.185931.21912@idacom.uucp>
Sender: news@gvlv2.GVL.Unisys.COM
Reply-To: tim@gvl.unisys.com (Timothy Scharping)
Organization: Unisys Defense Systems, Great Valley Labs, Paoli, Pa
Lines: 23

In article <1990Jan17.185931.21912@idacom.uucp> danny@idacom.uucp (Danny Wilson) writes:
>
>There is a big problem with tar for doing backups if your backup
>spans multiple tapes.  This is not a particular problem with Apollo,
>just tar in general.
>
>This means that, for example, you want to backup a 10 Meg directory
>and only have 5 Meg tape, tar will only backup half the directory!
>
>It does not prompt for a second tape and will not inform you that
>data was not recorded.
>

	I have also encountered another problem with using tar for complete
system backups.  There seem to be several files which tar isn't able to read
(i.e. `node_data/system_logs/sys_error_log).  When tar is comes accross a file
that can't be opened it chokes causing it to hang on our DN3550.

--tim
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Timothy Scharping       Internet: tim@GVL.Unisys.COM
Unisys Corporation	UUCP: ...!uunet!lgnp1!gvlv2!tim  
Paoli, PA  19301              ...!{gatech,purdue}!psuvax1!burdvax!gvlv2!tim