Hi Jeffrey,
Sounds doable, but as I say, I'm backing a Linux server, not a Win client,
so I don't think I need to worry too much about the busy files...
Thanks for the suggestion though...
Cheers,
Jx
On Thu, Jul 30, 2009 at 8:19 PM, Jeffrey J. Kosowsky
wrote:
> Matthias Meyer wrote at about 21:00
Hi Matthias,
Sorry it took me so long to get back to you - I've had a lot of tight
deadlines.
I'm not backing up a windows client... It's a Linux server offering a samba
share.
To be fair, thinking about it, since I'm using rsync, it's just a Linux
server, and the fact that I access it with Windows
Matthias Meyer wrote at about 21:00:54 +0200 on Thursday, July 30, 2009:
> Vetch wrote:
>
> > Hi Matthias,
> > All my xferlogs say they have 0 errors (apart from one, but that was after
> > the problem occurred anyway)...
> > I've had a look at them, but they are... quite long...
> > Withou
Vetch wrote:
> Hi Matthias,
> All my xferlogs say they have 0 errors (apart from one, but that was after
> the problem occurred anyway)...
> I've had a look at them, but they are... quite long...
> Without knowing what to search for, I'm not sure what I can do with
> them... If they report no erro
Hi Matthias,
All my xferlogs say they have 0 errors (apart from one, but that was after
the problem occurred anyway)...
I've had a look at them, but they are... quite long...
Without knowing what to search for, I'm not sure what I can do with them...
If they report no errors, I guess I can assume a
You should check the backup log file XferLOG.
Each file which can not backup will be logged theire, including the reason.
br
Matthias
--
Don't Panic
--
___
BackupPC-users mail
Hi Jeffrey,
Thanks for getting back to me...
On Wed, Jul 22, 2009 at 1:22 AM, Jeffrey J. Kosowsky
wrote:
> Vetch wrote at about 00:14:06 +0100 on Wednesday, July 22, 2009:
[snip]
>
> Well, with Windows there can be all kinds of reasons for mismatches
> including:
> 1. Busy files that can't be b
Hi,
sorry for replying so late, busy week.
Matthias Meyer wrote on 2009-07-20 21:59:49 +0200 [Re: [BackupPC-users] Restore
issues]:
> Vetch wrote:
> > I tried restoring a backup to my system - it kept on failing with aborted
> > by signal=PIPE.
> > I have a feeling it may
Vetch wrote at about 00:14:06 +0100 on Wednesday, July 22, 2009:
> Hi Matthias,
>
> Thanks for your help on this...
>
> See replies below...
>
> On Tue, Jul 21, 2009 at 6:40 PM, Matthias Meyer wrote:
>
> > Vetch wrote:
> >
> > >
> > > Ok - I tried direct restores back into the origi
Hi Matthias,
Thanks for your help on this...
See replies below...
On Tue, Jul 21, 2009 at 6:40 PM, Matthias Meyer wrote:
> Vetch wrote:
>
> >
> > Ok - I tried direct restores back into the original directories over the
> > network - and it came up with successful restores for all the home
> > d
Vetch wrote:
>
> Ok - I tried direct restores back into the original directories over the
> network - and it came up with successful restores for all the home
> directories...
> Does this mean that the data has been fully successfully restored?
Probably. But as I said, BackupPC didn't check file
Hi Matthias,
Thanks for getting back to me...
I've put my replies below...
On Mon, Jul 20, 2009 at 8:59 PM, Matthias Meyer wrote:
> Vetch wrote:
>
> > Hi all,
> >
> > I have a question...
> >
> > I tried restoring a backup to my system - it kept on failing with aborted
> > by signal=PIPE.
> > I h
Vetch wrote:
> Hi all,
>
> I have a question...
>
> I tried restoring a backup to my system - it kept on failing with aborted
> by signal=PIPE.
> I have a feeling it may have been related to corrupt files within the
> hardlinks, since when I tried restoring using tar, the tar files were not
> re
Hi all,
I have a question...
I tried restoring a backup to my system - it kept on failing with aborted by
signal=PIPE.
I have a feeling it may have been related to corrupt files within the
hardlinks, since when I tried restoring using tar, the tar files were not
readable, and the zip files didn't
backuppc-users@lists.sourceforge.net
Subject: Re: [BackupPC-users] Restore Issues with larger files
Lee writes:
> Sorr I missed information. I am restoring to RHEL4 box. I can
transfer 500MB files no problem, but once I try 2GB or more it fails
with a PIPE error. I have been able to transfer a 2G
Lee writes:
> Sorr I missed information. I am restoring to RHEL4 box. I can transfer
> 500MB files no problem, but once I try 2GB or more it fails with a PIPE
> error. I have been able to transfer a 2GB file maybe twice out of the 20
> times I've tried. Any ideas?
>
> Not directly related
>> You are restoring to Linux, Windows, MacOSX? 2G is, for example the size
> limit for > FAT32, no way you can restore a bigger file to a, say WinXP with
> FAT32.
> I think you mean that 2 GB is the limit for FAT16. Windows 95a was the last
> FAT16 operating system released by Microsoft.
No, I
-444-3937
If you require immediate response please send your inquiry to
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Baker
Sent: Monday, May 19, 2008 3:16 PM
To: backuppc-users@lists.sourceforge.net
Subject: Re: [BackupPC-u
Chris Baker wrote:
>> You are restoring to Linux, Windows, MacOSX? 2G is, for example the size
> limit for > FAT32, no way you can restore a bigger file to a, say WinXP with
> FAT32.
>
>> Eduardo.
>
> I think you mean that 2 GB is the limit for FAT16. Windows 95a was the last
> FAT16 operating s
> You are restoring to Linux, Windows, MacOSX? 2G is, for example the size
limit for > FAT32, no way you can restore a bigger file to a, say WinXP with
FAT32.
> Eduardo.
I think you mean that 2 GB is the limit for FAT16. Windows 95a was the last
FAT16 operating system released by Microsoft.
The
> I get the error below with large files, this one is around 2GB, files around
> 500MB transfer and restore with no problem. What can be causing this? I am
> running rsync 2.6.8 on both client and server.
You are restoring to Linux, Windows, MacOSX? 2G is, for example the size limit
for FAT32,
ECTED] On Behalf Of Lee A.
Connell
Sent: Friday, May 16, 2008 3:34 PM
To: backuppc-users@lists.sourceforge.net
Subject: [BackupPC-users] Restore Issues with larger files
I get the error below with large files, this one is around 2GB, files around
500MB transfer and restore with no problem. What c
I get the error below with large files, this one is around 2GB, files
around 500MB transfer and restore with no problem. What can be causing
this? I am running rsync 2.6.8 on both client and server.
Server Log
Sorted file list has 1 entries
PostSortFile 0: BACKUP_DB_WBBI_S_3201_P_2_T_6548
23 matches
Mail list logo
