Hello,
I'm restoring from one RHEL4 to another, using rdiff-backup v. 1.0.4.
SELinux is turned off
Let's call:
- the server where the backup resides: b
- the server I'm trying to restore to: r
The restore process is 3/4 through, but seems stuck now. Backing up is
performed from r, using
rdiff-backup --restore-as-of now backup < at > b::scm /var/restore
On b, load avarage is high, and rdiff-backup has a resident set size of
356MB (rising). On r, load avarage is practically 0.
On b, when I go to /proc/<pid of rdiff-backup>/fd I see:
0 -> a socket
1 -> a socket
2 -> a socket
3 -> /home/backup/HOSTNAME/rdiff-backup-data/restore.log
4 ->
/home/backup/HOSTNAME/rdiff-backup-data/mirror_metadata.2006-02-12TO8:17:7+01:00.snapshot.gz
On r, when I go to /proc/<pid of rdiff-backup/fd I see:
0 -> a socket
1 -> a socket
2 -> a socket
3 -> /var/restore/home/jiratest/mail/.imap/INBOX/rdiff-backup.tmp.146052
4 -> a socket
5 -> a socket
Files in the /home/jiratest/mail/.imap/INBOX are very small and shouldn't
be able to inflict any trouble.
Any ideas about how to proceed in such a situation?
(When I get more time, I might try doing it again with elevated verbosity
levels, but currently, I'll have to re-create my data in other ways.)
--
Greetings from Troels Arvin
