On Tue, 12 Dec 2006, Kern Sibbald wrote: >> The solution proposed is to keep file flags in a list and set them after >> all files have been restored, so that all hardlinks can be created. Though >> it is probably enough to do this for hardlinked files. Looks like this >> would make the restore code even more complicated. > > Not only is it more complicated, but it can be very expensive. Suppose you > are restoring a million hard linked files. That could mean that you need > you will need to keep a list that could amount to hundreds of millions of > bytes (you need to keep at least forward links, the full path and the file, > as well as certain of the file attributes).
Sounds perfect for a database table.... >> But what is the solution if you restore a file from an incremental backup >> which is a hardlink to an IMMUTABLE file? Um... why would you ever restore in place unless it's disaster recovery? > Off hand, I would say that the FreeBSD guys have worked themselves into a big > hole. They have violated the rule that says that root can do anything. Linux has similar issues for immutable filesystems. In many environments it's important that root _can't_ do anything unless it's taken the initial step of removing the safety catch off the shotgun first. (Eg: Webservers, other easily compromised systems as a starting point) AB ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
