Re: holding disk when using HD backup ?
On Tuesday 07 March 2006 15:41, FM wrote: >Sorry if I was no clear enough :-) > >My setup : >1 amanda server with virtual tape (hard disk) >20 remote clients > >My problems : my server is overloaded during the backup. I suppose > that I can play with those parameters to reduce the load : >compress parameter should be client and not on amanda server >reduce inparallel (now 10) >reduce maxdumps (now 4) > I'm not sure the latter 2 will reduce the loading on the server. It really should be capable of keeping up with 20 clients unless the network is some old slow protocol or there simply isn't enough iron in the server to do it. After all, all it should be doing is moving data to the holding disk from the network, and thence to the tape, neither of which, even combined, should make a 400mhz K6 even break a sweat unless its also doing the compression duties for itself as a client at the same time. There is not a not you can do about that except add cpu horsepower & memory. To put that into perspective, this box, an xp-2800 athlon, is also backing up my firewall, a 500mhz k6-III, with the clients all doing their own compression. I have 48 DLE's, 12 of them on that slow box. On nights when level 0's are being done, they are the last 37-48 in the order. On nights when its all level 1, that boxes order ascends to 5 thru 16. In the case I had 20 clients, I would make sure those 20 clients all have unique spindle numbers for every physical disk, and then reset the inparallel to 20 and the maxdumps to 20, which means that all 20 clients can then work at their own pace. The holding disk will fill up if the tape can't handle it, but more holding disk is a commodity item these days with 300GB ATA Seagates with a 5 year warranty at about $130 (after an $80 rebate) at C.City. This is not intended to be gospel, just a suggestion, but thats how I'd approach it till I found differently by experimental results. >thanks! > >Ram "TK" Krishnamurthy wrote: >> Jon >> My comment was for backing upto disks. And I mis-read the original >> post that he was backing to tape. You are correct that holding disk >> is key for dumping multiple dle's. >> >> >> tk >> >> Jon LaBadie wrote: >>> On Tue, Mar 07, 2006 at 12:07:25PM -0800, Ram TK Krishnamurthy wrote: You generally do not use holding disks when backing up to disks. tk FM wrote: > Hello, > > Do I need a holdingdisk when I using hard drive backup ? > > I have a lots of iowait because of the copy from holding disk to > virtual > tape even if the holding disk is on internal SCSI drives and > tapes are on an extrenal SCSI array (using sata drives) >>> >>> Why not Ram? Without a holding disk only one client DLE can >>> be dumped at a time. The holding disk is to allow multiple >>> DLEs to collect simultaneously, only transfered to "tape" >>> when complete. Without a holding disk the DLE must be >>> dumped "directly to tape" eliminating all parallelism. -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: holding disk when using HD backup ?
One other thing [and you might have done this already], take a look at http://wiki.zmanda.com/index.php/Amdump_is_terribly_slow When you say "server is terribly overloaded" I assume you are also seeing the symptom of slow dumps. Thanks tk FM wrote: Sorry if I was no clear enough :-) My setup : 1 amanda server with virtual tape (hard disk) 20 remote clients My problems : my server is overloaded during the backup. I suppose that I can play with those parameters to reduce the load : compress parameter should be client and not on amanda server reduce inparallel (now 10) reduce maxdumps (now 4) thanks! Ram "TK" Krishnamurthy wrote: Jon My comment was for backing upto disks. And I mis-read the original post that he was backing to tape. You are correct that holding disk is key for dumping multiple dle's. tk Jon LaBadie wrote: On Tue, Mar 07, 2006 at 12:07:25PM -0800, Ram TK Krishnamurthy wrote: You generally do not use holding disks when backing up to disks. tk FM wrote: Hello, Do I need a holdingdisk when I using hard drive backup ? I have a lots of iowait because of the copy from holding disk to virtual tape even if the holding disk is on internal SCSI drives and tapes are on an extrenal SCSI array (using sata drives) Why not Ram? Without a holding disk only one client DLE can be dumped at a time. The holding disk is to allow multiple DLEs to collect simultaneously, only transfered to "tape" when complete. Without a holding disk the DLE must be dumped "directly to tape" eliminating all parallelism. -- Ram "TK" Krishnamurthy Amanda Wiki: http://wiki.zmanda.com Amanda Forums:http://forums.zmanda.com
Re: holding disk when using HD backup ?
On Tue, Mar 07, 2006 at 03:41:19PM -0500, FM wrote:
> Sorry if I was no clear enough :-)
>
> My setup :
> 1 amanda server with virtual tape (hard disk)
> 20 remote clients
>
> My problems : my server is overloaded during the backup. I suppose that
> I can play with those parameters to reduce the load :
> compress parameter should be client and not on amanda server
That is "could" not "should" :)
Also consider compress "fast" if you are using "best".
Still get a lot of compression for much less cpu usage.
> reduce inparallel (now 10)
> reduce maxdumps (now 4)
>
IIRC, there is a parameter to specify a start time for a DLE.
Perhaps you could stagger your clients so only a few are
dumping at the same time.
Make sure the spindle(s) for the holding disk do not contain
any DLEs that might be getting backed up at the same time.
The holding disk should be relatively unused. If you must
backup some part of the drive containing the holding disk,
then for those DLEs specify no holding disk and let them
go directly to {v}tape.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: holding disk when using HD backup ?
Ok, I re-read the original as well as this post again. If you are copying multiple DLEs's and you want to be in a single image then holding disk is definitely needed - whether you are flusing to an actual tape or vtape. And the added fact that you have anothe copy, should the actual back up fail. Performance improvement without holding disc is likely to happen when you have only a few [more like 1 or 2], dle's. Thanks tk FM wrote: Sorry if I was no clear enough :-) My setup : 1 amanda server with virtual tape (hard disk) 20 remote clients My problems : my server is overloaded during the backup. I suppose that I can play with those parameters to reduce the load : compress parameter should be client and not on amanda server reduce inparallel (now 10) reduce maxdumps (now 4) thanks! Ram "TK" Krishnamurthy wrote: Jon My comment was for backing upto disks. And I mis-read the original post that he was backing to tape. You are correct that holding disk is key for dumping multiple dle's. tk Jon LaBadie wrote: On Tue, Mar 07, 2006 at 12:07:25PM -0800, Ram TK Krishnamurthy wrote: You generally do not use holding disks when backing up to disks. tk FM wrote: Hello, Do I need a holdingdisk when I using hard drive backup ? I have a lots of iowait because of the copy from holding disk to virtual tape even if the holding disk is on internal SCSI drives and tapes are on an extrenal SCSI array (using sata drives) Why not Ram? Without a holding disk only one client DLE can be dumped at a time. The holding disk is to allow multiple DLEs to collect simultaneously, only transfered to "tape" when complete. Without a holding disk the DLE must be dumped "directly to tape" eliminating all parallelism. -- Ram "TK" Krishnamurthy Amanda Wiki: http://wiki.zmanda.com Amanda Forums:http://forums.zmanda.com
Re: controlling when a box is backed up.
On Tue, Mar 07, 2006 at 03:28:24PM -0500, Matt Hyclak wrote: > Check the starttime parameter in amanda.conf. Great! That looks like just what I was looking for... don't know how I never noticed that in the past. Thanks, Cameron Matheson > Matt > > -- > Matt Hyclak > Department of Mathematics > Department of Social Work > Ohio University > (740) 593-1263
Re: holding disk when using HD backup ?
On Tuesday 07 March 2006 14:58, FM wrote: >Hello, > >Do I need a holdingdisk when I using hard drive backup ? > >I have a lots of iowait because of the copy from holding disk to > virtual tape even if the holding disk is on internal SCSI drives and > tapes are on an extrenal SCSI array (using sata drives) > I think the holding disk is still a good idea. It allows the "tapeing" to proceed in the order that the individual DLE's are completed, and to even have them juggled a bit in sequence in the event you are using a priority string in your amanda.conf. There may well be fragmentation effects to deal with when not using the holding disk since then each DLE would get written in much smaller pieces leading to more severe fragmentation issues. I am not haveing that to a noticeable degree here, and I am using a large (24GB) holding disk. However, when its time to e2fsck that disk, I haven't been aware that fragmentation has ever been over 3%, and even that would be preventable were it practical to make that many partitions, which it isn't. All disks are ext3 formatted here. The holding disk here is not, for obvious reasons, on the same spindle as the vtapes, that would indeed be a "not recommended practice" I believe. It also serves as an emergency backup should something happen to the vtapes disk, a rather important consideration IMO as you can effect a repair of a failed disk before you actually run out of space, in my case even for a 3 or 4 day holiday weekend. Install a new disk, format it, do the mkdirs & labeling, make the link, and amflush it one days worth at a time. No data of importance is lost since my dumpcycle is 4 days here. >thanks ! -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: holding disk when using HD backup ?
Sorry if I was no clear enough :-) My setup : 1 amanda server with virtual tape (hard disk) 20 remote clients My problems : my server is overloaded during the backup. I suppose that I can play with those parameters to reduce the load : compress parameter should be client and not on amanda server reduce inparallel (now 10) reduce maxdumps (now 4) thanks! Ram "TK" Krishnamurthy wrote: > Jon > My comment was for backing upto disks. And I mis-read the original > post that he was backing to tape. You are correct that holding disk is > key for dumping multiple dle's. > > > tk > > Jon LaBadie wrote: >> On Tue, Mar 07, 2006 at 12:07:25PM -0800, Ram TK Krishnamurthy wrote: >> >>> You generally do not use holding disks when backing up to disks. >>> >>> tk >>> >>> FM wrote: >>> Hello, Do I need a holdingdisk when I using hard drive backup ? I have a lots of iowait because of the copy from holding disk to virtual tape even if the holding disk is on internal SCSI drives and tapes are on an extrenal SCSI array (using sata drives) >> >> >> >> Why not Ram? Without a holding disk only one client DLE can >> be dumped at a time. The holding disk is to allow multiple >> DLEs to collect simultaneously, only transfered to "tape" >> when complete. Without a holding disk the DLE must be >> dumped "directly to tape" eliminating all parallelism. >> >
Re: holding disk when using HD backup ?
Jon My comment was for backing upto disks. And I mis-read the original post that he was backing to tape. You are correct that holding disk is key for dumping multiple dle's. tk Jon LaBadie wrote: On Tue, Mar 07, 2006 at 12:07:25PM -0800, Ram TK Krishnamurthy wrote: You generally do not use holding disks when backing up to disks. tk FM wrote: Hello, Do I need a holdingdisk when I using hard drive backup ? I have a lots of iowait because of the copy from holding disk to virtual tape even if the holding disk is on internal SCSI drives and tapes are on an extrenal SCSI array (using sata drives) Why not Ram? Without a holding disk only one client DLE can be dumped at a time. The holding disk is to allow multiple DLEs to collect simultaneously, only transfered to "tape" when complete. Without a holding disk the DLE must be dumped "directly to tape" eliminating all parallelism. -- Ram "TK" Krishnamurthy Amanda Wiki: http://wiki.zmanda.com Amanda Forums:http://forums.zmanda.com
Re: controlling when a box is backed up.
On Tue, Mar 07, 2006 at 01:09:55PM -0700, Cameron Matheson enlightened us: > I haven't ever learned too much about how amanda's scheduler works (mostly > because it does just work), but now I have a situation which requires a bit > more control. I have a box that needs to be backed up any time after 2:00am, > but my backups start at 12:30am. Ideally I would like to keep my backups > starting at 12:30. Is there a way to control what time a certain box is > backed > up? I checked the docs, but didn't see anything. > Check the starttime parameter in amanda.conf. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
controlling when a box is backed up.
Hi guys, I haven't ever learned too much about how amanda's scheduler works (mostly because it does just work), but now I have a situation which requires a bit more control. I have a box that needs to be backed up any time after 2:00am, but my backups start at 12:30am. Ideally I would like to keep my backups starting at 12:30. Is there a way to control what time a certain box is backed up? I checked the docs, but didn't see anything. Thanks, Cameron Matheson
Re: holding disk when using HD backup ?
On Tue, Mar 07, 2006 at 12:07:25PM -0800, Ram TK Krishnamurthy wrote: > You generally do not use holding disks when backing up to disks. > > tk > > FM wrote: > >Hello, > > > >Do I need a holdingdisk when I using hard drive backup ? > > > >I have a lots of iowait because of the copy from holding disk to virtual > >tape even if the holding disk is on internal SCSI drives and tapes are > >on an extrenal SCSI array (using sata drives) Why not Ram? Without a holding disk only one client DLE can be dumped at a time. The holding disk is to allow multiple DLEs to collect simultaneously, only transfered to "tape" when complete. Without a holding disk the DLE must be dumped "directly to tape" eliminating all parallelism. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: holding disk when using HD backup ?
You generally do not use holding disks when backing up to disks. tk FM wrote: Hello, Do I need a holdingdisk when I using hard drive backup ? I have a lots of iowait because of the copy from holding disk to virtual tape even if the holding disk is on internal SCSI drives and tapes are on an extrenal SCSI array (using sata drives) thanks ! -- Ram "TK" Krishnamurthy Amanda Wiki: http://wiki.zmanda.com Amanda Forums:http://forums.zmanda.com
holding disk when using HD backup ?
Hello, Do I need a holdingdisk when I using hard drive backup ? I have a lots of iowait because of the copy from holding disk to virtual tape even if the holding disk is on internal SCSI drives and tapes are on an extrenal SCSI array (using sata drives) thanks !
Re: amrecover tar: ./tmp/enterprise-file-recovery: Cannot open: Not a directory
Hi Alexander I was able to extract the file to ./tmp/myserver-file-recovery as a test exercise. Cheers For the pointer. On Tue, 2006-03-07 at 14:28 +0100, Alexander Jolk wrote: > Chuck Amadi Systems Administrator wrote: > > I still unable to trouble shoot I can see the file and other files and > > directories but unable to extract. > > > > Error Message output > > > > amanda tar: ./tmp/myserver-file-recovery: Cannot open: Not a directory > > > > tar: Error exit delayed from previous errors > > It would seem to me you didn't have the necessary permissions to create > the directory `tmp' when you did the restore. That's either because you > weren't root, or you were on an NFS-mounted file-system with root > squashing, or a file named `tmp' existed in your current directory. > > I always restore (space permitting) into my machine's local /tmp as > root, in order to avoid this kind of problem. > > Alex > > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: LTO.ps anyone ?
2006/3/7, Paul Bijnens <[EMAIL PROTECTED]>: > On 2006-03-07 15:51, Guy Dallaire wrote: > > Did anyone on the list take the time to create an LTO.ps label > > template for LTO tapes ? If so, where can I find it ? > > > > I'll be moving from DLT to LTO shortly and would appreciate labels > > juste like with my DLT. > > Aren't they exactly the same size (paperwise)? > > > -- According to the specs, there are a couple mm difference on the height, width and length...
Re: LTO.ps anyone ?
On 2006-03-07 15:51, Guy Dallaire wrote: Did anyone on the list take the time to create an LTO.ps label template for LTO tapes ? If so, where can I find it ? I'll be moving from DLT to LTO shortly and would appreciate labels juste like with my DLT. Aren't they exactly the same size (paperwise)? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Setting filetape sizes
On Tue, Mar 07, 2006 at 06:34:50AM -0800, Wayne Johnson wrote: > I am using filetapes for backups. I have a 120GB Raid array that > I back up to another 120GB single drive. Unfortunately, I've > started getting an error during the nightly backup: > > taper: tape daily20 KB 4194272 fm 8 writing file: No space left on device > taper: retrying devserv:/common.2 on new tape: [writing file: No space > left on device] > taper: tape daily21 KB 0 fm 0 [OK] > > I assume this is because the new files on this "disk" are larger than > the filetape volume. I figured 4GB would be plenty for a file volume, > but someone added a new directory with 9 GB of data. Oops. Yeah, 9GB is a tight squeeze in a 4GB tape ;) > What is a good size to use for filetape volumes? Can I change these > sizes after I've started using them? What would be the best way to > get out of the situation I'm in? For a physical tape, when you run out of plastic ribbon, you are out of space regardless of what the tapetype says. For vtapes, I think the situation is different. The vtape driver tries to respect the size value in your tapetype definition. So you can "run out of space" because you exceed your tapetype def or because the hard disk file system ran out of space. Assuming you don't have FS space problems, I think you can just up your tapetype def and claim a bigger size. Then the question becomes something like "how many vtapes should/can I have and how big should I claim them to be". I've been thinking of analogies for this decision making. I think the "cellular phone plan" analogy works. Two types of plans, fixed monthly minutes and loss of unused minutes vs. rollover of unused minutes. If you have a 100GB space for vtapes and want 20 dumps stored (say four weeks worth of dumps Mon - Fri), then "obviously" the tapetype size should be 5GB each. That is the "fixed minutes" plan. But with this you find you run out of minutes some months (opps, I mean out of space some dumps) and some months you have minutes left over. Try the rollover minutes (GB) plan. Increase your apparent monthly minutes (tapetype size) to a larger number. Then any months (dumps) that didn't fit before can use the unused minutes (GB) from smaller months. Of course, if you talk a lot (dump a lot) for too many months, you will run out of your rollover minutes (i.e. the total file system). Only you can find, and maintain, the right balance of maximum dump size, number of vtapes, and file system size. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
LTO.ps anyone ?
Did anyone on the list take the time to create an LTO.ps label template for LTO tapes ? If so, where can I find it ? I'll be moving from DLT to LTO shortly and would appreciate labels juste like with my DLT. Thanks
Setting filetape sizes
I am using filetapes for backups. I have a 120GB Raid array that I back up to another 120GB single drive. Unfortunately, I've started getting an error during the nightly backup: taper: tape daily20 KB 4194272 fm 8 writing file: No space left on device taper: retrying devserv:/common.2 on new tape: [writing file: No space left on device] taper: tape daily21 KB 0 fm 0 [OK]I assume this is because the new files on this "disk" are larger than the filetape volume. I figured 4GB would be plenty for a file volume, but someone added a new directory with 9 GB of data. Oops.What is a good size to use for filetape volumes? Can I change these sizes after I've started using them? What would be the best way to get out of the situation I'm in?Thanks for any help you can give me.---Wayne Johnson, | There are two kinds of people: Those 3943 P! enn Ave. N. | who say to God, "Thy will be done," Minneapolis, MN 55412-1908 | and those to whom God says, "All right, (612) 522-7003 | then, have it your way." --C.S. Lewis Yahoo! Mail Bring photos to life! New PhotoMail makes sharing a breeze.
Re: amrecover tar: ./tmp/enterprise-file-recovery: Cannot open: Not a directory
Hi Alexander Thanks Yes I was hoping to extract to my /home/chuck which is NFS mounted as this is also the main file and document server. Thus I have cd on my backup server /tmp directory and will try again Cheers On Tue, 2006-03-07 at 14:28 +0100, Alexander Jolk wrote: > Chuck Amadi Systems Administrator wrote: > > I still unable to trouble shoot I can see the file and other files and > > directories but unable to extract. > > > > Error Message output > > > > amanda tar: ./tmp/myserver-file-recovery: Cannot open: Not a directory > > > > tar: Error exit delayed from previous errors > > It would seem to me you didn't have the necessary permissions to create > the directory `tmp' when you did the restore. That's either because you > weren't root, or you were on an NFS-mounted file-system with root > squashing, or a file named `tmp' existed in your current directory. > > I always restore (space permitting) into my machine's local /tmp as > root, in order to avoid this kind of problem. > > Alex > > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: amrecover tar: ./tmp/enterprise-file-recovery: Cannot open: Not a directory
Chuck Amadi Systems Administrator wrote: I still unable to trouble shoot I can see the file and other files and directories but unable to extract. Error Message output amanda tar: ./tmp/myserver-file-recovery: Cannot open: Not a directory tar: Error exit delayed from previous errors It would seem to me you didn't have the necessary permissions to create the directory `tmp' when you did the restore. That's either because you weren't root, or you were on an NFS-mounted file-system with root squashing, or a file named `tmp' existed in your current directory. I always restore (space permitting) into my machine's local /tmp as root, in order to avoid this kind of problem. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: amrecover tar: ./tmp/enterprise-file-recovery: Cannot open: Not a directory
Hi List I have had a look at my amrecover.20060307101502.debug on my main backup server. cd /tmp/amanda less amrecover.20060307101502.debug amrecover: debug 1 pid 22161 ruid 0 euid 0: start at Tue Mar 7 10:15:02 2006 amrecover: stream_client_privileged: connected to 193.xxx.xx.xxx.10082 amrecover: stream_client_privileged: our side is 0.0.0.0.951 amrecover: pid 22161 finish time Tue Mar 7 10:22:03 2006 I still unable to trouble shoot I can see the file and other files and directories but unable to extract. Error Message output amanda tar: ./tmp/myserver-file-recovery: Cannot open: Not a directory tar: Error exit delayed from previous errors extract_list - child returned non-zero status: 2 Continue [?/Y/n/r]? n Cheers On Tue, 2006-03-07 at 11:21 +, Chuck Amadi Systems Administrator wrote: > Hi List > > I am attempting to recover a md5sum file I created to run a test > exercise. > > Created myserver-file-recovery 0n the 06/03/2006 (run md5sum on the file > ready for that evenings backup). > > On the 07/03/2006 deleted the myserver-file-recovery file > > [EMAIL PROTECTED]:/home/chuck # amrecover -C DailySet1 -s > backupserver.my.co.uk -t > AMRECOVER Version 2.4.4p2. Contacting server on > backupserver.my.co.uk ... > 220 backup AMANDA index server (2.4.4p2) ready. > 200 Access OK > Setting restore date to today (2006-03-07) > 200 Working date set to 2006-03-07. > Warning: no log files found for tape SMTLSet105 written 2006-02-23 > Warning: no log files found for tape SMTLSet104 written 2006-02-22 > Warning: no log files found for tape SMTLSet103 written 2006-02-21 > Warning: no log files found for tape SMTLSet102 written 2006-02-20 > Warning: no log files found for tape SMTLSet101 written 2006-02-17 > Warning: no log files found for tape SMTLSet110 written 2006-02-16 > Scanning /backup/amanda-daily... > > > amrecover> sethost myserver.my.co.uk > > 200 Dump host set to myserver.my.co.uk. > > amrecover> setdisk / > > 200 Disk set to /. > > amrecover> setdate 2006-03-06 > > 200 Working date set to 2006-03-06. > > amrecover> ls > > amrecover> cd /tmp > > /tmp > > amrecover> ls > > amrecover> add myserver-file-recovery > > Added /tmp/myserver-file-recovery > > amrecover> extract > > > Extracting files using tape drive /dev/nst0 on host > backupserver.my.co.uk. > > The following tapes are needed: SMTLSet109 > > > Restoring files into directory /home/chuck > > Continue [?/Y/n]? y > > > Extracting files using tape drive /dev/nst0 on host > backupserver.my.co.uk. > > Load tape SMTLSet109 now > > Continue [?/Y/n/s/t]? y > > > Error Message output after I put the SMTLSet109 tape. > > amanda tar: ./tmp/myserver-file-recovery: Cannot open: Not a directory > > Any Ideas whats going on I want to extract a File and please advise or > point me in the right direction I have used this procedure on my other > hosts and all was well except this host hides behind a firewall. > > Cheers > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
amrecover tar: ./tmp/enterprise-file-recovery: Cannot open: Not a directory
Hi List I am attempting to recover a md5sum file I created to run a test exercise. Created myserver-file-recovery 0n the 06/03/2006 (run md5sum on the file ready for that evenings backup). On the 07/03/2006 deleted the myserver-file-recovery file [EMAIL PROTECTED]:/home/chuck # amrecover -C DailySet1 -s backupserver.my.co.uk -t AMRECOVER Version 2.4.4p2. Contacting server on backupserver.my.co.uk ... 220 backup AMANDA index server (2.4.4p2) ready. 200 Access OK Setting restore date to today (2006-03-07) 200 Working date set to 2006-03-07. Warning: no log files found for tape SMTLSet105 written 2006-02-23 Warning: no log files found for tape SMTLSet104 written 2006-02-22 Warning: no log files found for tape SMTLSet103 written 2006-02-21 Warning: no log files found for tape SMTLSet102 written 2006-02-20 Warning: no log files found for tape SMTLSet101 written 2006-02-17 Warning: no log files found for tape SMTLSet110 written 2006-02-16 Scanning /backup/amanda-daily... amrecover> sethost myserver.my.co.uk 200 Dump host set to myserver.my.co.uk. amrecover> setdisk / 200 Disk set to /. amrecover> setdate 2006-03-06 200 Working date set to 2006-03-06. amrecover> ls amrecover> cd /tmp /tmp amrecover> ls amrecover> add myserver-file-recovery Added /tmp/myserver-file-recovery amrecover> extract Extracting files using tape drive /dev/nst0 on host backupserver.my.co.uk. The following tapes are needed: SMTLSet109 Restoring files into directory /home/chuck Continue [?/Y/n]? y Extracting files using tape drive /dev/nst0 on host backupserver.my.co.uk. Load tape SMTLSet109 now Continue [?/Y/n/s/t]? y Error Message output after I put the SMTLSet109 tape. amanda tar: ./tmp/myserver-file-recovery: Cannot open: Not a directory Any Ideas whats going on I want to extract a File and please advise or point me in the right direction I have used this procedure on my other hosts and all was well except this host hides behind a firewall. Cheers -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
