Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

2017-09-23 Thread Charles Curley
On Mon, 18 Sep 2017 10:10:02 -0400 Jean-Louis Martineau wrote: > It is a compatibility issue between amrecover 3.3 and a 3.4 server. > The restore is successful, It is the error message that is bogus. > > Try the attached compat-crc.diff patch. > Patching only the perl/Amanda/Restore.pm should f

Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

2017-09-14 Thread Charles Curley
On Fri, 8 Sep 2017 09:42:36 -0400 Jean-Louis Martineau wrote: > Which version of amanda are you using? > > On 09/08/17 05:03 PM, Charles Curley wrote: > > Does anyone know what this message from amrecover means? Is it a > > problem? > > > > client-crc in head

Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

2017-09-13 Thread Jean-Louis Martineau
recover means? Is it a > > > problem? > > > > > > client-crc in header (01591e60:14438416) and client-crc in log > > > (38e41ca3:40960) differ > > > > They should be identical. > > I managed to loose the data that prompted the email. However, I have

Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

2017-09-12 Thread Jean-Louis Martineau
What are the crc logged in the log file for that dump? Post the log.20170908000101.0 file On 12/09/17 03:10 PM, Charles Curley wrote: > On Tue, 12 Sep 2017 14:34:17 -0400 > Jean-Louis Martineau wrote: > >> On 12/09/17 01:32 PM, Charles Curley wrote: >>> Can you post the dump header? >>

Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

2017-09-12 Thread Charles Curley
On Tue, 12 Sep 2017 14:34:17 -0400 Jean-Louis Martineau wrote: > On 12/09/17 01:32 PM, Charles Curley wrote: > > > > > Can you post the dump header? > > > > Where do I find it? > > amfetchdump -p -h CONF HOST DISK DATESTAMP | dd bs=32k count=1 backup@hawk:~$ amfetchdump -p -h DailySet1 ch

Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

2017-09-12 Thread Jean-Louis Martineau
On 12/09/17 01:32 PM, Charles Curley wrote: > > > Can you post the dump header? > > Where do I find it? amfetchdump -p -h CONF HOST DISK DATESTAMP | dd bs=32k count=1 This message is the property of CARBONITE, INC. and may contain confidential or privileged information. If this message has been d

Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

2017-09-08 Thread Jean-Louis Martineau
Which version of amanda are you using? On 09/08/17 05:03 PM, Charles Curley wrote: > Does anyone know what this message from amrecover means? Is it a > problem? > > client-crc in header (01591e60:14438416) and client-crc in log > (38e41ca3:40960) differ They should be identica

client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

2017-09-08 Thread Charles Curley
Does anyone know what this message from amrecover means? Is it a problem? client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ I am working on some bare metal restore software (http://www.tldp.org/HOWTO/Linux-Complete-Backup-and-Recovery-HOWTO/index.html). I