flexbackup-help — Support/help/usage

[flexbackup-help] Pb restoring from an afio-gz backup

[arakeis <ar...@fr...>]

here are my backup files :
total 8631140
drwxr-xr-x    2 root     root         4096 fév 20 11:55 ./
drwxr-xr-x    5 root     root         4096 jan  6 15:55 ../
-rw-r--r--    1 root     root           44 fév 13 12:35 00-index-key
-rw-r--r--    1 root     root     6124154880 fév 13 14:28
export-sambaraid-samba_x.0.200302131322.afio-gz
-rw-r--r--    1 root     root      7761920 fév 17 11:22
export-sambaraid-samba_x.1.200302171122.afio-gz
-rw-r--r--    1 root     root     885893120 fév 13 15:16

I've got a certain file listed in "files-to-restore.lst"

when trying :
flexbackup -extract export-sambaraid-samba_x.0.200302131322.afio-gz
-files files-to-restore.lst

here is the output :

|------------------------------------------------------------
| Checking 'buffer' on this machine... Ok
| Checking /bin/sh on this machine... bash2
|------------------------------------------------------------
| Logging output to "flexbackup.extract.200302201155.log"
Error: file "export-sambaraid-samba_x.0.200302131322.afio-gz" or
"/export/sambabackup/export-sambaraid-samba_x.0.200302131322.afio-gz"
not found
(like "-list file.tar.bz2")
Died at /usr/bin/flexbackup line 2897.

I checked that ulimit was not on the way : it is set to "unlimited"
both afio and buffer where rebuilded from the sources on the site
so I'm a bit lost ...

does anyone see's what is wrong ???
what should be the command line to extrat with afio ?

thanks,

Arnaud

RE: [flexbackup-help] Version 1.01 and mt setblk in Linux

[John R. <jo...@re...>]

[ On Wednesday, February 19, Luis Cortes wrote: ]
> My Perl is REAL rusty, can anyone tell me what to change in flexbackup
> to get it to change from:
>  cpio -t -v -C 32768
> 
> to
> cpio -t -v --block-size=64
> 
> Thanks ahead of time for any help,
> Luis.
> 

at line 2266 put

	$main::cpio_blk_flag = "--block-size=$main::cpio_blk_flag";

(you can either add that line into the code after the line that says
$main::cpio_blk_flag = "-C $main::cpio_blk_flag"; and the cpio_blk_flag
variable will just get overriden, or you can comment out the "-C" line with
a '#' and then add the --block-size line).

Hope this helps. If it does, maybe there's some things that Edwin and I can do
to "steer" flexbackup to do the right thing given a config knob or something.

-Jr

-- 
John & Jennifer Reynolds  jo...@re...  http://www.reynoldsnet.org/
Sr. Component Design Engineer, ICG, Intel Corp.    jre...@se...
Running FreeBSD since 2.1.5-RELEASE.               FreeBSD: The Power to Serve!
"Unix is user friendly, it's just particular about the friends it chooses."

RE: [flexbackup-help] Version 1.01 and mt setblk in Linux

[Luis C. <ad...@co...>]

My Perl is REAL rusty, can anyone tell me what to change in flexbackup
to get it to change from:
 cpio -t -v -C 32768

to
cpio -t -v --block-size=64


Thanks ahead of time for any help,
Luis.


-----Original Message-----
From: fle...@li...
[mailto:fle...@li...] On Behalf Of Luis
Cortes
Sent: Monday, February 17, 2003 11:08 AM
To: fle...@li...
Subject: Re: [flexbackup-help] Version 1.01 and mt setblk in Linux


Okay here is the error I get:



flexbackup version 1.0.1 (http://flexbackup.sourceforge.net)
/etc/flexbackup.conf syntax OK

|------------------------------------------------------------
| Checking /bin/sh on this machine... bash2
|------------------------------------------------------------
| Logging output to "flexbackup.list.200302171143.log"
| Trying "mt defblksize" instead of "mt setblk"
| Reading from current tape position
|------------------------------------------------------------
At block 134227397.
|------------------------------------------------------------
| dd ibs=32k obs=32k conv=noerror,sync if="/dev/nst0" | cpio -t -v -C 
|32768
|------------------------------------------------------------
1+0 records in
1+0 records out
cpio: premature end of archive
|------------------------------------------------------------
At block 134227401.
|------------------------------------------------------------


When I change the cpio command to block-size=64 instead of C, then it
works:

cpio -t -v --block-size=64


I think it is just my tape is real finicky about blocks.

I guess I will need to do with same with gzip.



----- Original Message -----
From: "Edwin Huffstutler" <ed...@co...>
To: "Luis Cortes" <ad...@co...>
Cc: <fle...@li...>
Sent: Sunday, February 16, 2003 8:37 AM
Subject: Re: [flexbackup-help] Version 1.01 and mt setblk in Linux


>
> [ Luis Cortes wrote: ]
> > Okay, let me clarify my own response.  I believe that for programs 
> > like
tar
> > or cpio, the default block size is 512.  When you specify 64 blocks,
>
> Nope.
>
> tar and many others default to 10k.  cpio does default to 512 bytes.  
> We don't use defaults for anything anyway, so it doesn't matter.
>
> > flexbackup thinks it's 1024 * 64.  If you specify 64 blocks for cpio

> > it means 512 * 64.  It seems to me that there is a logic problem 
> > somewhere.
Am
> > I right about this?
>
> Nope.
>
> The config file says "Block size (k)" for $blksize, and that's what it

> means.  It's converted for whichever archiver as needed.
>
> Flexbackup sets the flags are all set so units are consistent.  Check 
> the manpages and code.
>
>
> tar:
>   -b, --block-size N
>          block size of Nx512 bytes (default N=20)
>
> cpio: (flexbackup uses the -C flag!)
>   -C IO-SIZE, --io-size=IO-SIZE
>         Set the I/O block size to IO-SIZE bytes.
>
> dump:
>   -b blocksize
>              The number of kilobytes per dump record.  Since the IO
system
>              slices all requests into chunks of MAXBSIZE (typically 
> 64kB),
it
>              is not possible to use a larger blocksize without having
problems
>              later with restore(8).  Therefore dump will constrain 
> writes
to
>              MAXBSIZE.  The default blocksize is 10.
>
> afio:
>   -b size      Read  or write size-character archive blocks.  Suffices
of
>                b,  k,  m  and  g  denote  multiples  of  512,
kilobytes,
>                megabytes  and  gigabytes, respectively.  Defaults to
5120
>                for compatibility with cpio(1).  In  some  cases,
notably
>                when  using  ftape with some tape drives, -b 10k is
needed
>                for compatibility.  Note that -b 10k is the default
block
>                size used by tar(1), so it is usually a good choice if
the
>                tape setup is known to work with tar(1).
>
> etc..
>
> --
>  Edwin Huffstutler     Linux - because reboots are for hardware
changes
>  ed...@co...   GnuPG Key ID: AE782DC9
>
>
>



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
flexbackup-help mailing list fle...@li...
https://lists.sourceforge.net/lists/listinfo/flexbackup-help

Re: [flexbackup-help] bugreport "can't write to /dev/tape" when using remote tape

[Edwin H. <ed...@co...>]

[ raphael deimel wrote: ]
> the script (version 1.0.1) checks the existence of the tape device 
> locally, although i told it a remote tapedevice
> 
> line 2174:
>     if (! -w $main::device) {
>         push(@main::errors,"Can't write to $main::device");
>     }
> 

Thanks.

Was actually already fixed in my devel branch to not do that for remote
devices.

Might make a 1.0.2 release with that change.  Was waiting for awhile...  no
other obvious bugs have popped up quite yet.


-- 
 Edwin Huffstutler     Linux - because reboots are for hardware changes
 ed...@co...   GnuPG Key ID: AE782DC9

[flexbackup-help] bugreport "can't write to /dev/tape" when using remote tape

[raphael d. <ra...@ru...>]

the script (version 1.0.1) checks the existence of the tape device 
locally, although i told it a remote tapedevice

line 2174:
    if (! -w $main::device) {
        push(@main::errors,"Can't write to $main::device");
    }





mfg raphael

Re: [flexbackup-help] > 2 GB Backup question

[Brian B. <bb...@my...>]

I'm using the latest version of SME Server, and during the 
installation/upgrade all partitions are upgraded to EXT3.  That should 
take care of things for you.

Cheers,
BB

PS: Flexbackup is working great for me, Edwin.

Brian Barber
Ottawa, ON   CANADA
brian dot barber at mysun dot com

----- Original Message -----
From: "Cyrus Bharda" <cy...@la...>
Date: Sunday, February 16, 2003 8:07 pm
Subject: Re: [flexbackup-help] > 2 GB Backup question

> Wow first off thank you for your speedy responce!
> 
> :
> : If the SME core utils are from RedHat 7.x it should handle >2GB 
> files just
> : fine - large file support has been around a while.
> :
> 
> That is what I thought, but it is using the ext2 file system, 
> which only has
> a 2 GB file limit or so I have been told as I am a bit off a noob.
> 
> : I'm not sure if the SME setup uses "buffer" or not, but buffer 
> needs a
> : compilation tweak to read/write >2GB files.  If you are just 
> using dd it
> : should be fine.
> :
> 
> When you say there in the paragraph above, do you mean that SME 
> will need
> buffer if I wanted to write a >2GB file to the backup file or 
> write a >2GB
> backup file? Like say I had 3 x 2.3GB files then I would need 
> buffer to be
> able to back them up and that if I had 3 x 1.7GB files to backup 
> on the
> RedHat box TO the share then flexbackup doesnt need buffer as the 
> individualfiles are not >2GB but the total backup file that 
> flexbackup will create
> will be >2GB, right? Sorry for the drawn out explanation, but I am 
> a bit of
> a noob here.
> 
> : Basically any 2GB limits will come from the utilities used in 
> the pipeline
> : - dd/buffer/dum: your case), and not from flexbackup itself.
> :
> 
> I am not sure what this distro uses as it is developed for newbies 
> and is
> all web driven, I click on the backup now button and it just does 
> the rest
> for me, so I will enquire on what pipline is used. How do I find 
> out the
> size limits for the different pipelines used as once I find out which
> pipline is used that will be the next question :-).
> 
> Now I just need to find out if there is any file size limitations 
> on smbfs
> :-)
> 
> Thanks again for your help, it is very much appreciated!!
> 
> Cyrus Bharda
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> flexbackup-help mailing list
> fle...@li...
> https://lists.sourceforge.net/lists/listinfo/flexbackup-help
> 

Re: [flexbackup-help] Version 1.01 and mt setblk in Linux

[Luis C. <ad...@co...>]

Okay here is the error I get:



flexbackup version 1.0.1 (http://flexbackup.sourceforge.net)
/etc/flexbackup.conf syntax OK

|------------------------------------------------------------
| Checking /bin/sh on this machine... bash2
|------------------------------------------------------------
| Logging output to "flexbackup.list.200302171143.log"
| Trying "mt defblksize" instead of "mt setblk"
| Reading from current tape position
|------------------------------------------------------------
At block 134227397.
|------------------------------------------------------------
| dd ibs=32k obs=32k conv=noerror,sync if="/dev/nst0" | cpio -t -v -C 32768
|------------------------------------------------------------
1+0 records in
1+0 records out
cpio: premature end of archive
|------------------------------------------------------------
At block 134227401.
|------------------------------------------------------------


When I change the cpio command to block-size=64 instead of C, then it works:

cpio -t -v --block-size=64


I think it is just my tape is real finicky about blocks.

I guess I will need to do with same with gzip.



----- Original Message -----
From: "Edwin Huffstutler" <ed...@co...>
To: "Luis Cortes" <ad...@co...>
Cc: <fle...@li...>
Sent: Sunday, February 16, 2003 8:37 AM
Subject: Re: [flexbackup-help] Version 1.01 and mt setblk in Linux


>
> [ Luis Cortes wrote: ]
> > Okay, let me clarify my own response.  I believe that for programs like
tar
> > or cpio, the default block size is 512.  When you specify 64 blocks,
>
> Nope.
>
> tar and many others default to 10k.  cpio does default to 512 bytes.  We
> don't use defaults for anything anyway, so it doesn't matter.
>
> > flexbackup thinks it's 1024 * 64.  If you specify 64 blocks for cpio it
> > means 512 * 64.  It seems to me that there is a logic problem somewhere.
Am
> > I right about this?
>
> Nope.
>
> The config file says "Block size (k)" for $blksize, and that's what it
> means.  It's converted for whichever archiver as needed.
>
> Flexbackup sets the flags are all set so units are consistent.  Check the
> manpages and code.
>
>
> tar:
>   -b, --block-size N
>          block size of Nx512 bytes (default N=20)
>
> cpio: (flexbackup uses the -C flag!)
>   -C IO-SIZE, --io-size=IO-SIZE
>         Set the I/O block size to IO-SIZE bytes.
>
> dump:
>   -b blocksize
>              The number of kilobytes per dump record.  Since the IO system
>              slices all requests into chunks of MAXBSIZE (typically 64kB),
it
>              is not possible to use a larger blocksize without having
problems
>              later with restore(8).  Therefore dump will constrain writes
to
>              MAXBSIZE.  The default blocksize is 10.
>
> afio:
>   -b size      Read  or write size-character archive blocks.  Suffices of
>                b,  k,  m  and  g  denote  multiples  of  512,  kilobytes,
>                megabytes  and  gigabytes, respectively.  Defaults to 5120
>                for compatibility with cpio(1).  In  some  cases,  notably
>                when  using  ftape with some tape drives, -b 10k is needed
>                for compatibility.  Note that -b 10k is the default  block
>                size used by tar(1), so it is usually a good choice if the
>                tape setup is known to work with tar(1).
>
> etc..
>
> --
>  Edwin Huffstutler     Linux - because reboots are for hardware changes
>  ed...@co...   GnuPG Key ID: AE782DC9
>
>
>

Re: [flexbackup-help] > 2 GB Backup question

[Cyrus B. <cy...@la...>]

Wow first off thank you for your speedy responce!

:
: If the SME core utils are from RedHat 7.x it should handle >2GB files just
: fine - large file support has been around a while.
:

That is what I thought, but it is using the ext2 file system, which only has
a 2 GB file limit or so I have been told as I am a bit off a noob.

: I'm not sure if the SME setup uses "buffer" or not, but buffer needs a
: compilation tweak to read/write >2GB files.  If you are just using dd it
: should be fine.
:

When you say there in the paragraph above, do you mean that SME will need
buffer if I wanted to write a >2GB file to the backup file or write a >2GB
backup file? Like say I had 3 x 2.3GB files then I would need buffer to be
able to back them up and that if I had 3 x 1.7GB files to backup on the
RedHat box TO the share then flexbackup doesnt need buffer as the individual
files are not >2GB but the total backup file that flexbackup will create
will be >2GB, right? Sorry for the drawn out explanation, but I am a bit of
a noob here.

: Basically any 2GB limits will come from the utilities used in the pipeline
: - dd/buffer/dump/afio/whatever, or in the underlying filesystem (smbfs in
: your case), and not from flexbackup itself.
:

I am not sure what this distro uses as it is developed for newbies and is
all web driven, I click on the backup now button and it just does the rest
for me, so I will enquire on what pipline is used. How do I find out the
size limits for the different pipelines used as once I find out which
pipline is used that will be the next question :-).

Now I just need to find out if there is any file size limitations on smbfs
:-)

Thanks again for your help, it is very much appreciated!!

Cyrus Bharda

Re: [flexbackup-help] > 2 GB Backup question

[Edwin H. <ed...@co...>]

[ Cyrus Bharda wrote: ]
> So here are our questions:
> 
> 1. How big can files be created by flexbackup IF it is to a Windows NTFS share?

The limitation would be with smbfs if anything.  I have no clue what the
filesize limits are for it.  It might be your limiting factor.

> 2. Can a file that is >2GB that was created by flexbackup to a Windows
> NTFS share be restored without running into the 2GB limit on the RedHat
> Box?

If the SME core utils are from RedHat 7.x it should handle >2GB files just
fine - large file support has been around a while.

I'm not sure if the SME setup uses "buffer" or not, but buffer needs a
compilation tweak to read/write >2GB files.  If you are just using dd it
should be fine.

Basically any 2GB limits will come from the utilities used in the pipeline
- dd/buffer/dump/afio/whatever, or in the underlying filesystem (smbfs in
your case), and not from flexbackup itself.


-- 
 Edwin Huffstutler     Linux - because reboots are for hardware changes
 ed...@co...   GnuPG Key ID: AE782DC9

[flexbackup-help] > 2 GB Backup question

[Cyrus B. <cy...@la...>]

Hello all,

I use a modified version of RedHat 7.2 called SME, (was e-smith =
www.e-smith.org) and at the moment we are having some questions about =
flexbackup that no one on the e-smith list seems to be able to answer =
and hoping that someone here might.

It all has to do with using flexbackup.

Now instead of using a tape drive unit, we have configured flexbackup to =
use a shared folder on a windows 2000 (NTFS) computer to store the dump, =
the howto's are here:

Backup:
http://myezserver.com/downloads/mitel/howto/flexbackup-to-disk-howto.html=


Restore:
http://www.e-smith.org/docs/howto/contrib/flexbackup-restore-from-disk-ho=
wto.html

Now that all works great, but what happens when the actual file that is =
dumped/copied to the file share is larger than 2GB, now not a single =
file can be larger than 2GB on the RedHat box, because of the file =
system so we're not really worried about the size of the files being =
backed up, just the size of the backup file itself.

There is another backup function we could use and that is the "Backup to =
Desktop" feature which basically takes certain directories from the =
server and tars them and then copies that file to your desktop, but the =
problem is when we go to restore from that file, if it is >2GB then =
basically it stuffs up because it apparently it try's to create a temp =
file on the server and when it hits the 2GB file system limit it chokes.

That's why using flexbackup to a disk/file share seems so appropriate as =
then we get to use this great package for backing up and restoring and =
don't have to shell out heaps of cash for a tape drive, as most people =
have an abundance of spare hard drive space!

So here are our questions:

1. How big can files be created by flexbackup IF it is to a Windows NTFS =
share?

2. Can a file that is >2GB that was created by flexbackup to a Windows =
NTFS share be restored without running into the 2GB limit on the RedHat =
Box?

For more information and to see what other things we have discussed =
please view our discussion at:

http://www.e-smith.org/bboard/read.php?f=3D1&i=3D24288&t=3D24078&v=3Df

