On 04/04 07:14 , Holger Parplies wrote: > in particular, they are compressed, so the end of the file is in my experience > usually a considerable amount behind the file currently copying. This is also > the reason you can't simply "switch off buffering" for the log files > (compression needs reasonably sized chunks to operate on for efficient > results). It might make sense to think about (optionally) writing log files > uncompressed and compressing them after the backup has finished. Wanting to > follow backup progress seems to be a frequent enough requirement. Putting the > log files on a disk separate from the pool FS should probably be encouraged in > this case ;-).
These are all terribly good points. Perhaps the current file can simply be stored in memory and presented via the web interface? Is there a variable that already exists and can be read by the web interface to present the current file being copied? -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com ------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
