Re: problems running backup

2016-01-22 Thread Bob Holtzman
On Thu, Jan 21, 2016 at 09:54:27PM +0100, Ulf Volmer wrote:
> On 01/20/2016 10:33 PM, Bob Holtzman wrote:
> >>On 12/3/15, Bob Holtzman  wrote:
> 
> >>>rsync: mkdir "/media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop"
> >>>failed: No such file or directory (2)
> >>>rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.1]
> >>>
> >>>That second line is strange as I had just created the Jessie-laptop
> >>>directory.
> 
> >1) Target was external HD and was mounted.
> 
> Which filesystem do you use on your target drive?

At the moment I can't check this but I seem to recall formatting the external 
HD to ext3.
No matter what it is, it always worked with previous versions of debian and 
ubuntu.



Re: problems running backup

2016-01-21 Thread ken

On 01/21/2016 12:33 AM, Bob Holtzman wrote:

On Wed, Jan 20, 2016 at 04:59:05PM -0500, ken wrote:

On 01/20/2016 04:33 PM, Bob Holtzman wrote:

2) Target partition was mounted BUT had quietly been auto-renamed by

my system k/t that another partition was already bearing the same
label name. Fodder for another eventual thread and why I love and
advocate UUIDs over labels or other.

1) Target was external HD and was mounted.


The simple matter of permissions is often the problem.  This kind of problem
has cropped up for me before over an upgrade (not yet with Debian though).

Also, what exactly is the error message?  Can you increase its verbosity
so's to examine that as well?


In case you deleted my original post, the error message is:

  rsync: mkdir "/media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop"
  failed: No such file or directory (2)
  rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.1]

I already had verbosity turned on except I believe that refers to the list of 
files as they're
backed up. Not sure how to expand an error message, or even if that's possible.

Permissions are 700 for the executable file.

I'm snowed. Any other ideas?



Can you do at the cli

'mkdir "/media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop"'

as the same user as runs rsync?



Re: problems running backup

2016-01-21 Thread Bob Holtzman
On Thu, Jan 21, 2016 at 04:14:58AM -0500, ken wrote:
> On 01/21/2016 12:33 AM, Bob Holtzman wrote:
> >On Wed, Jan 20, 2016 at 04:59:05PM -0500, ken wrote:
> >>On 01/20/2016 04:33 PM, Bob Holtzman wrote:
> 2) Target partition was mounted BUT had quietly been auto-renamed by
> >my system k/t that another partition was already bearing the same
> >label name. Fodder for another eventual thread and why I love and
> >advocate UUIDs over labels or other.
> >>>1) Target was external HD and was mounted.
> >>
> >>The simple matter of permissions is often the problem.  This kind of problem
> >>has cropped up for me before over an upgrade (not yet with Debian though).
> >>
> >>Also, what exactly is the error message?  Can you increase its verbosity
> >>so's to examine that as well?
> >>
> >In case you deleted my original post, the error message is:
> >
> >  rsync: mkdir "/media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop"
> >  failed: No such file or directory (2)
> >  rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.1]
> >
> >I already had verbosity turned on except I believe that refers to the list 
> >of files as they're
> >backed up. Not sure how to expand an error message, or even if that's 
> >possible.
> >
> >Permissions are 700 for the executable file.
> >
> >I'm snowed. Any other ideas?
> >
> 
> Can you do at the cli
> 
> 'mkdir "/media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop"'
> 
> as the same user as runs rsync?

As I said in an earlier post in this thread, I had created the Jessie-laptop 
directory previously.



Re: problems running backup

