Re: Debugging empty index files

> "JLT" == Jason L Tibbitts writes: JLT> And that's what I did and it shows the problem pretty clearly: JLT> xfsrestore is segfaulting. In fact, xfsrestore segfaults trying to JLT> restore any of the backups of this filesystem. I should really be fair to the XFS devs

Re: Debugging empty index files

>>>>> "JLT" == Jason L Tibbitts <ti...@math.uh.edu> writes: JLT> Are there any tricks for trying to duplicate the index generation? JLT> I guess I could try to pull a raw dump file off of tape and run the JLT> same xfsrestore command line and see what happ

Debugging empty index files

I'm having a problem where one of my hosts has one filesystem which apears to back up perfectly fine, but produces an empty index file. Specifically, the (timestamp)_(level).gz file comes out to be exactly 20 bytes, and uncompressed it's completely empty. The machine is Fedora 24, and I've tried

Re: 'no index records...' or Linux -- FreeBSD migration

On Thu, 30 Jan 2014 08:42:51 -0500 Jean-Louis Martineau martin...@zmanda.com wrote: A downgrade of the server is not expected to works, the format of the amanda database (log files) might have changed. What's the output of 'amadmin CONF find'? If it report 'no log files found for

Re: 'no index records...' or Linux -- FreeBSD migration

Saša Janiška sjani...@gmail.com (Do 30 Jan 2014 09:44:09 CET): Hello! I'm migrating from Linux to Free/PC-BSD and have problem amrecovering backup due to 'no index records'. On Linux amrecover works and I did cp-ed (on smaller USB disk) all my / including amanda setup. The difference

Re: 'no index records...' or Linux -- FreeBSD migration

substitutions for '/') gour  atmarama  ~  $ amgetconf backup INDEXDIR /var/db/amanda/state/index These folders contain *.gz and *.header files. The *.gz are simple compressed text files, having line by line the names of the saved object. [gour@atmarama] /usr/home/gour# ls -l /var/db

Re: 'no index records...' or Linux -- FreeBSD migration

On Tue, 4 Feb 2014 13:12:49 +0100 Heiko Schlittermann h...@schlittermann.de wrote: The .tmp is somehow suspicious… I'd say the backup broke. At least the indexing broke. That's true, but on Jan 29th I did another full backup which I can restore on Linux, but on Free/PC-BSD. Sincerely, Sasa

Re: 'no index records...' or Linux -- FreeBSD migration

3.3.3. If it report all dumps, then the 'indexdir' is nor set correctly. Jean-Louis On 01/30/2014 03:44 AM, Saša Janiška wrote: Hello! I'm migrating from Linux to Free/PC-BSD and have problem amrecovering backup due to 'no index records'. On Linux amrecover works and I did cp-ed (on smaller USB

Re: 'no index records...' or Linux -- FreeBSD migration

