Re: Autoflush not working in 2.5.2
Steven Can you post: amflush.1 or amflush.2 log file, the one with the error amflush.datestamp.debug file with the error. Jean-Louis Steven Backus wrote: My solaris machine seems to have backed up fine last night, however, none of my holding disks were drained. I do nightly backups to the holding disk Monday - Thursday then put in the tape on Friday, autoflush used to take care of the rest, not so last night. So this morning I run amflush config and select ALL for the directories I want to flush. As in the man page, I expect: Are you sure you want to do this? yes Running in background, you can log off now. You'll get mail when amflush is finished. But that never comes up, eventually I log off and amflush dies, now when I try to use it I get: Scanning /home1/dumps/amanda... 20070428150002: found Amanda directory. 20070430190001: found Amanda directory. 20070501190001: found Amanda directory. 20070502190001: found Amanda directory. 20070503190001: found Amanda directory. Scanning /home2/dumps/amanda... 20070428150002: found Amanda directory. 20070430190001: found Amanda directory. 20070501190001: found Amanda directory. 20070502190001: found Amanda directory. 20070503190001: found Amanda directory. Multiple Amanda directories, please pick one by letter: A. 20070428150002 B. 20070430190001 C. 20070501190001 D. 20070502190001 E. 20070503190001 Select directories to flush [A..E]: [ALL] Could not find any valid dump image, check directory. How can I flush these? Steve
Re: Amrecovery?
On 2007-05-07 02:47, Donofrio, Lewis wrote: Folks, In amanda 2.5.x do we stil have to do the amrecover trick documented in the 'how to use amanda witht the file-driver - chapter13', pg 107 (13.4) when it states load tape b3_14 not continue [?/Y/n/s/t]? Then on a 'second terminal run: amtape woo slot 14. Amtape returns amtape: label b3_14 is not loaded. Then switch back to first amrecover tty. This was noted as a 'trick' for vtapes recovery from 2.4.4p3 so I'm guessing this is fixed/automatted now? Yes use the amanda.conf parameter: amrecover_changer changer And use that string changer as the name of the tapedevice. http://wiki.zmanda.com/index.php/File_driver#Recovery -- 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: amstatus returns uninitialized value!
Can you post the amdump.X log file that show this error in amstatus. Jean-Louis FL wrote: I'm using amanda version 2.5.1p3 amstatus Daily works for a while, then returns the following: MP line 3238. Use of uninitialized value in hash element at /usr/sbin/amstatus line 681, AMDUMP line 3238. Use of uninitialized value in hash element at /usr/sbin/amstatus line 685, AMDUMP line 3238. Use of uninitialized value in hash element at /usr/sbin/amstatus line 691, AMDUMP line 3238. Use of uninitialized value in hash element at /usr/sbin/amstatus line 534, AMDUMP line 3391. Use of uninitialized value in hash element at /usr/sbin/amstatus line 535, AMDUMP line 3391. Use of uninitialized value in hash element at /usr/sbin/amstatus line 536, AMDUMP line 3391. Use of uninitialized value in hash element at /usr/sbin/amstatus line 538, AMDUMP line 3391. Use of uninitialized value in hash element at /usr/sbin/amstatus line 539, AMDUMP line 3391. Use of uninitialized value in hash element at /usr/sbin/amstatus line 545, AMDUMP line 3391. Modification of non-creatable array value attempted, subscript -3 at /usr/sbin/amstatus line 751, AMDUMP line 3394. [EMAIL PROTECTED]:/home/amanda$ mailto:[EMAIL PROTECTED]:/home/amanda$ Could this be due to an error in a configuration file?
2.5.2 compilation failure on irix-6.5.x
First go at amanda-2.5.2 on a system running irix-6.5.x and compile fails with the error: cc-1040 cc: ERROR File = amanda.h, Line = 623 An identifier is expected. #define vstrallocf(...) debug_vstrallocf(__FILE__,__LINE__,__VA_ARGS__) ^ cc-1204 cc: WARNING File = amanda.h, Line = 957 The indicated declaration is not visible outside of the function. extern int check_security(struct sockaddr_storage *, char *, unsigned long, char **); ^ 1 error detected in the compilation of alloc.c. make[1]: *** [alloc.lo] Error 1 make[1]: Leaving directory `/stuff/amanda-source/amanda-2.5.2/common-src' make: *** [all-recursive] Error 1 jf -- °
question on splitsize
On another system with a smaller tape drive (limited to about 4-5 GB), I have been using the new capability in 2.5.x for manual tape changers and spanning tapes to more than one tape per backup. This has been working great and as expected except for the split size. Within my dumptype statement, I have the following specifications: tape_splitsize 410 mbytes fallback_splitsize 100 mbytes However, the size of the split archives that are getting written to the holding disk are approximately 1 GB in size instead of the size shown above. What can be done to correct this ? Am I interpreting this parameter incorrectly ? James D. Freels, Ph.D. Oak Ridge National Laboratory [EMAIL PROTECTED] Computational tools are important, but there is no substitute for understanding. -Will Zimmerman, 05/01/2007
Re: 2.5.2 compilation failure on irix-6.5.x
This is the same error as in
http://groups.yahoo.com/group/amanda-hackers/message/5401
the same patch is attached here -- could you let us know if it fixes the
compile?
Dustin
On Mon, May 07, 2007 at 12:05:44PM -0400, Jean-Francois Malouin wrote:
First go at amanda-2.5.2 on a system running irix-6.5.x
and compile fails with the error:
cc-1040 cc: ERROR File = amanda.h, Line = 623
An identifier is expected.
#define vstrallocf(...)
debug_vstrallocf(__FILE__,__LINE__,__VA_ARGS__)
^
cc-1204 cc: WARNING File = amanda.h, Line = 957
The indicated declaration is not visible outside of the function.
extern int check_security(struct sockaddr_storage *, char *,
unsigned long, char **);
^
1 error detected in the compilation of alloc.c.
make[1]: *** [alloc.lo] Error 1
make[1]: Leaving directory
`/stuff/amanda-source/amanda-2.5.2/common-src'
make: *** [all-recursive] Error 1
jf
--
?
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
diff -u -r --show-c-function --new-file
--exclude-from=/home/martinea/src.orig/amanda.diff
--ignore-matching-lines='$Id:' amanda-2.5.2/common-src/amanda.h
amanda-2.5.2.sockaddr_storage/common-src/amanda.h
--- amanda-2.5.2/common-src/amanda.h2007-04-10 06:56:00.0 -0400
+++ amanda-2.5.2.sockaddr_storage/common-src/amanda.h 2007-05-04
16:40:18.0 -0400
@@ -268,6 +268,9 @@ struct iovec {
#include arpa/inet.h
#endif
+#define sockaddr_storage sockaddr_in
+#define ss_family sin_family
+
/* Calculate the length of the data in a struct sockaddr_storage.
* THIS IS A HACK.
*
Re: amstatus returns uninitialized value!
On 5/7/07, Jean-Louis Martineau [EMAIL PROTECTED] wrote: Can you post the amdump.X log file that show this error in amstatus. Jean-Louis I don't see the error in amdump.1, only the command amstatus Daily shows this error. But here are the last 40 lines of /var/log/amanda/Daily/amdump.1 sh-3.1# tail -n 40 amdump.1 driver: FINISHED time 5506.906 amdump: end at Sun May 6 17:35:15 EDT 2007 line 111 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/My Data Sources 20070506160328 0 [sec 0 nkb 62 ckb 64 kps 1024] Scan failed at: Data Sources 20070506160328 0 [sec 0 nkb 62 ckb 64 kps 1024] line 115 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/Email from Outlook 20070506160328 0 [sec 0 nkb 102 ckb 64 kps 1024] Scan failed at: from Outlook 20070506160328 0 [sec 0 nkb 102 ckb 64 kps 1024] line 123 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/My Music 20070506160328 0 [sec 0 nkb 42 ckb 64 kps 1024] Scan failed at: Music 20070506160328 0 [sec 0 nkb 42 ckb 64 kps 1024] line 139 of log is bogus: estimate wilf /home/IOMEGANAS/System Volume Information 20070506160328 0 [sec 0 nkb 42 ckb 64 kps 1024] Scan failed at: Information 20070506160328 0 [sec 0 nkb 42 ckb 64 kps 1024] line 171 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/My Albums 20070506160328 0 [sec 0 nkb 4452 ckb 1024 kps 1024] Scan failed at: Albums 20070506160328 0 [sec 0 nkb 4452 ckb 1024 kps 1024] line 183 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/My PaperPort Documents 20070506160328 0 [sec 2 nkb 16362 ckb 12928 kps 6442] Scan failed at: PaperPort Documents 20070506160328 0 [sec 2 nkb 16362 ckb 12928 kps 6442] line 187 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/Miscellaneous Photos and Papers 20070506160328 0 [sec 4 nkb 32772 ckb 32032 kps 7548] Scan failed at: Photos and Papers 20070506160328 0 [sec 4 nkb 32772 ckb 32032 kps 7548] line 207 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/My Pictures 20070506160328 0 [sec 24 nkb 178562 ckb 176672 kps 7066] Scan failed at: Pictures 20070506160328 0 [sec 24 nkb 178562 ckb 176672 kps 7066] line 219 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/Hemtech SW 20070506160328 0 [sec 36 nkb 298762 ckb 258560 kps 6997] Scan failed at: SW 20070506160328 0 [sec 36 nkb 298762 ckb 258560 kps 6997] line 223 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/McCarthy Family Photos 20070506160328 0 [sec 52 nkb 381572 ckb 358912 kps 6836] Scan failed at: Family Photos 20070506160328 0 [sec 52 nkb 381572 ckb 358912 kps 6836] line 231 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/Suzanne's Personal Letters 20070506160328 0 [sec 102 nkb 500902 ckb 494176 kps 4814] Scan failed at: Personal Letters 20070506160328 0 [sec 102 nkb 500902 ckb 494176 kps 4814] line 235 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/McCarthy Family CD 20070506160328 0 [sec 83 nkb 583962 ckb 575424 kps 6881] Scan failed at: Family CD 20070506160328 0 [sec 83 nkb 583962 ckb 575424 kps 6881] line 243 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/Iomega 3 20070506160328 0 [sec 169 nkb 1399552 ckb 1002784 kps 5913] Scan failed at: 20070506160328 0 [sec 169 nkb 1399552 ckb 1002784 kps 5913] line 274 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/Iomega 1 20070506160328 1 [sec 26244 nkb 63713912 ckb 26498144 kps 1010] Scan failed at: 20070506160328 1 [sec 26244 nkb 63713912 ckb 26498144 kps 1010] line 279 of log is bogus: estimate wilf /home/IOMEGANAS/Shared Data/Iomega 2 20070506160328 1 [sec 95733 nkb 50800142 ckb 37340832 kps 390] Scan failed at: 20070506160328 1 [sec 95733 nkb 50800142 ckb 37340832 kps 390] Scanning /home/amanda... 0 0 0 0 0 0 0 sh-3.1# FL wrote: I'm using amanda version 2.5.1p3 amstatus Daily works for a while, then returns the following: MP line 3238. Use of uninitialized value in hash element at /usr/sbin/amstatus line 681, AMDUMP line 3238. Use of uninitialized value in hash element at /usr/sbin/amstatus line 685, AMDUMP line 3238. Use of uninitialized value in hash element at /usr/sbin/amstatus line 691, AMDUMP line 3238. Use of uninitialized value in hash element at /usr/sbin/amstatus line 534, AMDUMP line 3391. Use of uninitialized value in hash element at /usr/sbin/amstatus line 535, AMDUMP line 3391. Use of uninitialized value in hash element at /usr/sbin/amstatus line 536, AMDUMP line 3391. Use of uninitialized value in hash element at /usr/sbin/amstatus line 538, AMDUMP line 3391. Use of uninitialized value in hash element at /usr/sbin/amstatus line 539, AMDUMP line 3391. Use of uninitialized value in hash element at /usr/sbin/amstatus line 545, AMDUMP line 3391. Modification of non-creatable array value attempted, subscript -3 at /usr/sbin/amstatus line 751, AMDUMP line 3394. [EMAIL PROTECTED]:/home/amanda$ mailto: [EMAIL PROTECTED]:/home/amanda$ Could this be due to an error in a configuration file?
Re: 2.5.2 compilation failure on irix-6.5.x
* Pieter Bowman [EMAIL PROTECTED] [20070507 13:27]:
...
First go at amanda-2.5.2 on a system running irix-6.5.x
and compile fails with the error:
...
This is the case on both IRIX and OSF/1. These compilers can't
handle:
#define vstrallocf(...)
debug_vstrallocf(__FILE__,__LINE__,__VA_ARGS__)
The patch for sockaddr_storage seems to work with the addition of
these two definitions in amanda.h:
/* Needed on SGI IRIX 6.5 */
#ifdef WORKING_IPV6
#define INET6
#endif
#ifndef INET_ADDRSTRLEN
#define INET_ADDRSTRLEN 16
#endif
Pieter
Thanks Jean-Louis and Pieter but still no go:
Making all in gnulib
make[1]: Entering directory `/stuff/amanda-source/amanda-2.5.2/gnulib'
rm -f stdbool.h-t stdbool.h
{ echo '/* DO NOT EDIT! GENERATED AUTOMATICALLY! */'; \
sed -e 's/@''HAVE__BOOL''@/0/g' ./stdbool_.h; \
} stdbool.h-t
mv stdbool.h-t stdbool.h
rm -f string.h-t string.h
{ echo '/* DO NOT EDIT! GENERATED AUTOMATICALLY! */' \
sed -e 's|@''ABSOLUTE_STRING_H''@|///usr/include/string.h|g' \
-e 's|@''HAVE_DECL_MEMMEM''@|1|g' \
-e 's|@''HAVE_MEMPCPY''@|1|g' \
-e 's|@''HAVE_DECL_MEMRCHR''@|1|g' \
-e 's|@''HAVE_STPCPY''@|1|g' \
-e 's|@''HAVE_STPNCPY''@|1|g' \
-e 's|@''HAVE_DECL_STRNCASECMP''@|1|g' \
-e 's|@''HAVE_STRCHRNUL''@|1|g' \
-e 's|@''HAVE_DECL_STRDUP''@|1|g' \
-e 's|@''HAVE_STRNDUP''@|1|g' \
-e 's|@''HAVE_DECL_STRNDUP''@|1|g' \
-e 's|@''HAVE_DECL_STRNLEN''@|1|g' \
-e 's|@''HAVE_STRPBRK''@|1|g' \
-e 's|@''HAVE_STRSEP''@|1|g' \
-e 's|@''HAVE_DECL_STRTOK_R''@|1|g' \
-e 's|@''REPLACE_STRCASECMP''@|0|g' \
-e 's|@''REPLACE_STRSTR''@|0|g' \
-e 's|@''REPLACE_STRCASESTR''@|0|g' \
./string_.h; \
} string.h-t
mv string.h-t string.h
/usr/local/bin/make all-am
make[2]: Entering directory `/stuff/amanda-source/amanda-2.5.2/gnulib'
source='lock.c' object='lock.lo' libtool=yes \
DEPDIR=.deps depmode=sgi /bin/sh ../config/depcomp \
/bin/sh ../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I.
-I../config -I/usr/freeware/include -D_GNU_SOURCE -c -o lock.lo
lock.c
mkdir .libs
cc -DHAVE_CONFIG_H -I. -I. -I../config -I/usr/freeware/include -D_GNU_SOURCE
-c lock.c -Wp,-MDupdate,.deps/lock.TPlo -DPIC -o .libs/lock.o
cc -DHAVE_CONFIG_H -I. -I. -I../config -I/usr/freeware/include -D_GNU_SOURCE
-c lock.c -Wp,-MDupdate,.deps/lock.TPlo -o lock.o /dev/null 21
source='asnprintf.c' object='asnprintf.lo' libtool=yes \
DEPDIR=.deps depmode=sgi /bin/sh ../config/depcomp \
/bin/sh ../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I.
-I../config -I/usr/freeware/include -D_GNU_SOURCE -c -o asnprintf.lo
asnprintf.c
cc -DHAVE_CONFIG_H -I. -I. -I../config -I/usr/freeware/include -D_GNU_SOURCE
-c asnprintf.c -Wp,-MDupdate,.deps/asnprintf.TPlo -DPIC -o .libs/asnprintf.o
cc -DHAVE_CONFIG_H -I. -I. -I../config -I/usr/freeware/include -D_GNU_SOURCE
-c asnprintf.c -Wp,-MDupdate,.deps/asnprintf.TPlo -o asnprintf.o /dev/null 21
source='gai_strerror.c' object='gai_strerror.lo' libtool=yes \
DEPDIR=.deps depmode=sgi /bin/sh ../config/depcomp \
/bin/sh ../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I.
-I../config -I/usr/freeware/include -D_GNU_SOURCE -c -o
gai_strerror.lo gai_strerror.c
cc -DHAVE_CONFIG_H -I. -I. -I../config -I/usr/freeware/include -D_GNU_SOURCE
-c gai_strerror.c -Wp,-MDupdate,.deps/gai_strerror.TPlo -DPIC -o
.libs/gai_strerror.o
cc-1084 cc: ERROR File = /usr/include/sys/socket.h, Line = 66
The indicated declaration has an invalid combination of type specifiers.
typedef int socklen_t;
^
cc-1101 cc: ERROR File = getaddrinfo.h, Line = 37
addrinfo has already been declared in the current scope.
struct addrinfo
^
cc-1143 cc: ERROR File = getaddrinfo.h, Line = 116
Declaration is incompatible with int getaddrinfo(const char *, const char *,
const struct addrinfo *, struct addrinfo **) (declared at line 148
of /usr/include/netdb.h).
extern int getaddrinfo (const char *restrict nodename,
^
cc-1143 cc: ERROR File = getaddrinfo.h, Line = 126
Declaration is incompatible with void freeaddrinfo(struct addrinfo *)
(declared at line 146 of /usr/include/netdb.h).
extern void freeaddrinfo (struct addrinfo *ai);
^
cc-1143 cc: ERROR File = getaddrinfo.h, Line = 140
Declaration is incompatible with int getnameinfo(const struct sockaddr *,
int, char *, int, char *, int, unsigned int) (declared at line 144
of /usr/include/netdb.h).
extern int getnameinfo(const struct sockaddr *restrict sa, socklen_t salen,
^
5 errors detected in the compilation of gai_strerror.c.
make[2]: *** [gai_strerror.lo] Error 1
make[2]: Leaving directory `/stuff/amanda-source/amanda-2.5.2/gnulib'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/stuff/amanda-source/amanda-2.5.2/gnulib'
make: *** [all-recursive
Re: 2.5.2 compilation failure on irix-6.5.x
... First go at amanda-2.5.2 on a system running irix-6.5.x and compile fails with the error: ... This is the case on both IRIX and OSF/1. These compilers can't handle: #define vstrallocf(...) debug_vstrallocf(__FILE__,__LINE__,__VA_ARGS__) The patch for sockaddr_storage seems to work with the addition of these two definitions in amanda.h: /* Needed on SGI IRIX 6.5 */ #ifdef WORKING_IPV6 #define INET6 #endif #ifndef INET_ADDRSTRLEN #define INET_ADDRSTRLEN 16 #endif Pieter
amanda upgrade questions
I understand that amanda 2.5 is compatible with amanda 2.4 clients. This means I could upgrade my server and do the clients later ? I would like to upgrade to 2.5.2 for security reason (ability to encrypt backups, ssh) I compiled my server and client with restriction on the tcp and udp ports used for ease of firewall configuration: --with-tcpportrange=5,50100' '--with-udpportrange=850,859 Do these options still apply to the new amanda version ? Will the new version be able to restore old tapes that were written by the amanda 2.4 tapeserver ? Will amrecover on a 2.4 client be able to use the 2.5 amanda server ? Are the new encryption and ssh features easy to use ? Thanks !
amverify - reality check?
Folks, I've been tasked with guaranteeing that the backup vtapes or in the future real tapes are good. So I found the command amverify that seems to be the correct routine but I want to know does it completely check the archive and the files contained within? __ Lewis [EMAIL PROTECTED] Cell: (734) 323-8776
Re: 2.5.2 compilation failure on irix-6.5.x
Pieter, Jean-Francois,
Can you try the attached patch for the vstrallocf problem.
Jean-Louis
Pieter Bowman wrote:
...
First go at amanda-2.5.2 on a system running irix-6.5.x
and compile fails with the error:
...
This is the case on both IRIX and OSF/1. These compilers can't
handle:
#define vstrallocf(...) debug_vstrallocf(__FILE__,__LINE__,__VA_ARGS__)
The patch for sockaddr_storage seems to work with the addition of
these two definitions in amanda.h:
/* Needed on SGI IRIX 6.5 */
#ifdef WORKING_IPV6
#define INET6
#endif
#ifndef INET_ADDRSTRLEN
#define INET_ADDRSTRLEN 16
#endif
Pieter
diff -u -r --show-c-function --new-file --exclude-from=/home/martinea/src.orig/amanda.diff --ignore-matching-lines='$Id:' amanda-2.5.2/common-src/alloc.c amanda-2.5.2.vstralloc/common-src/alloc.c
--- amanda-2.5.2/common-src/alloc.c 2007-05-04 07:39:08.0 -0400
+++ amanda-2.5.2.vstrallocf/common-src/alloc.c 2007-05-07 14:27:57.0 -0400
@@ -389,8 +389,6 @@ arglist_function1(
*/
char *
debug_vstrallocf(
-const char *file,
-int line,
const char *fmt,
...)
{
@@ -398,9 +396,10 @@ debug_vstrallocf(
size_t size;
va_list argp;
-malloc_enter(debug_caller_loc(file, line));
+debug_alloc_pop();
+malloc_enter(debug_caller_loc(saved_file, saved_line));
-result = debug_alloc(file, line, MIN_ALLOC);
+result = debug_alloc(saved_file, saved_line, MIN_ALLOC);
if (result != NULL) {
arglist_start(argp, fmt);
@@ -409,7 +408,7 @@ debug_vstrallocf(
if (size = (size_t)MIN_ALLOC) {
amfree(result);
- result = debug_alloc(file, line, size + 1);
+ result = debug_alloc(saved_file, saved_line, size + 1);
arglist_start(argp, fmt);
(void)vsnprintf(result, size + 1, fmt, argp);
@@ -417,7 +416,7 @@ debug_vstrallocf(
}
}
-malloc_leave(debug_caller_loc(file, line));
+malloc_leave(debug_caller_loc(saved_file, saved_line));
return result;
}
diff -u -r --show-c-function --new-file --exclude-from=/home/martinea/src.orig/amanda.diff --ignore-matching-lines='$Id:' amanda-2.5.2/common-src/amanda.h amanda-2.5.2.vstralloc/common-src/amanda.h
--- amanda-2.5.2/common-src/amanda.h 2007-05-04 07:39:08.0 -0400
+++ amanda-2.5.2.vstrallocf/common-src/amanda.h 2007-05-07 14:22:45.0 -0400
@@ -577,8 +577,6 @@ extern void *debug_newalloc (const cha
extern char *debug_stralloc (const char *c, int l, const char *str);
extern char *debug_newstralloc(const char *c, int l, char *oldstr,
const char *newstr);
-extern char *debug_vstrallocf(const char *file, int line, const char *fmt,
- ...) __attribute__ ((format (printf, 3, 4)));
extern const char *debug_caller_loc (const char *file, int line);
extern int debug_alloc_push (char *file, int line);
extern void debug_alloc_pop (void);
@@ -620,10 +618,12 @@ extern void debug_alloc_pop (void);
#define vstralloc debug_alloc_push(__FILE__,__LINE__)?0:debug_vstralloc
#define newvstralloc debug_alloc_push(__FILE__,__LINE__)?0:debug_newvstralloc
-#define vstrallocf(...) debug_vstrallocf(__FILE__,__LINE__,__VA_ARGS__)
+#define vstrallocf debug_alloc_push(__FILE__,__LINE__)?0:debug_vstrallocf
extern char *debug_vstralloc(const char *str, ...);
extern char *debug_newvstralloc(char *oldstr, const char *newstr, ...);
+extern char *debug_vstrallocf(const char *fmt, ...)
+ __attribute__ ((format (printf, 1, 2)));
#define stralloc2(s1,s2) vstralloc((s1),(s2),NULL)
#define newstralloc2(p,s1,s2) newvstralloc((p),(s1),(s2),NULL)
Re: Amrestore
On Saturday 05 May 2007 09:13, Donofrio, Lewis wrote: Do I still have to use another tty to change tapes with amanda 2.5.x? Amrestore only supports one tape at a time, so you can change tapes with the same TTY. Amrecover and amfetchdump know how to use the changer now, so you don't need another tty for those, either. Cheers, --Ian -- Zmanda: Open Source Data Protection and Archiving. http://www.zmanda.com
Re: 2.5.2 compilation failure on irix-6.5.x
... cc-1084 cc: ERROR File = /usr/include/sys/socket.h, Line = 66 The indicated declaration has an invalid combination of type specifiers. typedef int socklen_t; ... I'm guessing that Jean-Francois' release of IRIX is probably newer than the one I have (IRIX 6.5.4m here). The socket.h here doesn't have a typedef for socklen_t. This also probably means that defining INET6 might be a bad idea. After looking through the amanda source and /usr/include/netinet/in.h a little more, I've found that: INET_ADDRSTRLEN is only defined if INET6 is defined. However, one thing I hadn't looked at is that on our IRIX system, WORKING_IPV6 is not being defined. From the Solaris version of netinet/in.h: /* * Miscellaneous IPv6 constants. */ #define INET_ADDRSTRLEN 16 /* max len IPv4 addr in ascii dotted */ /* decimal notation. */ #define INET6_ADDRSTRLEN46 /* max len of IPv6 addr in ascii */ /* standard colon-hex notation. */ This seems to imply that INET_ADDRSTRLEN should not be used on systems which can't do IPV6. Or an alternate definition set up. I was able to complete a build of amanda 2.5.2 on IRIX with the following addition to amanda.h and using gcc (SGI's cc won't handle the vstrallocf definition): #ifndef INET_ADDRSTRLEN #define INET_ADDRSTRLEN 16 #endif Pieter
FW: DailySet1 AMANDA VERIFY REPORT FOR DailySet101 DailySet102 DailySet103 DailySet104
Am I in trouble or are these ok? --doesn't feel alright...)-: From my # su - amanda -c /usr/sbin/amverify DailySet1 command __ Lewis [EMAIL PROTECTED] Cell: (734) 323-8776 -Original Message- From: Amanda user on the LSA dump server [mailto:[EMAIL PROTECTED] Sent: Monday, May 07, 2007 2:29 PM To: [EMAIL PROTECTED] Subject: DailySet1 AMANDA VERIFY REPORT FOR DailySet101 DailySet102 DailySet103 DailySet104 Tapes: DailySet101 DailySet102 DailySet103 DailySet104 Errors found: DailySet101 (dewey.lsa.umich.edu._.20070416.0): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring dewey.lsa.umich.edu._.20070416.0 gzip: stdin: unexpected end of file amrestore: 1: reached end of information /bin/tar: Unexpected EOF in archive /bin/tar: Error is not recoverable: exiting now 64+0 in 64+0 out DailySet101 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet101 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet101 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet101 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet101 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet102 (): amrestore: 0: skipping start of tape: date 20070416 label DailySet102 amrestore: 1: reached end of information ** No header 0+0 in 0+0 out DailySet102 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet102 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet102 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet102 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet102 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet103 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet103 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet103 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet103 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet103 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet103 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet104 (): amrestore: 0: skipping start of tape: date 20070417 label DailySet104 amrestore: 1: reached end of information ** No header 0+0 in 0+0 out DailySet104 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet104 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet104 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet104 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DailySet104 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out amverify DailySet1 Mon May 7 14:21:39 EDT 2007 Loading current slot... Using device file:/externalarray/tapes/daily Volume DailySet101, Date 20070416 Checked dewey.lsa.umich.edu._data.20070416.1 Checked dewey.lsa.umich.edu._etc.20070416.1 Checked dewey.lsa.umich.edu._var.20070416.0 ** Error detected (dewey.lsa.umich.edu._.20070416.0) amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring
Re: 2.5.2 compilation failure on irix-6.5.x
* Pieter Bowman [EMAIL PROTECTED] [20070507 15:09]: ... cc-1084 cc: ERROR File = /usr/include/sys/socket.h, Line = 66 The indicated declaration has an invalid combination of type specifiers. typedef int socklen_t; ... I'm guessing that Jean-Francois' release of IRIX is probably newer than the one I have (IRIX 6.5.4m here). The socket.h here doesn't Wow! You have 6.5.4m!?! Brave man! :) I have a mixture between 6.5.14m to 6.5.27m. My main amanda server is 6.5.19f but I'm having strange problems trying to configure on this host (configure coredumps with a memory error -- seen this before and a reboot seems to fix it). I patched and put your #defines in and using either gcc 3.3.2 or native irix C compiler seems to compile fine on a 6.5.14m host. I will install and do further tests tomorrow... thanks jf have a typedef for socklen_t. This also probably means that defining INET6 might be a bad idea. After looking through the amanda source and /usr/include/netinet/in.h a little more, I've found that: INET_ADDRSTRLEN is only defined if INET6 is defined. However, one thing I hadn't looked at is that on our IRIX system, WORKING_IPV6 is not being defined. From the Solaris version of netinet/in.h: /* * Miscellaneous IPv6 constants. */ #define INET_ADDRSTRLEN 16 /* max len IPv4 addr in ascii dotted */ /* decimal notation. */ #define INET6_ADDRSTRLEN46 /* max len of IPv6 addr in ascii */ /* standard colon-hex notation. */ This seems to imply that INET_ADDRSTRLEN should not be used on systems which can't do IPV6. Or an alternate definition set up. I was able to complete a build of amanda 2.5.2 on IRIX with the following addition to amanda.h and using gcc (SGI's cc won't handle the vstrallocf definition): #ifndef INET_ADDRSTRLEN #define INET_ADDRSTRLEN 16 #endif Pieter -- °
Re: 2.5.2 compilation failure on irix-6.5.x
... Can you try the attached patch for the vstrallocf problem. ... That corrected the problem for both IRIX and OSF/1 for me. Pieter
Re: restore not finding all incremental levels (SOLVED)
-In response to your message- --received from Jon LaBadie-- On Thu, Apr 19, 2007 at 06:50:44PM -0700, Paul Yeatman wrote: -In response to your message- --received from Jean-Louis Martineau-- Paul Yeatman wrote: So, as I continue to look at the problem, I haven't seen before that an amflush is require for the directories on holding disk to be included in a recovery yet . . . this kinda of seems to be the case now (that is as much a question as it is a statement). I see in the amindexd.###.debug log that it is trying to gzip -dc ... files in the amanda index directory for the disk being restored yet these files don't exist. For instance, the log says this is being executed /bin/gzip -dc '/etc/amanda/cass/index/cass246/_/20070331_6.gz' 2/dev/null | sort '/etc/amanda/cass/index/cass246/_/20070331_6' yet /etc/amanda/cass/index/cass246/_/20070331_6.gz does not exist; It is instead on the holding disk. Does it not exist because I have never run amflush? I swear I've performed tens of recoveries that included files on the holding disk that were (obviously) never amflushed. I'm so confused! amanda will never remove the compressed index files (.gz) while the dump are still on tape or holding disk. You said that you removed some dump from holding disk to debug your previous problem, if you ran amdump while dump was missing, amanda has removed the index file. Ah, I get it! I have another Amanda server to check with and do indeed see that all backups on the holding disk have an associated .gz file in the index directory. I CLEARLY need to change this yet, until now on this server, I have been filling a holding disk, leaving those backups there, and then changing my amanda.conf to point to a new [blank] holding disk. I always figured that in the event of a needed restore, I could change my amanda.conf to point to ALL holding disks. There was a reason I was doing this that I won't bore everyone with now. So now I see that, when changing to a new (empty) holding disk, all my previous, compressed, index files where flushed upon the next amdump run! Yikes!!! This is bad!! The good news is that the data is still there!!! But, boy, sure takes away the power of amrecover! I had no idea the consequence of this! I hope you have a backup of your index files. I suppose in a way I do but, given the current state of things, it seems it would be impossible to figure out what needs to be restored to correctly repopulate my index directory. I will hope for the time being that no restores will be needed until I create stable holding disks and repeat full backups of everything. In the meantime, should a restore be necessary, I will resort to an 'amadmin ... info' of the disk in conjuction with sequential hand-run amrestore's. Shouldn't be too major a job as you are only talking about restoring a single directory tree, the index directory tree. As the dumps are on disk, once you figure an an appropriate command line, you may even be able to automate it with a small shell script/loop. Be aware that you can specify multiple holding disks in your config. And as one of the holding disk parameters is use, you could even specify an appropriate use value for your old holding disk that makes it seem full. Then no more dumps will be added there but the old dumps will still be available for recovery. Thanks again for this! I am aware I can specify multiple holding disks and will do this from now on. I'm surprised that it has been as difficult as it has to make the disks appear full to AMANDA, however. I am using directories on the same RAID disk as holding disks and thus first tried specifying a negative Gigabyte value that was larger than the amount of space available on the RAID disk, for example I specified use -250 Gb when there is roughly 240 Gb available. Strangely, the next backup still used all directories on this disk. As my understanding of specifying use 0 Mb means use all space available, the best I've been able to come with is use 1 Mb which seems to be the smallest amount of space I can specify. This of course means, not very much, but some data is undesirably written into all holding disks (directories) every backup. I feel like I'm not quite understanding how this is supposed to work. When trying various use values, for instance, I don't quite understand what amcheck is trying to tell me. If I set use -250 Gb on one of the holding disks, for instance, amcheck tells me WARNING: holding disk /backup/vtc1/cass: only 238115672 KB free (4032823296 KB requested) The roughly 240 G free is correct but 4 Tb requested??? How does this relate to use -250 Gb? Don't get it! Paul -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ
Re: amverify - reality check?
On Monday 07 May 2007, Donofrio, Lewis wrote: Folks, I've been tasked with guaranteeing that the backup vtapes or in the future real tapes are good. So I found the command amverify that seems to be the correct routine but I want to know does it completely check the archive and the files contained within? AIUI, only that the media is readable without errors. I don't believe that a bit for bit compare has ever been attempted by any backup procedure. Bear in mind, and bring it to The Powers That be attention, that a verify pass on a real tape counts as one pass through the drive, and it also counts as wear and tear on the drive. A vtape verify pass is essentially free since the disk drives heads do not touch the disk, but fly a micron or two above the surface on a film of air carried along by the spinning disk, so there is not a major wear and tear consideration for disk drives, particularly if they spin 24/7. A tape drive, even the helical scan types, still have tape to head (and to the guides and drive rollers too) contact, real physical contact, so the wear is often calculated to be x number of running hours. Only because the tape is stopped 95% of the time do we get operating lifetimes from a tape drive that are even remotely comparable to the life of a modern hard drive. Figure on 1000 to 8000 hours for a tape drive, the latter figure only achievable in a clean room at 50F and less than 20% relative humidity. High temps, and high humidity both make tape a lot more abrasive. I have hard drives spinning here, right now, with over 50,000 hours on them. And no bad sectors according to smartctl. Your management would be served a lot better, by filling a 500GB drive and if long term storage is needed or demanded, put that drive in the safe, offsite, until such time as the data is too old, and then recycle it back into the system just as if it was a 2 year old tape. The costs might be a bit more than for equ tape storage, but at this stage of the technology, I'm convinced the hard drive is the more dependable device of the two. I switched about 3 years ago, don't worry about offsite or long term as I'm just a home user, and the hard drive has been so much more dependable I'm amazed. I had tape trouble or drive trouble at least weekly, and I plumb wore out 4 of those Seagate changers before I gave up. Now I just read the emails I get from amanada, and stack the printout, and other than playing canary for new amanda releases, I've forgotten about 'did my backup run ok' questions. Barring a major power failure, which we had last night, it Just Works(TM). YMMV of course. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) The beauty of a pun is in the Oy! of the beholder.
Re: amverify - reality check?
I've been tasked with guaranteeing that the backup vtapes or in the future real tapes are good. So I found the command amverify that seems to be the correct routine but I want to know does it completely check the archive and the files contained within? Amverify will try to extract any backup from the backup media, uncompress the files and see if they are readable. By no mean amverify will conduct a comparison file by file, for the simple reason that we are talking about live system and the files will have change between the moment they were backuped and the moment they are verified, so the verification would always show non-matching files, so you could not say anything about the correctness of your backup. To add to the answer of Gene, yes, amverify add wears and tears to the tape and the tape drive, but I have been using it anyway, just to be sure. I don't use cheap helical type tapes, that gets too much problems, but expensive ones, they are more expensive than a disk drive nowdays, so the next choice will be vtapes on some extractible disk. Bests, Olivier
Re: amverify - reality check?
On Tue, May 08, 2007 at 09:42:52AM +0700, Olivier Nicole wrote: I've been tasked with guaranteeing that the backup vtapes or in the future real tapes are good. So I found the command amverify that seems to be the correct routine but I want to know does it completely check the archive and the files contained within? Amverify will try to extract any backup from the backup media, uncompress the files and see if they are readable. By no mean amverify will conduct a comparison file by file, for the simple reason that we are talking about live system and the files will have change between the moment they were backuped and the moment they are verified, so the verification would always show non-matching files, so you could not say anything about the correctness of your backup. If the backup were done on a snapshot this objection might be worked around. Another reason a general procedure for verification does not exist is that the backups are not done by the server, they are done by the clients. The backup, compression, encryption, etc. programs are all over there. The same programs may not even exist on the server. So the dump would have to be extracted from the backup medium, transfered across the network to the client, expanded from the archive, and compared to the files on the client. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