2016-01-21 Thread Bob Holtzman
On Thu, Jan 21, 2016 at 01:13:04AM -0500, Gene Heskett wrote:
> On Thursday 21 January 2016 00:33:45 Bob Holtzman wrote:
> 
> > On Wed, Jan 20, 2016 at 04:59:05PM -0500, ken wrote:
> > > On 01/20/2016 04:33 PM, Bob Holtzman wrote:
> > > >>2) Target partition was mounted BUT had quietly been auto-renamed
> > > >> by
> > > >>
> > > >>>my system k/t that another partition was already bearing the same
> > > >>>label name. Fodder for another eventual thread and why I love and
> > > >>>advocate UUIDs over labels or other.
> > > >
> > > >1) Target was external HD and was mounted.
> > >
> > > The simple matter of permissions is often the problem.  This kind of
> > > problem has cropped up for me before over an upgrade (not yet with
> > > Debian though).
> > >
> > > Also, what exactly is the error message?  Can you increase its
> > > verbosity so's to examine that as well?
> >
> > In case you deleted my original post, the error message is:
> >
> >  rsync: mkdir
> > "/media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop" failed: No
> > such file or directory (2)
> >  rsync error: error in file IO (code 11) at main.c(674)
> > [Receiver=3.1.1]
> >
> > I already had verbosity turned on except I believe that refers to the
> > list of files as they're backed up. Not sure how to expand an error
> > message, or even if that's possible.
> >
> > Permissions are 700 for the executable file.
> >
> > I'm snowed. Any other ideas?
> 
> Permissions of 0700 means that only the owner:group of that file can do 
> anything with it, nobody else can read it, or exec it.

True. The owner and group of the file is myself.

Keep trying. Thanks.



Re: problems running backup

2016-01-21 Thread Ulf Volmer

On 01/20/2016 10:33 PM, Bob Holtzman wrote:

On 12/3/15, Bob Holtzman  wrote:



rsync: mkdir "/media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop"
failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.1]

That second line is strange as I had just created the Jessie-laptop
directory.



1) Target was external HD and was mounted.


Which filesystem do you use on your target drive?

best regards
Ulf Volmer



Re: problems running backup

2016-01-20 Thread Gene Heskett
On Thursday 21 January 2016 00:33:45 Bob Holtzman wrote:

> On Wed, Jan 20, 2016 at 04:59:05PM -0500, ken wrote:
> > On 01/20/2016 04:33 PM, Bob Holtzman wrote:
> > >>2) Target partition was mounted BUT had quietly been auto-renamed
> > >> by
> > >>
> > >>>my system k/t that another partition was already bearing the same
> > >>>label name. Fodder for another eventual thread and why I love and
> > >>>advocate UUIDs over labels or other.
> > >
> > >1) Target was external HD and was mounted.
> >
> > The simple matter of permissions is often the problem.  This kind of
> > problem has cropped up for me before over an upgrade (not yet with
> > Debian though).
> >
> > Also, what exactly is the error message?  Can you increase its
> > verbosity so's to examine that as well?
>
> In case you deleted my original post, the error message is:
>
>  rsync: mkdir
> "/media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop" failed: No
> such file or directory (2)
>  rsync error: error in file IO (code 11) at main.c(674)
> [Receiver=3.1.1]
>
> I already had verbosity turned on except I believe that refers to the
> list of files as they're backed up. Not sure how to expand an error
> message, or even if that's possible.
>
> Permissions are 700 for the executable file.
>
> I'm snowed. Any other ideas?

Permissions of 0700 means that only the owner:group of that file can do 
anything with it, nobody else can read it, or exec it.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 



Re: problems running backup

2016-01-20 Thread Bob Holtzman
On Wed, Jan 20, 2016 at 04:59:05PM -0500, ken wrote:
> On 01/20/2016 04:33 PM, Bob Holtzman wrote:
> >>2) Target partition was mounted BUT had quietly been auto-renamed by
> >>>my system k/t that another partition was already bearing the same
> >>>label name. Fodder for another eventual thread and why I love and
> >>>advocate UUIDs over labels or other.
> >1) Target was external HD and was mounted.
> 
> The simple matter of permissions is often the problem.  This kind of problem
> has cropped up for me before over an upgrade (not yet with Debian though).
> 
> Also, what exactly is the error message?  Can you increase its verbosity
> so's to examine that as well?
> 
In case you deleted my original post, the error message is:

 rsync: mkdir "/media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop"
 failed: No such file or directory (2)
 rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.1]