On Thu, Jan 30, 2014 at 2:42 PM, Jean-Louis Martineau martin...@zmanda.comwrote: A downgrade of the server is not expected to works, the format of the amanda database (log files) might have changed. Ahh...that sucks. I was expected that the same major version 3.3.x should work. :-( What's

'no index records...' or Linux -- FreeBSD migration

Hello! I'm migrating from Linux to Free/PC-BSD and have problem amrecovering backup due to 'no index records'. On Linux amrecover works and I did cp-ed (on smaller USB disk) all my / including amanda setup. The difference is that on Linux state files are under /var/lib/amanda/... while

Problem: 599 System error index file not found

Hello, We have problem 599 System error index file not found in using 'amrecover' for one DLE (ibs5 /export/home3/./g-m) and no problem for other DLE from the same host (ibs5 /export/home3/./t-z): --- AMRECOVER Version 2.5.2p1. Contacting server on ibs4 ... 220 ibs4 AMANDA index server (2.5.2p1

No index records after upgrade

anything using amrecover: amrecover BACKUP AMRECOVER Version 3.2.0. Contacting server on mail.mydomain.ee ... 220 mail AMANDA index server (3.2.0) ready. Setting restore date to today (2010-12-13) 200 Working date set to 2010-12-13. 200 Config set to BACKUP. 200 Dump host set to mail.mydomain.ee

Re: No index records after upgrade

as before (backup). Hostname is also same, and the name resolution in DNS is correct. Amcheck passes with no problems. However, I can't restore anything using amrecover: amrecover BACKUP AMRECOVER Version 3.2.0. Contacting server on mail.mydomain.ee ... 220 mail AMANDA index server (3.2.0) ready

index removal question

skip' stanza in the dumptypes while we researched/solved the issue. This is with amanda-2.6.1p2 both on clients and servers. Once the firmware issue was sorted out and the affected raidsets rebuilt I tried to restore them as they were prior to the failure just to see that the index files

Re: index removal question

Jean-Francois, It is a bug that the index files are removed for 'strategy skip' dles. The attached patch fix it. Jean-Louis Jean-Francois Malouin wrote: Hi, Last Friday we got bitten by a rather vicious raid controller firmware/codeset that corrupted some of our raidsets when a disk failed

Re: index removal question

* Jean-Louis Martineau martin...@zmanda.com [20100112 14:27]: Jean-Francois, It is a bug that the index files are removed for 'strategy skip' dles. The attached patch fix it. Thanks Jean-Louis, I've applied the patch and will recompile later. jf Jean-Louis Jean-Francois Malouin wrote

Amanda error: sendbackup: index tee cannot write [Bad file descriptor]

/tar -xpGf - ... sendbackup: info end ? sendbackup: index tee cannot write [Bad file descriptor] | Total bytes written: 71680 (70KiB, ?/s) ? /bin/tar: -: Wrote only 2048 of 10240 bytes ? /bin/tar: Error is not recoverable: exiting now ? index index returned 1 ? dump (17333) /bin/tar returned 2

Re: 599 System error index file not found

ministryofinformation AMANDA index server (2.5.2p1) ready. Setting restore date to today (2009-04-17) 200 Working date set to 2009-04-17. Was a dump done on April 17, or was it still pending. If not, then there would be no index for that working date. Use setdate to an earlier time for which dumps

No Index - date not correct

Hi All, I am having a weird issue with the following server? 200 Disk set to /mnt/fileserver1/bb-share/project/. No index records for disk for specified date If date correct, notify system administrator amrecover The date is same on both server and client, but still have this error

Re: no Index on client

/amanda/fullback# log directory indexdir /var/lib/amanda/fullback/index # index directory amrecover_do_fsf yes amrecover_check_label yes holdingdisk hd1 { comment main holding disk directory /var/tmp/amanda use 1000 Mb # chunksize 2 Gb # size of chunk if you want big

No Index on client.

Hi All, I have added a slackware host to a backup schedule and there is no index for the host. Amrecover shows the following for host webtwo and test directory is /usr/local/amanda 200 Disk set to /usr/local/amanda/. No index records for disk for specified date If date correct, notify system

Index files and no-reuse

be overwritten (digital preservation). Are index files of tapes set to no-reuse removed after 12 month (tapecycle 12 tapes)? Or do I have to keep them somewhere else to have a comfortable recovering using amrecover? Regards Marc -- Marc Muehlfeld (Leitung IT) Zentrum fuer Humangenetik und

Re: Index files and no-reuse

to no-reuse and will never be overwritten (digital preservation). Are index files of tapes set to no-reuse removed after 12 month (tapecycle 12 tapes)? Or do I have to keep them somewhere else to have a comfortable recovering using amrecover? No, the index files are not erased after a dumpcycle

missing index

Hi, need to recover a storage volume and the amanda index is missing. There seems to be lots of data on the tape for the volume. Is it possible to build an amanda index from the tape? I used tar for the backup. I've got a file listing of whats on the tape by doing: amrestore -f12 -p /dev

Re: missing index

On Tue, May 20, 2008 at 9:42 AM, A.M.A.N.D.A. Materials [EMAIL PROTECTED] wrote: amrestore -f12 -p /dev/st0 brokenserver /media/disk | tar tvf - list.tar Can I use the listing as the index or is there a neat amanda command to build the index properly? You can use that file listing

Re: missing index

Can I use the listing as the index or is there a neat amanda command to build the index properly? You can use that file listing as an index, as thats exactly how Amanda builds the index. There's currently no neat amanda command to do this, although it is planned as part of the Application API

Re: No index files being generated - possible freebsd-ism or shell specific issues

/amanda --with-index-server=amanda.utexas.edu --without-ipv6 - created a dumptype on the amanda server with the following: define dumptype ssh-encrypt { global program GNUTAR comment No compression, using TAR and client symmetric encryption compress none

Re: No index files being generated - possible freebsd-ism or shell specific issues

On Thu, Apr 3, 2008 at 9:40 PM, Oscar Ricardo Silva [EMAIL PROTECTED] wrote: I think I'm getting closer to getting this working on FreeBSD and my past errors were a combination of hardheadedness and incorrect documentation. Some of the encryption documentation points to the need to create your

Re: No index files being generated - possible freebsd-ism or shell specific issues

Dustin J. Mitchell wrote: On Thu, Apr 3, 2008 at 9:40 PM, Oscar Ricardo Silva [EMAIL PROTECTED] wrote: I think I'm getting closer to getting this working on FreeBSD and my past errors were a combination of hardheadedness and incorrect documentation. Some of the encryption documentation points

No index files being generated - possible freebsd-ism or shell specific issues

appear to run without a hitch, I can't restore. These problems are all on FreeBSD machines, 4.x on up through 6.3. I can launch amrecover and it communicates with the amanda server. When I try to list files I get the error: No index records for disk for specified date If date correct, notify

amrecover complains about missing index

Hi, when I try to run amrecover and call it like: [EMAIL PROTECTED] $ amrecover -C DAILYSET -s tapehost -t tapehost -d /dev/nst0 the answer is: 501 Index directory /var/lib/amanda/DAILYSET/index does not exist and then: amrecover sethost HOST.LAN it shows me: 501 Must set config before setting

Re: amrecover complains about missing index

Why /var/lib/amanda/DAILYSET/index does not exist? Do you generate index? What's the index setting on your dumptype? What's the output of: amadmin DAILYSET disklist Did it list 'index yes' for all DLE? Jean-Louis Ingo Freund wrote: Hi, when I try to run amrecover and call it like: [EMAIL

Re: amrecover complains about missing index

On 22.10.2007 17:17, Jean-Louis Martineau wrote (please find the answer below the original text): Why /var/lib/amanda/DAILYSET/index does not exist? Do you generate index? What's the index setting on your dumptype? What's the output of: amadmin DAILYSET disklist Did it list 'index yes

Re: amrecover complains about missing index

Index are needed for amrecover, you must enabled them. Add 'index yes' to your dumptype. amrecover will only works your newer dump. Ingo Freund wrote: On 22.10.2007 17:17, Jean-Louis Martineau wrote (please find the answer below the original text): Why /var/lib/amanda/DAILYSET/index does

Problem creating some clients' index file

-- I added 2 new clients to a working amanda system. Both of these clients are Ubuntu Edgy machines running Amanda 2.5.2p1. The Amanda server(Amanda 2.5.2p1) is Ubuntu Fiesty 50+ clients of various OSes/versions of Amanda which work. The error reported on the edgy machines from running

Re: Problem creating some clients' index file

stan wrote: I added 2 new clients to a working amanda system. Both of these clients are Ubuntu Edgy machines running Amanda 2.5.2p1. The Amanda server(Amanda 2.5.2p1) is Ubuntu Fiesty 50+ clients of arious OSes/versions of Amanda which work. The error reported on the edgy machines from

Re: Problem creating some clients' index file

stan wrote: On Wed, Oct 03, 2007 at 11:00:57AM -0400, Jean-Louis Martineau wrote: stan wrote: I added 2 new clients to a working amanda system. Both of these clients are Ubuntu Edgy machines running Amanda 2.5.2p1. The Amanda server(Amanda 2.5.2p1) is Ubuntu Fiesty 50+ clients of

Re: Problem creating some clients' index file

On Wed, Oct 03, 2007 at 11:00:57AM -0400, Jean-Louis Martineau wrote: stan wrote: I added 2 new clients to a working amanda system. Both of these clients are Ubuntu Edgy machines running Amanda 2.5.2p1. The Amanda server(Amanda 2.5.2p1) is Ubuntu Fiesty 50+ clients of arious OSes/versions

Re: no index records

McGraw, Robert P wrote: Jean-Louis, Thanks for your reply. Sorry I did not indicate that I had the following in my tapelist. 20060701 071012 no-reuse 20060701 071011 no-reuse 20060701 071010 no-reuse 20060701 071009 no-reuse This is a grep of my log file. ##R##-zorn-[90] ## grep 0710

no index records

I am trying to manually merge some old amanda index data into my present date. When I run amrecover I get the following message. 200 Working date set to 2006-07-02. amrecover listdisk 200- List of disk for host zorn 201- /export/users-q 201- /export

Re: no index records

The tapelist file must list the label from the log.20060701.0 file. Jean-Louis McGraw, Robert P wrote: I am trying to manually merge some old amanda index data into my present date. When I run amrecover I get the following message. 200 Working date set to 2006-07-02

index tee cannot write [Broken pipe]

I have an amanda (2.5.1p3) server (solaris10) with seven amanda clients (2.4.4) and a new amanda (2.5.2) client on new hardware. I have been getting a index tee cannot write [Broken pipe] error message. I have looked at all the various aspects I can think of but still no joy. Could

Re: index tee cannot write [Broken pipe]

On 2007-08-02 15:56, Mike Gallant wrote: I have an amanda (2.5.1p3) server (solaris10) with seven amanda clients (2.4.4) and a new amanda (2.5.2) client on new hardware. I have been getting a index tee cannot write [Broken pipe] error message. I have looked at all the various aspects I can

Re: index tee cannot write [Broken pipe]

On Thu, Aug 02, 2007 at 09:56:12AM -0400, Mike Gallant wrote: I have an amanda (2.5.1p3) server (solaris10) with seven amanda clients (2.4.4) and a new amanda (2.5.2) client on new hardware. I have been getting a index tee cannot write [Broken pipe] error message. I have looked at all

Re: index tee cannot write [Broken pipe]

-0400, Mike Gallant wrote: I have an amanda (2.5.1p3) server (solaris10) with seven amanda clients (2.4.4) and a new amanda (2.5.2) client on new hardware. I have been getting a index tee cannot write [Broken pipe] error message. I have looked at all the various aspects I can think of but still

Dump error index tee cannot write

conf file /usr/local/etc/amanda/DailySet1/amanda-client.conf. sendbackup: debug 1 pid 30943 ruid 514 euid 514: rename at Fri May 4 14:59:15 2007 sendbackup req: GNUTAR /boot 0 1970:1:1:0:0:0 OPTIONS |;auth=bsd;compress-fast;index; parsed request as: program `GNUTAR' disk

sendbackup: index tee cannot write [Broken pipe]

still doesn't run properly - this time it's sendbackup that gets into trouble. The full sendbackup...debug from a failed dump is included below. Does anyone have any idea what may be causing this? What exactly is this index tee trying to write to (file, FIFO, socket...)? Is there anything extra

Re: sendbackup: index tee cannot write [Broken pipe]

access problems. Or at least, so I thought, but after sorting out these issues, I still get the same message. So I looked at the logs again and noticed the index tee cannot write, but maybe it's just a coincidence that this started occurring right now, and that the other message is caused

Re: Backup of index and config files

In my case the machine which works as an Amanda backup server itself is backed up by Amanda. So which are the important files/directories (index and config files/directories or any other important files) that I should save on some other machine, so that I can recover data from the Amanda

Re: (repost) 2.5.1: underscores in diskname and index files

can't seem to find any info on that post I made a while ago and if any provisions have been made to fix it in 2.5.1p3: The ChangeLog is not specific if this issue has been fixed: It's about diskname containing underscores '_' that under 2.4.x lead to the creation of index files

Backup of index and config files

Hi All, In my case the machine which works as an Amanda backup server itself is backed up by Amanda. So which are the important files/directories (index and config files/directories or any other important files) that I should save on some other machine, so that I can recover data from the Amanda

Re: Backup of index and config files

On Friday 02 March 2007, Yogesh Hasabnis wrote: Hi All, In my case the machine which works as an Amanda backup server itself is backed up by Amanda. So which are the important files/directories (index and config files/directories or any other important files) that I should save on some other

Re: (repost) 2.5.1: underscores in diskname and index files

2.4.x lead to the creation of index files with the '_' doubled, ie for a DLE like (say): I just upgraded my server to amanda 2.5.1p3. I have two DLEs whose labels include underscores, and both of them get the index dir doesn't exist --will create on next run error. For both

Re: (repost) 2.5.1: underscores in diskname and index files

a while ago and if any provisions have been made to fix it in 2.5.1p3: The ChangeLog is not specific if this issue has been fixed: It's about diskname containing underscores '_' that under 2.4.x lead to the creation of index files with the '_' doubled, ie for a DLE like (say

(repost) 2.5.1: underscores in diskname and index files

Hi, I can't seem to find any info on that post I made a while ago and if any provisions have been made to fix it in 2.5.1p3: The ChangeLog is not specific if this issue has been fixed: It's about diskname containing underscores '_' that under 2.4.x lead to the creation of index files

Re: (repost) 2.5.1: underscores in diskname and index files

it in 2.5.1p3: The ChangeLog is not specific if this issue has been fixed: It's about diskname containing underscores '_' that under 2.4.x lead to the creation of index files with the '_' doubled, ie for a DLE like (say): myhost home_user /home/user { tar-me-please } the index files would be stuffed

Re: amrecover doesn't see all the index entries?

directory :) so I started an amrecover session (2.5.1p2, client is the server, irix-6.5) using the last full backup of the DLE (backed up with xfsdump). This DLE while not that big (~70GB) has a lot of small files (the uncompressed index file for the full shows ~1M entries). After a few hours

Re: amrecover doesn't see all the index entries?

On Tuesday 30 January 2007 09:46, Jean-Francois Malouin wrote: * Gene Heskett [EMAIL PROTECTED] [20070130 01:59]: [...] I think my first question might be what version of tar are you using? Hi Gene, The DLE is backed up with xfsdump (irix-6.5.x) jf Which I have no knowledge of, so I'll

Re: amrecover doesn't see all the index entries?

while not that big (~70GB) has a lot of small files (the uncompressed index file for the full shows ~1M entries). After a few hours waiting for the prompt back from amrecover after doing the setdisk I aborted the session, started a screen session and did the whole thing again, and left work

Re: amrecover doesn't see all the index entries?

is the server, irix-6.5) using the last full backup of the DLE (backed up with xfsdump). This DLE while not that big (~70GB) has a lot of small files (the uncompressed index file for the full shows ~1M entries). After a few hours waiting for the prompt back from amrecover after doing the setdisk

Re: amrecover doesn't see all the index entries?

(backed up with xfsdump). This DLE while not that big (~70GB) has a lot of small files (the uncompressed index file for the full shows ~1M entries). After a few hours waiting for the prompt back from amrecover after doing the setdisk I aborted the session, started a screen session and did

amrecover doesn't see all the index entries?

Hi, Last Friday a user managed to remove her entire home directory :) so I started an amrecover session (2.5.1p2, client is the server, irix-6.5) using the last full backup of the DLE (backed up with xfsdump). This DLE while not that big (~70GB) has a lot of small files (the uncompressed index

Re: index tee cannot write problem with 2.5.1

: time 50.042: index tee cannot write [Broken pipe] sendbackup: time 50.042: pid 5989 finish time Tue Sep 5 20:01:43 2006 I believe the index tee cannot write is just a secondary problem. Because the serverside of amanda had problems, it closed down the data, message and the index channel

Re: index tee cannot write problem with 2.5.1

Jean-Louis Martineau [EMAIL PROTECTED] wrote to me yesterday: Could you try to increase ACK_TRIES in common-src/protocol.c ? The relevant code segment is: #define ACK_WAIT 10 /* time (secs) to wait for ACK - keep short */ #define ACK_TRIES 3 /* num retries after ACK_WAIT timeout */ I screwed

index tee cannot write problem with 2.5.1

read header: got 0 instead of 32768] ambiance.med.utah.edu / lev 0 FAILED [too many dumper retry: [request failed: timeout waiting for ACK]] the sendbackup debug files on the client all say: sendbackup: time 0.054: started backup sendbackup: time 50.042: index tee cannot write

does amflush updates index?

, in the indexdir specified in amanda.conf i have more than one index file and amrecover make the index with the non latest index file and some new directories and files don't backup in my system. The amflush man page says that "Amflush writes Amanda backups from the holding disks to tape, and updates the A

Re: does amflush updates index?

. And finally i have executed amrecover but, and that's my problem, in the indexdir specified in amanda.conf i have more than one index file and amrecover make the index with the non latest index file and some new directories and files don't backup in my system. The amflush man page says

Re: Re: Cyrillic support for index files

От: Копия:(СК: Евгений Ю Сосунов/Sibancor) owner-amanda-usersТема: Re: Cyrillic support for index files

Cyrillic support for index files

' ' --sharedstatedir=/usr/com' '--mandir=/usr/share/man' ' --infodir=/usr/share/info' '--without-included-gettext' '--enable-shared' ' --with-index-server=localhost' '--with-gnutar=/bin/tar' ' --with-gnutar-listdir=/var/lib/amanda/gnutar-lists' ' --with-smbclient=/usr/bin/smbclient' '--with-db=text

Re: Cyrillic support for index files

On Fri, Jun 09, 2006 at 02:22:38PM +0700, å×ÇÅÎÉÊ à óÏÓÕÎÏ× wrote: Good day! Sorry for my English. I have installed and configured amanda. ... After that I modify ENVIRONMENT Variable LANG in crontab of amanda user. But amdump which create index files still not working correctly

Re: Could not open index directory bla

On Mon, Apr 17, 2006 at 01:34:53PM +0900, David Leangen wrote: The index would not be created unless a backup had succeeded. Have you ever succeeded in backing up this DLE? If not, the problem is likely elsewhere. No, since I have updated to 2.5.0, I have not. But this is the only

Could not open index directory bla

I'm still not able to backup one of my local networked hosts. The only problem I can find in the logs is this: could not open index directory /usr/adm/amanda/daily/index/host/_home/ Could this be a cause of my problems? I am running the process from my backup server like so: $root: sudo -u

Re: Could not open index directory bla

On Mon, Apr 17, 2006 at 12:46:15PM +0900, David Leangen wrote: I'm still not able to backup one of my local networked hosts. The only problem I can find in the logs is this: could not open index directory /usr/adm/amanda/daily/index/host/_home/ Could this be a cause of my problems

Re: Could not open index directory bla

The index would not be created unless a backup had succeeded. Have you ever succeeded in backing up this DLE? If not, the problem is likely elsewhere. No, since I have updated to 2.5.0, I have not. But this is the only error or warning message that I could find. Any ideas where I could

Re: amrecover index empty

http://amanda.sourceforge.net/fom-serve/cache/24.html and I am not in any cases mentioned index yes is set, amrecover is call with -C , and I use Gnu tar tar-1.14-4 on my fedora core 3 backup systeme ( kernel 2.6.10-1.770_FC3 amanda-server-2.4.4p3-4) tar 1.14 is not a good version of tar to use. See

Re: amrecover index empty

and I am not in any cases mentioned index yes is set, amrecover is call with -C , and I use Gnu tar tar-1.14-4 on my fedora core 3 backup systeme ( kernel 2.6.10-1.770_FC3 amanda-server-2.4.4p3-4) tar 1.14 is not a good version of tar to use. See http://www.amanda.org/docs/faq.html

Re: amrecover index empty

, the restore owner modes on . [Y,n] might have been answered Yes :-( ! so just resetting chmod 1777 on /tmp on the clients systems which had lost their indexes corrected the problem. Apperently the dump is forking the dump to the amanda server and to a local pipe which finally does a started index creator

Re: amrecover index empty

have been answered Yes :-( ! so just resetting chmod 1777 on /tmp on the clients systems which had lost their indexes corrected the problem. Apperently the dump is forking the dump to the amanda server and to a local pipe which finally does a started index creator: /sbin/restore -tvf - 21

Re: amrecover index empty

the dump is forking the dump to the amanda server and to a local pipe which finally does a started index creator: /sbin/restore -tvf - 21 | sed -e '... and this restore is done on the local /tmp ! if tmp is not writable, here's the problem I had . Thanks a lot for your help .

Re: amrecover index empty

cases mentioned index yes is set, amrecover is call with -C , and I use Gnu tar tar-1.14-4 on my fedora core 3 backup systeme ( kernel 2.6.10-1.770_FC3 amanda-server-2.4.4p3-4) tar 1.14 is not a good version of tar to use. See http://www.amanda.org/docs/faq.html#id2554919 Matt -- Matt

Re: amrecover index empty

cases mentioned index yes is set, amrecover is call with -C , and I use Gnu tar tar-1.14-4 on my fedora core 3 backup systeme ( kernel 2.6.10-1.770_FC3 amanda-server-2.4.4p3-4) Index file are present but empty ! [EMAIL PROTECTED] /var/lib/amanda/int/index/cobra3/_p2v5f1] ... -rw--- 1

Re: Index files not being created

planner hostname / START planner date 20050913 WARNING planner tapecycle (3) = runspercycle (10) ^^ May not have anything to do with your index problem, but you will take care of this, right? Otherwise you will be overwriting your only level 0 before

Re: Index files not being created

Some of your comments confuse me. On Fri, Sep 16, 2005 at 07:39:18PM +1200, Cameron Beattie wrote: I believe this problem is resolved thanks to some help from the list. See my inline comments for the resolution. ... The warning is no longer present in the log and the index seems

Re: Index files not being created

Some of your comments confuse me. On Fri, Sep 16, 2005 at 07:39:18PM +1200, Cameron Beattie wrote: I believe this problem is resolved thanks to some help from the list. See my inline comments for the resolution. ... The warning is no longer present in the log and the index seems

Re: Index files not being created

Cameron Beattie wrote: I am having trouble getting amanda to create index files. I have set index to yes in the dumptype. I don't believe there is a permissions problem: ls -laF /var/lib/amanda/normal/index/hostname drwxr-sr-x 2 amanda disk 4096 Sep 13 16:56 _/ drwxr-sr-x 4 amanda disk

Re: Index files not being created

On Tue, Sep 13, 2005 at 05:40:50PM +1200, Cameron Beattie wrote: I am having trouble getting amanda to create index files. I have set index to yes in the dumptype. I don't believe there is a permissions problem: ls -laF /var/lib/amanda/normal/index/hostname drwxr-sr-x 2 amanda disk 4096 Sep

Index files not being created

I am having trouble getting amanda to create index files. I have set index to yes in the dumptype. I don't believe there is a permissions problem: ls -laF /var/lib/amanda/normal/index/hostname drwxr-sr-x 2 amanda disk 4096 Sep 13 16:56 _/ drwxr-sr-x 4 amanda disk 4096 Sep 13 16:47 ./ drwxr-xr

Re: problems with index creation

Le samedi 02 juillet 2005 à 13:31 -0400, Jon LaBadie a écrit : On Sat, Jul 02, 2005 at 06:17:11PM +0200, Eric DOUTRELEAU wrote: Hi with changing index to index yes it didn't solved my problem. and the output if the commands give me the same output. the only thing that i can see

Re: problems with index creation

On Tuesday 05 July 2005 05:15, Eric Doutreleau wrote: [...] On Fri, Jul 01, 2005 at 05:36:18PM +0200, ERic Doutreleau wrote: Indeed i have index yes for almost type except some that are realted to my problems. i will test that that night thanks for your answer

Re: problems with index creation

Hi with changing index to index yes it didn't solved my problem. and the output if the commands give me the same output. the only thing that i can see about the hosts that failed is that they a lot of partition to backup. one has 20 and the othr 36 Selon Jon LaBadie [EMAIL PROTECTED

Re: problems with index creation

On Sat, Jul 02, 2005 at 06:17:11PM +0200, Eric DOUTRELEAU wrote: Hi with changing index to index yes it didn't solved my problem. and the output if the commands give me the same output. the only thing that i can see about the hosts that failed is that they a lot of partition to backup

problems with index creation

i have a problem with index creation. i have out the word index on my dumptype but the index created are always empty. here is some debug on the client the sendbackup. we can see in it that the index is created succesfully. more sendbackup.20050630231107.debug sendbackup: debug 1 pid 13721

Re: problems with index creation

On Fri, Jul 01, 2005 at 11:48:38AM +0200, Eric Doutreleau wrote: i have a problem with index creation. i have out the word index on my dumptype but the index created are always empty. Just to confirm, do you have just the word index, or is it index yes? Should be the latter. -- Jon H

Re: problems with index creation

Indeed i have index yes for almost type except some that are realted to my problems. i will test that that night thanks for your answer Le vendredi 01 juillet 2005 à 07:25 -0400, Jon LaBadie a écrit : On Fri, Jul 01, 2005 at 11:48:38AM +0200, Eric Doutreleau wrote: i have a problem

Re: problems with index creation

On Fri, Jul 01, 2005 at 05:36:18PM +0200, ERic Doutreleau wrote: Indeed i have index yes for almost type except some that are realted to my problems. i will test that that night thanks for your answer Le vendredi 01 juillet 2005 à 07:25 -0400, Jon LaBadie a écrit : On Fri, Jul 01

amrecover: no index records for host

I added 'index yes' in the dumptype Comp-root-tar. I ran amdump using that dumptype with no error reporting. When I use amrecover C myconfig name, I still got the same errorno index records for host. amandaidx service is enabled in xinetd. Please help. Thank you, lei

Re: Amrecover: No index records for disk for specified date: Done

figured that since the tape was old, that the index record has been rotated or removed. I check /var/lib/amanda/xes/index/brimstone/sdb1 and noticed that the index file does index exist for that date. Was that a level 0? I wonder if a level is needed for amrecover to work - I don't know

Amrecover: No index records for disk for specified date

on that date due to stability issues. However, I need to restore a tar'd file from this tape off that host. I run amrecover -C xes setdate 2005-02-25 sethost brimstone setdisk sdb1 and this message pops up: No index records for disk for specified date If date correct, notify system administrator

Re: Amrecover: No index records for disk for specified date

On Wed, 27 Apr 2005 at 11:46am, Tanniel Simonian wrote If it is not possible to use amrecover at this point, someone one to point me on how to restore a file from tape that has a combination of zipped tar's and dumps. This bit is easy. The instructions are in docs/RESTORE in the tarball. --

Re: Amrecover: No index records for disk for specified date

that tape? Is that a different archive config? Or did you just pull it out of rotation? Possibly replacing it with another of the same label so amanda thinks it might have been overwritten? At first I figured that since the tape was old, that the index record has been rotated or removed. I check /var

  1   2   3   4   5   >