Thank you for any help that is provided!!

Cyrus Bharda
IT Support Officer
Langs Building Supplies
2 Elliot Drive
Yatala  QLD  4207
Australia

Ph: +61 7 3382 5200
Fx: +61 7 3807 6400
Em: cy...@la...
www: www.langs.net.au

Disclaimer:
This email and any files transmitted with it are confidential and =
intended solely for the use of the individual or entity to whom they are =
addressed. If you have received this email in error please notify the =
system manager. This message contains confidential information and is =
intended only for the individual named. If you are not the named =
addressee you should not disseminate, distribute or copy this e-mail. =
Please notify the sender immediately by e-mail if you have received this =
e-mail by mistake and delete this e-mail from your system.

Computer viruses can be transmitted via email. The recipient should =
check this email and any attachments for the presence of viruses. Langs =
Building Supplies accepts no liability for any damage caused by any =
virus transmitted by this email. E-mail transmission cannot be =
guaranteed to be secure or error-free as information could be =
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or =
contain viruses. The sender therefore does not accept liability for any =
errors or omissions in the contents of this message, which arise as a =
result of e-mail transmission.

Langs Building Supplies accepts no liability for the content of this =
email, or for the consequences of any actions taken on the basis of the =
information provided, unless that information is subsequently confirmed =
in writing. If you are not the intended recipient you are notified that =
disclosing, copying, distributing or taking any action in reliance on =
the contents of this information is strictly prohibited.=20

Any views or opinions presented in this email are solely those of the =
author and do not necessarily represent those of Langs Building =
Supplies. Employees of Langs Building Supplies are expressly required =
not to make defamatory statements and not to infringe or authorize any =
infringement of copyright or any other legal right by email =
communications. Any such communication is contrary to company policy and =
outside the scope of the employment of the individual concerned. The =
company will not accept any liability in respect of such communication, =
and the employee responsible will be personally liable for any damages =
or other liability arising.

Langs Building Supplies, 2 Elliot Drive, Yatala, Australia, =
www.langs.net.au

Re: [flexbackup-help] Version 1.01 and mt setblk in Linux

[Edwin H. <ed...@co...>]

[ Luis Cortes wrote: ]
> Okay, let me clarify my own response.  I believe that for programs like tar
> or cpio, the default block size is 512.  When you specify 64 blocks,

Nope.

tar and many others default to 10k.  cpio does default to 512 bytes.  We
don't use defaults for anything anyway, so it doesn't matter.

> flexbackup thinks it's 1024 * 64.  If you specify 64 blocks for cpio it
> means 512 * 64.  It seems to me that there is a logic problem somewhere.  Am
> I right about this?

Nope.

The config file says "Block size (k)" for $blksize, and that's what it
means.  It's converted for whichever archiver as needed.

Flexbackup sets the flags are all set so units are consistent.  Check the
manpages and code.


tar:
  -b, --block-size N
         block size of Nx512 bytes (default N=20)

cpio: (flexbackup uses the -C flag!)
  -C IO-SIZE, --io-size=IO-SIZE
        Set the I/O block size to IO-SIZE bytes.

dump:
  -b blocksize
             The number of kilobytes per dump record.  Since the IO system
             slices all requests into chunks of MAXBSIZE (typically 64kB), it
             is not possible to use a larger blocksize without having problems
             later with restore(8).  Therefore dump will constrain writes to
             MAXBSIZE.  The default blocksize is 10.

afio:
  -b size      Read  or write size-character archive blocks.  Suffices of
               b,  k,  m  and  g  denote  multiples  of  512,  kilobytes,
               megabytes  and  gigabytes, respectively.  Defaults to 5120
               for compatibility with cpio(1).  In  some  cases,  notably
               when  using  ftape with some tape drives, -b 10k is needed
               for compatibility.  Note that -b 10k is the default  block
               size used by tar(1), so it is usually a good choice if the
               tape setup is known to work with tar(1).

etc..

-- 
 Edwin Huffstutler     Linux - because reboots are for hardware changes
 ed...@co...   GnuPG Key ID: AE782DC9

Re: [flexbackup-help] Version 1.01 and mt setblk in Linux

[Luis C. <ad...@co...>]

Okay, let me clarify my own response.  I believe that for programs like tar
or cpio, the default block size is 512.  When you specify 64 blocks,
flexbackup thinks it's 1024 * 64.  If you specify 64 blocks for cpio it
means 512 * 64.  It seems to me that there is a logic problem somewhere.  Am
I right about this?



----- Original Message -----
From: "Luis Cortes" <ad...@co...>
To: <fle...@li...>
Sent: Saturday, February 15, 2003 8:16 PM
Subject: Re: [flexbackup-help] Version 1.01 and mt setblk in Linux