I already had verbosity turned on except I believe that refers to the list of 
files as they're 
backed up. Not sure how to expand an error message, or even if that's possible.

Permissions are 700 for the executable file.

I'm snowed. Any other ideas?  



Re: problems running backup

2016-01-20 Thread Cindy-Sue Causey
On 12/3/15, Bob Holtzman  wrote:
> Just installed Jessie and I'm still picking my way thru it. When I tried
> invoking "scripts/backup" as root I get:
>
> rsync: mkdir "/media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop"
> failed: No such file or directory (2)
> rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.1]
>
> That second line is strange as I had just created the Jessie-laptop
> directory.
>
> My backup script has always worked in Wheezy:
>
> rsync -vahHz --delete --exclude '/proc' --exclude '*.iso' --exclude
> '/home/holtzm/mail/backup' --exclude '/sys ' --exclude '/tmp' --exclude
> '/media' /. /media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop
>
> Searching on the error message yielded zip. I'd appreciate any pointers
> on how to attack this.


Found this while thinning my inbox. Adding something for the archives
from one who makes a lot of manual mistakes. I've seen similar errors
under two different circumstances:

1) My target partition wasn't mounted. *oops*

2) Target partition was mounted BUT had quietly been auto-renamed by
my system k/t that another partition was already bearing the same
label name. Fodder for another eventual thread and why I love and
advocate UUIDs over labels or other.

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* sometimes words #fail me. *



Re: problems running backup

2016-01-20 Thread Bob Holtzman
On Wed, Jan 20, 2016 at 12:25:46PM -0500, Cindy-Sue Causey wrote:
> On 12/3/15, Bob Holtzman  wrote:
> > Just installed Jessie and I'm still picking my way thru it. When I tried
> > invoking "scripts/backup" as root I get:
> >
> > rsync: mkdir "/media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop"
> > failed: No such file or directory (2)
> > rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.1]
> >
> > That second line is strange as I had just created the Jessie-laptop
> > directory.
> >
> > My backup script has always worked in Wheezy:
> >
> > rsync -vahHz --delete --exclude '/proc' --exclude '*.iso' --exclude
> > '/home/holtzm/mail/backup' --exclude '/sys ' --exclude '/tmp' --exclude
> > '/media' /. /media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop
> >
> > Searching on the error message yielded zip. I'd appreciate any pointers
> > on how to attack this.
> 
> 
> Found this while thinning my inbox. Adding something for the archives
> from one who makes a lot of manual mistakes. I've seen similar errors
> under two different circumstances:
> 
> 1) My target partition wasn't mounted. *oops*
> 
> 2) Target partition was mounted BUT had quietly been auto-renamed by
> my system k/t that another partition was already bearing the same
> label name. Fodder for another eventual thread and why I love and
> advocate UUIDs over labels or other.

1) Target was external HD and was mounted.

2) Note the use of the UUID in my post. I'm with you.

3) I'm still at sea on this.

4) Thanks for the effort.



Re: problems running backup

2016-01-20 Thread ken

On 01/20/2016 04:33 PM, Bob Holtzman wrote:

2) Target partition was mounted BUT had quietly been auto-renamed by
>my system k/t that another partition was already bearing the same
>label name. Fodder for another eventual thread and why I love and
>advocate UUIDs over labels or other.

1) Target was external HD and was mounted.


The simple matter of permissions is often the problem.  This kind of 
problem has cropped up for me before over an upgrade (not yet with 
Debian though).


Also, what exactly is the error message?  Can you increase its verbosity 
so's to examine that as well?





problems running backup

2015-12-03 Thread Bob Holtzman
Just installed Jessie and I'm still picking my way thru it. When I tried
invoking "scripts/backup" as root I get:

