lui
asked on
problem with rdump from HP-UX to Solaris
I have a problem to dump a HP-UX 09.01 filesystem on a Sun running Solaris 5.4, over a LAN.
The dump command that i use is running on the same HP-UX System with success.
The successfull dump-partition is smaler than ~3 GB. The problem appears with partitions that are greater than ~3 GB.
The storage-medium is a 4mm DAT Autoloader with a capacity of ~8 GB, i have tested it on a 8 mm Exabyte-DAT too, without success.
I use the following command-lines (2 lines) in a shell-script, that runs on the SUN :
echo "Dump hp1 /dev/dsk/c201d2s0 mountpoint /users1 vom `date`
EXITCODE=`rsh hp1 "(/etc/rdump 0ubdsf 126 54000 6000 sun46:$LAUFWERK /dev/dsk/c201d2s0 && echo ok)"
And this is the output on the SUN :
Dump hp1 /dev/dsk/c201d2s0 mountpoint /users1 vom Tue Dec 2 01:38:53 MET 1997
DUMP: Date of this level 0 dump: Tue Dec 2 02:41:47 1997
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/rdsk/c201d2s0 (/users1) to /dev/rmt/1cn on host sun46
DUMP: This is an HP long file name filesystem
DUMP: mapping (Pass I) [regular files]
DUMP: mapping (Pass II) [directories]
DUMP: estimated 3039625 tape blocks on -0.07 tape(s).
DUMP: dumping (Pass III) [directories]
DUMP: dumping (Pass IV) [regular files]
DUMP: 2.93% done, finished in 2:45
DUMP: 6.23% done, finished in 2:30
DUMP: 9.50% done, finished in 2:22
DUMP: 12.78% done, finished in 2:16
DUMP: 16.09% done, finished in 2:10
DUMP: 19.53% done, finished in 2:03
DUMP: 24.06% done, finished in 1:50
DUMP: 28.63% done, finished in 1:39
DUMP: 33.22% done, finished in 1:30
DUMP: 37.79% done, finished in 1:22
DUMP: 42.34% done, finished in 1:14
DUMP: 46.24% done, finished in 1:09
DUMP: 50.27% done, finished in 1:04
DUMP: 54.54% done, finished in 0:58
DUMP: 58.67% done, finished in 0:52
DUMP: 62.07% done, finished in 0:48
DUMP: 65.22% done, finished in 0:45
DUMP: 68.32% done, finished in 0:41
DUMP: 71.50% done, finished in 0:37
DUMP: 74.71% done, finished in 0:33
DUMP: 77.78% done, finished in 0:29
DUMP: 80.99% done, finished in 0:25
DUMP: 84.91% done, finished in 0:20
DUMP: 88.93% done, finished in 0:14
DUMP: 92.96% done, finished in 0:09
DUMP: Tape rewinding
DUMP: Change Tapes: Mount tape #2
DUMP: fopen on /dev/tty fails
DUMP: The ENTIRE dump is aborted.
The dump with the following stations is successfull, so the tape is not full.
I hope someone can help me !.
Thank you.
The dump command that i use is running on the same HP-UX System with success.
The successfull dump-partition is smaler than ~3 GB. The problem appears with partitions that are greater than ~3 GB.
The storage-medium is a 4mm DAT Autoloader with a capacity of ~8 GB, i have tested it on a 8 mm Exabyte-DAT too, without success.
I use the following command-lines (2 lines) in a shell-script, that runs on the SUN :
echo "Dump hp1 /dev/dsk/c201d2s0 mountpoint /users1 vom `date`
EXITCODE=`rsh hp1 "(/etc/rdump 0ubdsf 126 54000 6000 sun46:$LAUFWERK /dev/dsk/c201d2s0 && echo ok)"
And this is the output on the SUN :
Dump hp1 /dev/dsk/c201d2s0 mountpoint /users1 vom Tue Dec 2 01:38:53 MET 1997
DUMP: Date of this level 0 dump: Tue Dec 2 02:41:47 1997
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/rdsk/c201d2s0 (/users1) to /dev/rmt/1cn on host sun46
DUMP: This is an HP long file name filesystem
DUMP: mapping (Pass I) [regular files]
DUMP: mapping (Pass II) [directories]
DUMP: estimated 3039625 tape blocks on -0.07 tape(s).
DUMP: dumping (Pass III) [directories]
DUMP: dumping (Pass IV) [regular files]
DUMP: 2.93% done, finished in 2:45
DUMP: 6.23% done, finished in 2:30
DUMP: 9.50% done, finished in 2:22
DUMP: 12.78% done, finished in 2:16
DUMP: 16.09% done, finished in 2:10
DUMP: 19.53% done, finished in 2:03
DUMP: 24.06% done, finished in 1:50
DUMP: 28.63% done, finished in 1:39
DUMP: 33.22% done, finished in 1:30
DUMP: 37.79% done, finished in 1:22
DUMP: 42.34% done, finished in 1:14
DUMP: 46.24% done, finished in 1:09
DUMP: 50.27% done, finished in 1:04
DUMP: 54.54% done, finished in 0:58
DUMP: 58.67% done, finished in 0:52
DUMP: 62.07% done, finished in 0:48
DUMP: 65.22% done, finished in 0:45
DUMP: 68.32% done, finished in 0:41
DUMP: 71.50% done, finished in 0:37
DUMP: 74.71% done, finished in 0:33
DUMP: 77.78% done, finished in 0:29
DUMP: 80.99% done, finished in 0:25
DUMP: 84.91% done, finished in 0:20
DUMP: 88.93% done, finished in 0:14
DUMP: 92.96% done, finished in 0:09
DUMP: Tape rewinding
DUMP: Change Tapes: Mount tape #2
DUMP: fopen on /dev/tty fails
DUMP: The ENTIRE dump is aborted.
The dump with the following stations is successfull, so the tape is not full.
I hope someone can help me !.
Thank you.
ASKER
Adjusted points to 105
You might want to make a comment on why you rejected that
answer. Check the man page, you'll find that I am right.
(man ufsdump - s and d flags only control ufsdump notion of
end of tape)
If increasing one doesn't work, than increase the other one
instead.
answer. Check the man page, you'll find that I am right.
(man ufsdump - s and d flags only control ufsdump notion of
end of tape)
If increasing one doesn't work, than increase the other one
instead.
ASKER
Sorry.
I must test that first.
The Backup is running at night, so i can´t say its successfull or not.
I must test that first.
The Backup is running at night, so i can´t say its successfull or not.
Well, it's too late now, but you probably should test the
solution before rejecting the answer. Otherwise, the
person who gives the correct answer may not get any credit.
That wouldn't be fair, would it?
solution before rejecting the answer. Otherwise, the
person who gives the correct answer may not get any credit.
That wouldn't be fair, would it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
be far too little to backup to an 8GB tape. You need to
increase either the s or the d arguments. It doesn't matter
which since both are superfluous. The only thing they do
is tell you how much of the dump is remaining. I'm not sure
what the exact values are for an 8GB dat, but, since your primary goal
is probably just to GET IT TO WORK! :), just do 4X the s
value to make it 24000, which should be approximately close.