> I have been having a similar problem.  I haven't tried this fix yet, but I
> hope this does it for me.
>
> My problem is that I set the default to 64 blocks.  I am guessing that the
> default block size is 512 bytes.  But when I try to list anything, it
either
> says something about the first block all null or that the archive is not
> correctly terminated and false to list anything.
>
>
>
> ----- Original Message -----
> From: "Edwin Huffstutler" <ed...@co...>
> To: "Douglas Bollinger" <dc...@sd...>
> Cc: <fle...@li...>
> Sent: Saturday, February 15, 2003 2:22 PM
> Subject: Re: [flexbackup-help] Version 1.01 and mt setblk in Linux
>
>
> >
> > [ Douglas Bollinger wrote: ]
> > > I've been using the flexbackup script for a long time.  Love it!
> >
> > Thanks!
> >
> > > In the latest update, my system has been having trouble,
> >
> > (Strange, as recent changes haven't touched mt blocksize that I recall)
> >
> > > I need to have blocks set to 512, but the script takes the 512*1024.
> This
> > > doesn't work for me.  Output of the flexbackup error:
> > >
> > > Neither of these commands worked:
> > >   mt -f /dev/nst0 setblk 524288
> > >   mt -f /dev/nst0 defblksize 524288
> > >
> > > But, if I do this manually:
> > >
> > > rodan:~# mt -f /dev/nst0 setblk 524288
> > > mt: /dev/nst0: Input/output error
> > > rodan:~# mt -f /dev/nst0 setblk 512
> > > rodan:~#
> > >
> > > You can see, I need the blocks in k's, not multiplied by 1024.  In the
> > > script I had to change line 2251:
> > >
> > > #   $main::mt_blksize = $cfg::blksize * 1024;
> > >     $main::mt_blksize = $cfg::blksize;
> > >
> > > And now it works.
> >
> >
> > I bet you can set $blksize=1 and you'd be fine.  A multiple of the
> > hardware block size is OK in my experience and testing.
> >
> > I think the problem you ran into is that 512k is huge and over a limit
> > somewhere.
> >
> > Also, does $mt_var_blksize='true' work for you?  That's more often
> > recommended and is easier than trying to find the right blocksize for
your
> > tape drive.
> >
> > At any rate, please report back.  I may need to adjust so non-multiples
of
> > 1024 bytes can be used.
> >
> >
> > Thanks,
> >   -Edwin
> >
> >
> > --
> >  Edwin Huffstutler     Linux - because reboots are for hardware changes
> >  ed...@co...   GnuPG Key ID: AE782DC9
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > flexbackup-help mailing list
> > fle...@li...
> > https://lists.sourceforge.net/lists/listinfo/flexbackup-help
> >
> >
> >
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> flexbackup-help mailing list
> fle...@li...
> https://lists.sourceforge.net/lists/listinfo/flexbackup-help
>
>
>

Re: [flexbackup-help] Version 1.01 and mt setblk in Linux

[Luis C. <ad...@co...>]

I have been having a similar problem.  I haven't tried this fix yet, but I
hope this does it for me.

My problem is that I set the default to 64 blocks.  I am guessing that the
default block size is 512 bytes.  But when I try to list anything, it either
says something about the first block all null or that the archive is not
correctly terminated and false to list anything.



----- Original Message -----
From: "Edwin Huffstutler" <ed...@co...>
To: "Douglas Bollinger" <dc...@sd...>
Cc: <fle...@li...>
Sent: Saturday, February 15, 2003 2:22 PM
Subject: Re: [flexbackup-help] Version 1.01 and mt setblk in Linux


>
> [ Douglas Bollinger wrote: ]
> > I've been using the flexbackup script for a long time.  Love it!
>
> Thanks!
>
> > In the latest update, my system has been having trouble,
>
> (Strange, as recent changes haven't touched mt blocksize that I recall)
>
> > I need to have blocks set to 512, but the script takes the 512*1024.
This
> > doesn't work for me.  Output of the flexbackup error:
> >
> > Neither of these commands worked:
> >   mt -f /dev/nst0 setblk 524288
> >   mt -f /dev/nst0 defblksize 524288
> >
> > But, if I do this manually:
> >
> > rodan:~# mt -f /dev/nst0 setblk 524288
> > mt: /dev/nst0: Input/output error
> > rodan:~# mt -f /dev/nst0 setblk 512
> > rodan:~#
> >
> > You can see, I need the blocks in k's, not multiplied by 1024.  In the
> > script I had to change line 2251:
> >
> > #   $main::mt_blksize = $cfg::blksize * 1024;
> >     $main::mt_blksize = $cfg::blksize;
> >
> > And now it works.
>
>
> I bet you can set $blksize=1 and you'd be fine.  A multiple of the
> hardware block size is OK in my experience and testing.
>
> I think the problem you ran into is that 512k is huge and over a limit
> somewhere.
>
> Also, does $mt_var_blksize='true' work for you?  That's more often
> recommended and is easier than trying to find the right blocksize for your
> tape drive.
>
> At any rate, please report back.  I may need to adjust so non-multiples of
> 1024 bytes can be used.
>
>
> Thanks,
>   -Edwin
>
>
> --
>  Edwin Huffstutler     Linux - because reboots are for hardware changes
>  ed...@co...   GnuPG Key ID: AE782DC9
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> flexbackup-help mailing list
> fle...@li...
> https://lists.sourceforge.net/lists/listinfo/flexbackup-help
>
>
>

Re: [flexbackup-help] Version 1.01 and mt setblk in Linux

[Edwin H. <ed...@co...>]

[ Douglas Bollinger wrote: ]
> I've been using the flexbackup script for a long time.  Love it!

Thanks!

> In the latest update, my system has been having trouble,

(Strange, as recent changes haven't touched mt blocksize that I recall)

> I need to have blocks set to 512, but the script takes the 512*1024.  This
> doesn't work for me.  Output of the flexbackup error:
> 
> Neither of these commands worked:
>   mt -f /dev/nst0 setblk 524288
>   mt -f /dev/nst0 defblksize 524288
> 
> But, if I do this manually:
> 
> rodan:~# mt -f /dev/nst0 setblk 524288
> mt: /dev/nst0: Input/output error
> rodan:~# mt -f /dev/nst0 setblk 512   
> rodan:~#
> 
> You can see, I need the blocks in k's, not multiplied by 1024.  In the
> script I had to change line 2251:
> 
> #   $main::mt_blksize = $cfg::blksize * 1024;
>     $main::mt_blksize = $cfg::blksize;
> 
> And now it works.


I bet you can set $blksize=1 and you'd be fine.  A multiple of the
hardware block size is OK in my experience and testing.  

I think the problem you ran into is that 512k is huge and over a limit
somewhere.

Also, does $mt_var_blksize='true' work for you?  That's more often
recommended and is easier than trying to find the right blocksize for your
tape drive.

At any rate, please report back.  I may need to adjust so non-multiples of
1024 bytes can be used.


Thanks, 
  -Edwin


-- 
 Edwin Huffstutler     Linux - because reboots are for hardware changes
 ed...@co...   GnuPG Key ID: AE782DC9

[flexbackup-help] Version 1.01 and mt setblk in Linux

[Douglas B. <dc...@sd...>]

I've been using the flexbackup script for a long time.  Love it!

In the latest update, my system has been having trouble,

I need to have blocks set to 512, but the script takes the 512*1024.  This
doesn't work for me.  Output of the flexbackup error:

Neither of these commands worked:
  mt -f /dev/nst0 setblk 524288
  mt -f /dev/nst0 defblksize 524288

But, if I do this manually:

rodan:~# mt -f /dev/nst0 setblk 524288
mt: /dev/nst0: Input/output error
rodan:~# mt -f /dev/nst0 setblk 512   
rodan:~#

You can see, I need the blocks in k's, not multiplied by 1024.  In the
script I had to change line 2251:

#   $main::mt_blksize = $cfg::blksize * 1024;
    $main::mt_blksize = $cfg::blksize;

And now it works.

I'm using Debian Woody with a IDE tape drive run through SCSI emulation.

-- 
You can rent this space for only $5 a week.

Re: [flexbackup-help] option -newtape not working

[Edwin H. <ed...@co...>]

[ Allori Lorenzo wrote: ]
> Dear Group,
> 
> i wanted to erase a tape making an index to it but it does not work.
> 
> i do:
> 
> # flexbackup -newtape
> 
> it takes a very long time do do it but it does it.
> 
> # flexbackup -fs /home/pippo
> 
> it says my tape has no index and so i have to format it with -newtape.
> 
> What do i have to do?

Does it work without the index header, or are you having a more generic
tape problem?

Try a sequence like the following:
(may want to use a couple smaller dirs first rather than your home)

flexbackup -erase -fs /home/pippo -d indexes=false 
flexbackup -fs <some other dir> -d indexes=false 

flexbackup -list         ( make this lists /home/pippo )
flexbackup -list -num 1  ( make sure this lists the other dir )


 -Edwin

-- 
 Edwin Huffstutler     Linux - because reboots are for hardware changes
 ed...@co...   GnuPG Key ID: AE782DC9

[flexbackup-help] option -newtape not working

[Allori L. <lla...@sy...>]

Dear Group,

i wanted to erase a tape making an index to it but it does not work.

i do:

# flexbackup -newtape

it takes a very long time do do it but it does it.

# flexbackup -fs /home/pippo

it says my tape has no index and so i have to format it with -newtape.

What do i have to do?

Best,

Lorenzo


Lorenzo Allori
Assistant to Network Services Coordinator
Office: +390555031355
Mobile: +393398612411
Syracuse University Florence
<lla...@sy...>

Re: [flexbackup-help] Logging levels

[Edwin H. <ed...@co...>]

[ Dav...@cs... wrote: ]
> Hi all,
> 
> I am using flexbackup successfully but would like to reduce the logging
> output verbosity.
> 
> Is there an option to do this in flexbackup?

If you set $verbose='false' (or use -d verbose=false on the command line),
it will turn off some of the output from the archive backend.

Try that first and see if that's what you are looking for.

I don't have a mechanism to turn what remains after that... might be an
idea for the future.

(Of course "flexbackup [args] > /dev/null" works :). You'll have the log
file to see what happened... but that's not the answer you wanted I'm sure)


-- 
 Edwin Huffstutler     Linux - because reboots are for hardware changes
 ed...@co...   GnuPG Key ID: AE782DC9

RE: [flexbackup-help] Logging levels

[John R. <jo...@re...>]

[ On Wednesday, February 12, Dav...@cs... wrote: ]
> Hi John
> 
> Im using tar.  
> 
> I assume that the program is using option v for tar?
> 
> Can I turn this off?
> 
> Thanks John

Yes, actually. Set

$verbose = 'false';

in your flexbackup.conf file. I didn't know that this was a config knob myself
until I UTSL'ed ("use the source luke" :). That ought to turn off echoing every
single file that is archived. However, there are not specific "levels" of logs
that the script itself prints that can be turned on/off.

-Jr

-- 
John & Jennifer Reynolds  jo...@re...  http://www.reynoldsnet.org/
Sr. Component Design Engineer, ICG, Intel Corp.    jre...@se...
Running FreeBSD since 2.1.5-RELEASE.               FreeBSD: The Power to Serve!
"Unix is user friendly, it's just particular about the friends it chooses."

[flexbackup-help] Logging levels

[<Dav...@cs...>]

Hi all,

I am using flexbackup successfully but would like to reduce the logging
output verbosity.

Is there an option to do this in flexbackup?

Thanks in advance

David

Re: [flexbackup-help] Problems using sudo

[Edwin H. <ed...@co...>]

[ Markus Schaub wrote: ]
> The flexbackup setup with sudo from the FAQ does not work as described. I
> had to set "Defaults:backupuser !authenticate" ind /etc/sudoers to turn off
> the password prompt (thought that NOPASSWD should do it, but for me it
> doesn't).

I don't need the Defaults: line for this to work, perhaps it's a sudo
difference?  I have sudo-1.6.6.

> Second, "$path{'dump'} = 'sudo -u backup dump';" (outcommented example from
> flexbackup.conf) gives an error ("sudo -u not found in $PATH"), so it is not
> possible, to run the command as !root.

Common case is to use $path{'dump'} = 'sudo dump', since dump needs root to
run.

The -u is for possibly running the command as non-root AND not the current
user, I'm not sure that's what you wanted, is it?  (it does have a buglet
you found with the path-checking which I'll fix)

I'll clean up the config comment and the faq for this so it's more clear.
(You don't even need to set $remoteuser for the common case.)


-- 
 Edwin Huffstutler     Linux - because reboots are for hardware changes
 ed...@co...   GnuPG Key ID: AE782DC9

Re: [flexbackup-help] Problems using sudo

[John R. <jo...@re...>]

[ On Tuesday, February 11, Markus Schaub wrote: ]
> Hi list,
> 
> The flexbackup setup with sudo from the FAQ does not work as described. I
> had to set "Defaults:backupuser !authenticate" ind /etc/sudoers to turn off
> the password prompt (thought that NOPASSWD should do it, but for me it
> doesn't).
> Second, "$path{'dump'} = 'sudo -u backup dump';" (outcommented example from
> flexbackup.conf) gives an error ("sudo -u not found in $PATH"), so it is not
> possible, to run the command as !root.

I think you need to send the actual bits of your config file and the actual
screen output when trying to do a backup. The explanations above are too
unclear to help at this point. Send us the real unedited error messages and
screen text.

-Jr

-- 
John & Jennifer Reynolds  jo...@re...  http://www.reynoldsnet.org/
Sr. Component Design Engineer, ICG, Intel Corp.    jre...@se...
Running FreeBSD since 2.1.5-RELEASE.               FreeBSD: The Power to Serve!
"Unix is user friendly, it's just particular about the friends it chooses."

[flexbackup-help] Problems using sudo

[Markus S. <mai...@ma...>]

Hi list,

The flexbackup setup with sudo from the FAQ does not work as described. I
had to set "Defaults:backupuser !authenticate" ind /etc/sudoers to turn off
the password prompt (thought that NOPASSWD should do it, but for me it
doesn't).
Second, "$path{'dump'} = 'sudo -u backup dump';" (outcommented example from
flexbackup.conf) gives an error ("sudo -u not found in $PATH"), so it is not
possible, to run the command as !root.

Markus

Re: [flexbackup-help] ahhh.. tar option not working.. help?

[Edwin H. <ed...@co...>]

[ Jamie Harper wrote: ]
> I'm trying to implement the newest version of flexbackup to backup my 
> Solaris Machines to a linux machine. I've installed and configured it, but 
> it's given me problems with every archive type. My preference would be tar 
> since I'm backing up to a hard drive, not a tape drive, but zip would also 
> work fine for me. I've included what I get when I try to backup a simple 
> small directory on a remote Solaris machine.
> 
> The error seems to be saying that tar doesn't have an -a flag, but I don't 
> seem to see one being asked for in the command line, but then again this 
> command is too complicated for me to fully understand.
> 
> I'll also include my flexbackup.conf at the end of this message so you can 
> see how I've got it configured. Any assistance would be greatly appreciated.


If you want to use "tar" as the archiver, you need to use GNU tar.


Try "pax" if you don't want to install anything additional on the Solaris
box - it should be there, and should be commandline compatible across
platforms.


-- 
 Edwin Huffstutler     Linux - because reboots are for hardware changes
 ed...@co...   GnuPG Key ID: AE782DC9

[flexbackup-help] ahhh.. tar option not working.. help?

[Jamie H. <ha...@de...>]

Hi group,

I'm trying to implement the newest version of flexbackup to backup my 
Solaris Machines to a linux machine. I've installed and configured it, but 
it's given me problems with every archive type. My preference would be tar 
since I'm backing up to a hard drive, not a tape drive, but zip would also 
work fine for me. I've included what I get when I try to backup a simple 
small directory on a remote Solaris machine.

The error seems to be saying that tar doesn't have an -a flag, but I don't 
seem to see one being asked for in the command line, but then again this 
command is too complicated for me to fully understand.

I'll also include my flexbackup.conf at the end of this message so you can 
see how I've got it configured. Any assistance would be greatly appreciated.

Jamie


[root@interpole flexbackup-1.0.1]# flexbackup -fs 
earth.web-hosting.com:/home2/harper

flexbackup version 1.0.1 (http://flexbackup.sourceforge.net)
/etc/flexbackup.conf syntax OK

|------------------------------------------------------------
| Checking /bin/sh on this machine... bash2
| Checking shell on earth.web-hosting.com... ro...@ea...'s 
password:
bash2
| Checking for required programs on host earth.web-hosting.com... 
ro...@ea...'s password:
Ok
|------------------------------------------------------------
| Doing level 0 backup of earth.web-hosting.com:/home2/harper using tar
| Found directory index key 200302101949
|------------------------------------------------------------
| Backup of: earth.web-hosting.com:/home2/harper
| Date of this level 0 backup: Mon Feb 10 20:25:03 2003
| Date of last level 0 backup: the epoch
|------------------------------------------------------------
| ssh earth.web-hosting.com 'cd "/home2/harper" && find . -xdev -depth !
|   -regex ".*/[Cc]ache/.*" ! -regex ".*~"$ -print0 | tar --create --null
|   --files-from=- --same-permissions --same-order --no-recursion --totals
|   --label "level 0 earth.web-hosting.com:/home2/harper Mon Feb 10
|   20:25:03 2003 tar from interpole.interpole.com" --verbose --sparse
|   --atime-preserve -R -b 20 --file - ; x=(${PIPESTATUS[@]}); i=0; while [
|   $i -lt ${#x[@]} ]; do [ ${x[$i]} -eq 0 ] || exit ${x[$i]}; i=$(($i+1));
|   done' | dd ibs=10k obs=10k conv=noerror
|   of="/opt/earth.web-hosting.com-home2-harper.0.tar"
|------------------------------------------------------------
ro...@ea...'s password:
tar: a: unknown option
Usage: tar {txruc}[vfbFXhiBEelmopwnq[0-7]] [-k size] [tapefile] [blocksize] 
[exclude-file] [-I include-file] files ...
0+0 records in
0+0 records out

ERROR from backup, exiting
offending command(s):
ssh earth.web-hosting.com 'cd "/home2/harper" && find . -xdev -depth ! 
-regex ".*/[Cc]ache/.*" ! -regex ".*~"$ -print0 | tar --create --null 
--files-from=- --same-permissions --same-order --no-recursion --totals 
--label "level 0 earth.web-hosting.com:/home2/harper Mon Feb 10 20:25:03 
2003 tar from interpole.interpole.com" --verbose --sparse --atime-preserve 
-R -b 20 --file - ; x=(${PIPESTATUS[@]}); i=0; while [ $i -lt ${#x[@]} ]; 
do [ ${x[$i]} -eq 0 ] || exit ${x[$i]}; i=$(($i+1)); done' | dd ibs=10k 
obs=10k conv=noerror of="/opt/earth.web-hosting.com-home2-harper.0.tar"
[root@interpole flexbackup-1.0.1]#


---------------------------------------------------------------------------------------------------------------------------------------------------


# -*-Mode: perl-*-
# ----------------------------------------------------------------------
# Flexbackup configuration file
#
# $Id: flexbackup.conf,v 1.64 2003/01/21 15:43:17 edwinh Exp $
# $Name: v1_0_1 $
#
# ----------------------------------------------------------------------
# General configuration section

# Archive type?  afio, dump, tar, cpio, star, pax, zip
$type = 'tar';

# List the directories you wish to dump when 'all' is given
# Just a simple space-separated list
# Remote filesystems should denoted as 'host:dir'
#
# Example:
#   $filesystems[0] = '/ /usr /home machine1:/usr machine2:/home';
#
# The array index is a tape number. If you want an 'all' level 0 backup to
# span multiple tapes, add more lines with different array indices. You will
# be prompted for tape change in between.
#
$filesystems[0] = '/home';

# Compression
$compress = 'false'; # one of false/gzip/bzip2/zip/compress/hardware
$compr_level = '4'; # compression level (1-9) (for gzip/bzip2/zip)

# Buffering / padding
$buffer = 'false';   # 'false' or 'buffer', to use buffer program to help 
streaming
$buffer_megs = '10';  # buffer memory size (in megabytes)
$pad_blocks = 'true'; # true to pad blocks to blocksize (devices only, not 
used when
                       # archiving to files)

# Device to backup to - non-rewinding version please!
#
# Examples:
#    Linux SCSI: /dev/nst0       Linux IDE: /dev/nht0
#    Linux ftape: /dev/nqft0     FreeBSD SCSI: /dev/nrsa0
#
# If a directory, will archive to files in that directory rather than a device
# If "host:/dev/tapedevice", will use remote tape drive via rsh/ssh
#
$device = '/opt';

# Block size (k) to use
# Default is 10 for most things.  Some tape drives need 32 or 64.
# Set to '0' to disable all blocking
$blksize = '10';

# True to use "variable" block size for the tape device (mt setblk 0)
# If false, will use the $blksize parameter above. All non-mt commands
# will still use $blksize regardless of this value
$mt_var_blksize = 'true';

# Other global flags
$remoteshell = 'ssh'; # command for remote shell (rsh/ssh/ssh2)
$remoteuser = '';     # if non-null, username for remote shell
$verbose = 'true';    # echo each file?
$sparse = 'true';     # handle sparse files?
$indexes = 'true';    # false to turn off all table-of-contents support

# If backing up to files, use static filenames - no date stamp
# (same level backup of same directory will overwrite old backups)
$staticfiles = 'true';

# True to try and preserve file access times during backup, if the selected
# archive program can do so. Note that if this is true, -cnewer checks (file
# permission/status changes only, not content) are turned off when deciding
# which files to archive on the local system.
$atime_preserve = 'true';

# Span across filesytems? ("dump" will ignore this option)
# Set to "false" (don't) , "local" (all but nfs/smbfs), or "all" (everything)
$traverse_fs = 'false';

# Exclude files that match these *regular expressions* (not shell wildcards)
# from the backups (no affect on 'dump' archives). You can list more than one,
# just keep incrementing the index in the brackets for each.  Also, strip off
# leading directories (the filesystem specs above or the "-fs" flag).
# Matches paths, not filenames, so put .* on the front/back as needed.
# Comment these out to exclude nothing.
$exclude_expr[0] = '.*/[Cc]ache/.*';
$exclude_expr[1] = '.*~$';

# If true (default), level zero "all" assumes you want to erase and use
# a new tape. If false, level zero "all" appends like all other backups.
# If not doing 'all', backups won't erase the tape first, unless you use
# "-erase" on the commandline.
$erase_tape_all_level_zero = 'true';

# Set this to "true" to make erase operations just call "mt rewind" - not
# "mt rewind' followed by "mt erase".  (For some tape drives, erase takes
# hours rather than seconds or is otherwise undesirable)
$erase_rewind_only = 'true';

# ----------------------------------------------------------------------
# Log/stamp files, path for temporary files

$logdir = "/var/log/flexbackup";   # directory for log files
$stampdir = "/var/lib/flexbackup"; # directory for backup timestamps
$index = "$stampdir/index";        # DB filename for tape indexes
$comp_log = "false";                # compress log? 
false/gzip/bzip2/compress/zip
$staticlogs = "false";             # static log filenames w/ no date stamp
$prefix = "";                      # log files will start with this prefix
$sprefix = "";                     # stamp files will start with this prefix
$tmpdir = "/tmp";                  # used for temporary refdate files, etc
$keyfile = "00-index-key";         # filename for keyfile if archiving to dir

# ----------------------------------------------------------------------
# Parameters for 'afio' only

# File extensions that should not be compressed (seperate with spaces)
$afio_nocompress_types = 'mp3 MP3 Z z gz gif zip ZIP lha jpeg jpg JPG taz 
tgz deb rpm bz2';

# True to show block numbers
$afio_echo_block = 'false';

# Files less than this size (kilobytes) won't be compressed
$afio_compress_threshold = '3';

# Maximum amount of memory (megabytes) to use for temporary storage of
# compression results.  If a compressed file is bigger than this, compression
# will have to run twice on the file (see manpage).
$afio_compress_cache_size = '2';

# ----------------------------------------------------------------------
# Parameters for 'tar' only

# True to show record numbers
$tar_echo_record_num = 'true';

# ----------------------------------------------------------------------
# Parameters for 'cpio' only

# Format of cpio archive
$cpio_format = 'newc';

# ----------------------------------------------------------------------
# Parameters for 'dump' only

# Estimated tape size (in kilobytes). This number doesn't really do much
# but help 'dump' get size estimates if set to zero uses 'dump -a'
$dump_length = '0';

# True to use /etc/dumpdates (could mess things up if you dump subdirectories
# of mount points).  False to use flexbackup's timestamps.
$dump_use_dumpdates = 'false';

# ----------------------------------------------------------------------
# Parameters for 'star' only

# Use fifo (buffering)? (you probably want to set $buffer=false above if so)
$star_fifo = 'true';

# Handle ACLs?
$star_acl = 'true';

# Format of star archive
$star_format = 'exustar';

# True to show block numbers
$star_echo_block_num = 'false';

# ----------------------------------------------------------------------
# Parameters for 'pax' only

# Format of pax archive
$pax_format = 'ustar';

# ----------------------------------------------------------------------
# Parameters for 'zip' only

# File extensions that should not be compressed (seperate with spaces)
$zip_nocompress_types = 'mp3 MP3 Z z gz gif zip ZIP lha jpeg jpg JPG taz 
tgz deb rpm bz2';

# ----------------------------------------------------------------------
# Paths to commands. Default will look for them in $PATH. Set if
# you want to set them explicitly.  You can use full paths or just
# change command names.
#
# Example: If GNU tar is called "gtar" on your system:
#   $path{'tar'} = 'gtar';
#
# Or can be used to "sudo" certain commands. Examples:
#    $path{'find'} = 'sudo find';
#    $path{'dump'} = 'sudo -u backup dump';
#


######################################################################
# Leave '1;' on the the next line - for perl 'require'
1;