rsync: mkdir "/media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop"
failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.1]

That second line is strange as I had just created the Jessie-laptop
directory.

My backup script has always worked in Wheezy:

rsync -vahHz --delete --exclude '/proc' --exclude '*.iso' --exclude
'/home/holtzm/mail/backup' --exclude '/sys ' --exclude '/tmp' --exclude
'/media' /. /media/cf0a98ed-3c11-4107-b61e-f5139d024396/Jessie-laptop

Searching on the error message yielded zip. I'd appreciate any pointers
on how to attack this.




Re: problems running backup

2015-12-03 Thread John Hasler
Bob Holtzman writes:
> That second line is strange as I had just created the Jessie-laptop
> directory.

The message does not necessarily refer to *that* file or directory.
IIRC you can get that message from the loader when it can't find a
library.  Run the rsync command under strace.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA



Re: running backup

2006-05-31 Thread Florian Kulzer
On Wed, May 31, 2006 at 13:56:39 +0800, Jon  Miller wrote:
 I have a file that I want to run daily to backup data.  This tgz file then 
 needs to be copied to a Windows 2003 server.  I'm using smbclient, but it 
 does not seem to work thru the script.  Can someone point out where the 
 problem lies.  I run this as a cron job as follows:
 30 19 * * 1,2,3,4,5 root /root/rubybackup.sh
 
 The script is as follows:
 #!/bin/sh
 # script to automate the backup of the Ruby server to the W2K3 server
 #
 DAY=`date +'%a-%d-%m-%y'`
 BACKUPDIR=/backup
 RUBYLIVE=/var/lib/mysql/
 
 cd $RUBYLIVE
 tar -czvf /backup/rubylive${DAY}.tgz ./rubylive
 
 cd $BACKUPDIR
 smbclient //server/backup tfc651800 -U administrator
 put rubylive${DAY}.tgz

The recommended procedure for smbclient in scripts is to use the -c
option for the command string. In your case that would probably be
something like

smbclient //server/backup tfc651800 -U administrator -c put 
rubylive${DAY}.tgz; exit

Is it really necessary to use the administrator account for pushing a
backup file to the server?

-- 
Regards,
  Florian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: running backup

2006-05-31 Thread Ron Johnson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Florian Kulzer wrote:
 On Wed, May 31, 2006 at 13:56:39 +0800, Jon  Miller wrote:
 I have a file that I want to run daily to backup data.  
This tgz file then needs to be copied to a Windows 2003 server.
I'm using smbclient, but it does not seem to work thru the script.
Can someone point out where the problem lies.  I run this as a
cron job as follows:
 30 19 * * 1,2,3,4,5 root /root/rubybackup.sh

 The script is as follows:
 #!/bin/sh
 # script to automate the backup of the Ruby server to the W2K3 server
 #
 DAY=`date +'%a-%d-%m-%y'`
 BACKUPDIR=/backup
 RUBYLIVE=/var/lib/mysql/

 cd $RUBYLIVE
 tar -czvf /backup/rubylive${DAY}.tgz ./rubylive

 cd $BACKUPDIR
 smbclient //server/backup tfc651800 -U administrator
 put rubylive${DAY}.tgz
 
 The recommended procedure for smbclient in scripts is to use the -c
 option for the command string. In your case that would probably be
 something like
 
 smbclient //server/backup tfc651800 -U administrator -c put 
 rubylive${DAY}.tgz; exit
 
 Is it really necessary to use the administrator account for pushing a
 backup file to the server?

Windows has functional non-Administrator accounts??  :\

- --
Ron Johnson, Jr.
Jefferson LA  USA

Is common sense really valid?
For example, it is common sense to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that common sense is obviously wrong.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEfVUqS9HxQb37XmcRAuiTAJ4mM5kh1BhjohIyRlVbO6iDNGErVQCeKpl4
4mE7ehcYYEZWwkQsSXuzN/s=
=plQI
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: running backup

