Very Computer

1. Backup and Restore Manager skips root disk during Full Backup

Alan Glendinning schrieb:
 > I replaced my system (root) disk on my Power Indigo2 (IRIX 6.5.17m)
 > last week via a disk cloning procedure.  After formatting the drive
 > with fx I copied over the volume header files via dvhtool and used
 > xfsdump/xfsrestore to copy the files.  Everything went smoothly and
 > the new disk works just fine.  The filesystem looks good and I have no
 > problems accessing or creating any files on it.
 >
 > Unfortunately, when I started a Full backup using the Backup and
 > Restore Manager, the root disk was apparently skipped.  All other
 > internal and external SCSI disks were properly backed up.  I tried
 > starting the procedure again this morning using the
 > /usr/sysadm/privbin/backup command instead of the GUI process, but I'm
 > getting similar results.
 >
 > This is the second time I've replaced the system disk via cloning (did
 > it three years ago) and this did not occur the first time.  The only
 > thing I can think of that may be confusing Backup is that the new disk
 > is quite large (50 Gb).  Is there a size limit to filesystems that
 > Backup will try to process?
 >
 > Thanks in advance,
 > Alan Glendinning
 >

Some places to look at:

   - Backup: Ordinary users cannot do full system backups, and backups
     made by ordinary users will not be able to back up files that the
     user does not have permission to read.

   - Backup uses cpio:

     - Device files with major numbers greater than 127 or
       minor numbers greater than 255 could not normally be
       archived.

     - The types of files that might cause problems are those
       larger than 2 Gbytes, files with holes (no data blocks),
       and device files with major numbers larger than 127 or
       minor numbers larger than 255.

     - Only a super-user user can copy special files.  Additionally,
       when running from a setuid program (or if made setuid itself),
       some files may still not be accessible, since the effective
       userid is checked in several places, rather than the real
       userid.

     - If a file has 000 permissions, contains more than 0 characters
       of data, and the user does not have the appropriate access to
       the file, the file will not be saved or restored.

Regards
Ralf Beyer
--

2. My DLT drive is slow?

3. tape backup only full restore?

4. >>> Amiga chips (Alice, Lisa, .... ) WANTED !!!! <<<

5. 3D Viewer 35

6. Can Backup and Restore Manager use tar?

7. uucp on a DEC ALPHA VMS system - is ther one

8. Full Backups w/o root???

9. Full System disk backup

10. Disk backup/restore using DAT...

11. Error Messages During Backup

12. system backup - Backup fails