RE: changing volumes on pioe input
Hello, I replying to share with you, what I found out with this problem. Thanks to the one who replyed to me. Well, it took a while for me to find out the following: With solaris 8 you can have a mount opption logging (See the mount_ufs man page). With this I get the error described below. With out this option the restore works fine. On the amanda page there ist a patch available for the advfs but I didn't have the time to try it out if this would fix the problem. The description doesn't really say something about my problem. Maybe somebody tried it already. All in all, what I can say now, be carefully with the logging option for mounting on solaris 8!! Wolfgang -Original Message- From: Mair, Wolfgang [mailto:[EMAIL PROTECTED]] Sent: Montag, 14. Mai 2001 12:34 To: [EMAIL PROTECTED] Subject: changing volumes on pioe input Hello list, can somebody please help me with the following problem: I'm using amanda 2.4.2p2 on Solaris 8 and I don't have a tape device, therfore I need to restore from the holdingdisk. The backup runs fine, I'm doing a full backup (always-full) on each run. But with the restore I'm having problems. I'm trying to restore from the holding disk, after I mounted the directory from the backup server. I use the following command: dd if=/a/20010515/volvo._dev_dsk-c0t0d0s7.0 bs=32k skip=1 | ufsrestore -ifv - After entering the command, the ufsrestore runs fine for a while. Then I get the following message: 42267+0 records in 42267+0 records out changing volumes on pipe input abort? [yn] The only thing I can do at this point is to abort the restore. When I abort it the system core is dumped. It looks to me as it only occurs while restoring partitions arround or greater 1 Gbyte. When I dump the image into a file f. e.: dd if=volvo._dev_dsk-c0t0d0s7.0 bs=32k skip=1 of=volvopart7 and run ufsrestore: ufsrestore -ifv ./volvopart7 ufsrestore expects a second volume. But there is no second volume...:-((( Any help or ideas would be appreciated Wolfgang
RE: client timing out
Title: client timing out Hi, the amandad on the client host ist probably not running. According to the system you use you have to enter something like the following: /etc/services: amanda 10080/udp amandaidx 10082/tcp amidxtape 10083/tcp /etc/inetd.conf: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad After this, don't forgett to send a kill -1 to the pid of the inetd. Wolfgang -Original Message-From: Anthony Carter [mailto:[EMAIL PROTECTED]]Sent: Mittwoch, 16. Mai 2001 17:28To: '[EMAIL PROTECTED]'Subject: client timing out I installed Amanda and I'm trying to backup the client (also the Amanda host). I am getting the message that the client is timing out. Any suggesstions? Thanks Anthony Carter
RE: changing volumes on pioe input
Hi, thanks for the answer. I expected something like this, but unfortunatelly the image is not split into multiple chunks on the holding disk and also with amrestore I get the same message. Amdump runs without error and creates only one image per partition. Even worse I do have the same entry in the disklist file (always-full) for different partitions on the same host. I'm able to restore all other partitions on that host. When I run amdump again I get the same result restoring that host but sometimes with a different partition. Help please, I've got a bad feeling, when I should rely on this.. Wolfgang I'm trying to restore from the holding disk, after I mounted the directory from the backup server. I use the following command: dd if=/a/20010515/volvo._dev_dsk-c0t0d0s7.0 bs=32k skip=1 | ufsrestore -ifv - After entering the command, the ufsrestore runs fine for a while. Then I get the following message: 42267+0 records in 42267+0 records out changing volumes on pipe input abort? [yn] That means ufsrestore did not get the end of image markers it expected. Is your image split into multiple chunks in the holding disk? If so, or even if not, you might want to use amrestore rather than dd to pipe into ufsrestore: amrestore -p /a/20010515/volvo._dev_dsk-c0t0d0s7.0 volvo | ufsrestore ... Amrestore knows about multiple holding disk chunks and will go from one to the other. Using dd to do that will be more challenging :-). Wolfgang John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
changing volumes on pioe input
Hello list, can somebody please help me with the following problem: I'm using amanda 2.4.2p2 on Solaris 8 and I don't have a tape device, therfore I need to restore from the holdingdisk. The backup runs fine, I'm doing a full backup (always-full) on each run. But with the restore I'm having problems. I'm trying to restore from the holding disk, after I mounted the directory from the backup server. I use the following command: dd if=/a/20010515/volvo._dev_dsk-c0t0d0s7.0 bs=32k skip=1 | ufsrestore -ifv - After entering the command, the ufsrestore runs fine for a while. Then I get the following message: 42267+0 records in 42267+0 records out changing volumes on pipe input abort? [yn] The only thing I can do at this point is to abort the restore. When I abort it the system core is dumped. It looks to me as it only occurs while restoring partitions arround or greater 1 Gbyte. When I dump the image into a file f. e.: dd if=volvo._dev_dsk-c0t0d0s7.0 bs=32k skip=1 of=volvopart7 and run ufsrestore: ufsrestore -ifv ./volvopart7 ufsrestore expects a second volume. But there is no second volume...:-((( Any help or ideas would be appreciated Wolfgang