2006-05-31 Thread Florian Kulzer
On Wed, May 31, 2006 at 03:34:51 -0500, Ron Johnson wrote:
 Florian Kulzer wrote:
  On Wed, May 31, 2006 at 13:56:39 +0800, Jon  Miller wrote:
  I have a file that I want to run daily to backup data.  
 This tgz file then needs to be copied to a Windows 2003 server.
 I'm using smbclient, but it does not seem to work thru the script.
 Can someone point out where the problem lies.  I run this as a
 cron job as follows:
  30 19 * * 1,2,3,4,5 root /root/rubybackup.sh
 
  The script is as follows:
  #!/bin/sh
  # script to automate the backup of the Ruby server to the W2K3 server
  #
  DAY=`date +'%a-%d-%m-%y'`
  BACKUPDIR=/backup
  RUBYLIVE=/var/lib/mysql/
 
  cd $RUBYLIVE
  tar -czvf /backup/rubylive${DAY}.tgz ./rubylive
 
  cd $BACKUPDIR
  smbclient //server/backup tfc651800 -U administrator
  put rubylive${DAY}.tgz
  
  The recommended procedure for smbclient in scripts is to use the -c
  option for the command string. In your case that would probably be
  something like
  
  smbclient //server/backup tfc651800 -U administrator -c put 
  rubylive${DAY}.tgz; exit
  
  Is it really necessary to use the administrator account for pushing a
  backup file to the server?
 
 Windows has functional non-Administrator accounts??  :\

Oops, my bad. Can we all pretend that it was a rhetorical question?

-- 
Regards,
  Florian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: running backup

2006-05-31 Thread Jon Dowland
At 1149083799 past the epoch, Jon  Miller wrote:
 cd $BACKUPDIR
 smbclient //server/backup tfc651800 -U administrator
 put rubylive${DAY}.tgz

I think Florian has hit on the problem here, but it would be
easier in general if you supplied some kind of diagnostic
output rather than just it does not work.

-- 
Jon Dowland
http://alcopop.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: running backup

2006-05-31 Thread Dave Ewart
On Wednesday, 31.05.2006 at 13:56 +0800, Jon  Miller wrote:

 #!/bin/sh
 # script to automate the backup of the Ruby server to the W2K3 server
 #
 DAY=`date +'%a-%d-%m-%y'`
 BACKUPDIR=/backup
 RUBYLIVE=/var/lib/mysql/
 
 cd $RUBYLIVE
 tar -czvf /backup/rubylive${DAY}.tgz ./rubylive

(Not related to what you asked, but might be important)

Are you backing up MySQL databases here via there location in the
filesystem?  If so, this is 'unsafe', since any changes made to the
databases during your 'tar' will not be handled properly: this *could*
result in a partially- or completely-useless backup.

You should really backup MySQL databases using mysqldump instead.

If that's not what you're doing, apologies...

Dave.
-- 
Please don't CC me on list messages!
...
Dave Ewart - [EMAIL PROTECTED] - jabber: [EMAIL PROTECTED]
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92



signature.asc
Description: Digital signature


running backup

2006-05-30 Thread Jon Miller
I have a file that I want to run daily to backup data.  This tgz file then 
needs to be copied to a Windows 2003 server.  I'm using smbclient, but it does 
not seem to work thru the script.  Can someone point out where the problem 
lies.  I run this as a cron job as follows:
30 19 * * 1,2,3,4,5 root /root/rubybackup.sh

The script is as follows:
#!/bin/sh
# script to automate the backup of the Ruby server to the W2K3 server
#
DAY=`date +'%a-%d-%m-%y'`
BACKUPDIR=/backup
RUBYLIVE=/var/lib/mysql/

cd $RUBYLIVE
tar -czvf /backup/rubylive${DAY}.tgz ./rubylive

cd $BACKUPDIR
smbclient //server/backup tfc651800 -U administrator
put rubylive${DAY}.tgz


Thanks