Re: Win32 client (was: Re: Amanda GUI)
> If not, it is possible that my employer would be willing to pay > someone to bring it sufficiently up-to-date that it actually works. > (Since the backup image is created OK, we are expecting that this > ought not be a huge amount of work for someone with a reasonable > ability & willingness to develop in/for the win32 environment.) It > would be Nice(tm) if, aas an additional result, it would be possible > to do an amrecover from the UNIX side against a backup created in the > win32 side and have a reasonable expectation that some arbitrary set > of the files could be restored. It's actually rather much a pain, although this is someone who's primarily a unix geek talking who only has marginal experience in the MS world. (and most of it under win 3.1). This is assuming you don't want to break the unix-philosophy driving much of amanda's design. I've actually gotten everything to build in client-src natively under Windows (using visual studio .NET and a few hacked up Makefiles, no configure), but not actually working. I think all that's really left is getting the event driver working and figuring out how to interact with some backup program, although each time I get someting working, I've found something else that needs attention. Unfortunately, things like select() don't work the same way under Windows as they do under Unix (you can't select on a file descriptor, only sockets, for example). For the software required to backup, it would be nice if amanda stored things in the microsoft tape format used by the "backup" program that ships with the NT Track, that is: http://www.layton-graphics.com/mtf/MTF_100a.PDF I don't think "backup" can dump to stdout. However, in theory this would allow for bare-metal restores if you have the dump image. I haven't really considered amrecover yet, figuring that in a pinch someone could use microsoft's backup utility over samba to a big disk on the unix side if something was generating dump imaages in MTF. Also, for people just wanting to get at files in the backups without having to touch NT: http://www.layton-graphics.com/mtf/ would mitigate that (I think; I've never tried it). Certainly WinTar (or whatever) would be another reasoable alternative. all of my work was against the 2.5.0 track. (top of the cvs repository) which has significantly different innards for the clients, but should theoretically be compatible with 2.4 servers. (never tried). I was avoiding all the glue packages lke cygwin or mingw for at least the client portion to try to simplify the world for would-be users. I've touched this maybe a few hours recently (it still builds) but not with any significance since last March or so. One of these days, I'll get back to it. -Todd
Re: Win32 client (was: Re: Amanda GUI)
On Wed, Nov 05, 2003 at 05:58:14PM +0100, JC Simonetti wrote: > [...] > > > > In addition to "cygwin", which has a large overhead, > > the same project has another package called, I think, > > "mingw". Unlike cygwin, which requires a cygwin dll > > to be on the system, and is GPL'ed, mingw compiles > > are standalone and can be used to generate non-GPL'ed > > executables (I think I'm correct there, net lawyers will > > complain if I'm not :) > > > > I've not, but I wonder if anyone has tried to get a > > set of amanda client executables built under mingw > > and using the previously mentioned tarNT? > > > > BTW, the mingw package would be another way to build > > the selfcheck/true executable without a full IDE. > > Amanda Win32 Sourceforge project IS based on a mingw solution. Ahh, nevermind :) -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Win32 client (was: Re: Amanda GUI)
[...] > > In addition to "cygwin", which has a large overhead, > the same project has another package called, I think, > "mingw". Unlike cygwin, which requires a cygwin dll > to be on the system, and is GPL'ed, mingw compiles > are standalone and can be used to generate non-GPL'ed > executables (I think I'm correct there, net lawyers will > complain if I'm not :) > > I've not, but I wonder if anyone has tried to get a > set of amanda client executables built under mingw > and using the previously mentioned tarNT? > > BTW, the mingw package would be another way to build > the selfcheck/true executable without a full IDE. Amanda Win32 Sourceforge project IS based on a mingw solution.
Re: Win32 client (was: Re: Amanda GUI)
On Wed, Nov 05, 2003 at 02:36:46PM +0100, JC Simonetti wrote: > On Wed, 5 Nov 2003 04:52:33 -0800 > David Wolfskill <[EMAIL PROTECTED]> wrote: > > I wasn't aware that the Win32 environment was sufficiently "special" > > that tar archives were unportable between that and normal (UNIX) > > environments. > It's the reason of the existence of the WinTar software :) Oh. I had (perhaps naively) thought that it was merely a win32/NT/...? port of a more standard tar > > Well, I suppose it might be, if it were small enough to fit in the > > available space on the Windows box, and if someone who had a clue about > > the Windows environment (i.e., not me) did it. But it's a (Win32) tar > > archive for the entire "C:" drive. > Whoops... Try a smaller tar to make your tests... Well, I suppose any sub-tree would be somewhat smaller, but I have no idea how Microsoft spells "du". > I did not use amrecover for my restorations, but just amrestore. Why? Because in my > backup architecture, I d not want to restore to data directly on the client but I > restore them on the backup server then push them on the client. > And as WinTar and GnuTar are different, I was just able to extract the dd image from > the tape with amrestore and push these data on the Win32 server, and over there > untar them. > But I was backing up small data, something les than 5 Gb, so I was able to have on > my Windows box the tar and the untar data simultaneously, right :) Ah. Well, nearly anything that is done around here involving a Microsoft platform will need to be done by someone other than me: they seem to be remarkably unreliable around me. (They probably know what I think of them) > Concerning development on Win32 architectures, you have Dev-C++ > (http://sourceforge.net/projects/dev-cpp/) : a free software IDE compiler under > Windows. Well, for whoever does the development, that might be useful; thanks. > Personally I don't like the Win32 client since it is based on a CVS snapshot of > Amanda from august 2001 : so old isn't it?! Understood. I believe that my employer would be willing to pay someone to re-do that work, with a more recent version of the source. > Maybe a future development of this client should only be libraries to interface the > *nix version of Amanda under Win32, maybe real libraries or patches to apply on the > sources, but something that would be generic and not applied on a particular version > and just on this version. Maybe in the longer term; for now, we just want something that actually works. > The 2 other solutions are : > 1. Samba backup using "smbclient" on the Linux Amanda server: simple but you do not > backup NT file rights (well... see some messages above in the mailing-list, someone > sent a little script to backup the rights) Yes, I know of this. However, in our environment, it is not an acceptable approach. > 2. Cygwin and the Amanda source code: very functional but you have to install a > Linux emulator on your Windows box... I don't like the idea (what would you say if I > told you that you have to install a Windows emulator on your BSD to backup your BSD?) Right; I expect that Cygwin will be involved, but only for development. We are trying to minimize the impact on clients' machines. Thanks again, david -- David H. Wolfskill [EMAIL PROTECTED]
Re: Win32 client (was: Re: Amanda GUI)
On Wed, Nov 05, 2003 at 02:36:46PM +0100, JC Simonetti wrote: > > The 2 other solutions are : > ... > 2. Cygwin and the Amanda source code: very functional but you have to install a > Linux emulator on your Windows box... I don't like the idea (what would you say if I > told you that you have to install a Windows emulator on your BSD to backup your BSD?) In addition to "cygwin", which has a large overhead, the same project has another package called, I think, "mingw". Unlike cygwin, which requires a cygwin dll to be on the system, and is GPL'ed, mingw compiles are standalone and can be used to generate non-GPL'ed executables (I think I'm correct there, net lawyers will complain if I'm not :) I've not, but I wonder if anyone has tried to get a set of amanda client executables built under mingw and using the previously mentioned tarNT? BTW, the mingw package would be another way to build the selfcheck/true executable without a full IDE. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Win32 client (was: Re: Amanda GUI)
On Wed, 5 Nov 2003 04:52:33 -0800
David Wolfskill <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 05, 2003 at 10:26:37AM +0100, JC Simonetti wrote:
> > [...]
> > > But in the testing so far, we're finding some odd results:
>
> > > * The actual program that the Win32 client uses to do the backups
> > > appears to be an NT port of tar. But trying to restore a file
> > > made from that backup on a FreeBSD system generates a message saying
> > > that the file does not look like a tar archive.
>
> > Sure... It's a Win32 tar archive...
>
> I wasn't aware that the Win32 environment was sufficiently "special"
> that tar archives were unportable between that and normal (UNIX)
> environments.
It's the reason of the existence of the WinTar software :)
>
> > A tar archive includes: data of the file and data related to the file: name,
> > rights... And rights are completely different between *nix and Windows...
>
> OK; I'll take your word for it.
>
> > Take your tar on a Windows box and untar it: it will be successful.
>
> Well, I suppose it might be, if it were small enough to fit in the
> available space on the Windows box, and if someone who had a clue about
> the Windows environment (i.e., not me) did it. But it's a (Win32) tar
> archive for the entire "C:" drive.
Whoops... Try a smaller tar to make your tests...
>
> > > Also, "ls" showed each directory twice -- once as a directory; once as
> > > a regular file.
>
> > Which ls? In amrecover?
>
> Yes.
>
> > > * Trying to use the "amrestore" on the Win32 side, the "ls" command
> > > doesn't seem to work.
>
> > amrestore or amrecover? amrestore just dd's out the tape and, if you want, make a
> > grep on the output. There's no ls...
>
> Right; sorry: I screwed up. I meant "amrecover".
I did not use amrecover for my restorations, but just amrestore. Why? Because in my
backup architecture, I d not want to restore to data directly on the client but I
restore them on the backup server then push them on the client.
And as WinTar and GnuTar are different, I was just able to extract the dd image from
the tape with amrestore and push these data on the Win32 server, and over there untar
them.
But I was backing up small data, something les than 5 Gb, so I was able to have on my
Windows box the tar and the untar data simultaneously, right :)
>
> > > At some point, I would like my employer to contribute some resources
> > > toward making this version of the amanda client solid enough to install
> > > from the directions and run. This may include paying someone to
> > > implement "selfcheck," for example, as well as other parts of the Win32
> > > client that need attention. Speaking only for myself, I would be less
> > > interested in a GUI for any of this, but that's just me.
>
> > When I tested the Win32 client, I needed a selfcheck. This was for production
> > systems, not workstations (so you may find my solution not useful). My selfcheck
> > was something like:
> > int main() {
> > return 0;
> > }
>
> That's fine (and resembles /usr/src/usr.bin/true/true.c, without
> the BSD copyright that the version I use has), but I have no Win32
> development environment. At the rate things are going, we're looking
> for some help in doing some work in such an environment so we can
> create executables that will actually work; I have no reason to
> believe that a physical presence here (in Fremont, California) is
> especially necessary.
Concerning development on Win32 architectures, you have Dev-C++
(http://sourceforge.net/projects/dev-cpp/) : a free software IDE compiler under
Windows.
Personally I don't like the Win32 client since it is based on a CVS snapshot of Amanda
from august 2001 : so old isn't it?!
Maybe a future development of this client should only be libraries to interface the
*nix version of Amanda under Win32, maybe real libraries or patches to apply on the
sources, but something that would be generic and not applied on a particular version
and just on this version.
The 2 other solutions are :
1. Samba backup using "smbclient" on the Linux Amanda server: simple but you do not
backup NT file rights (well... see some messages above in the mailing-list, someone
sent a little script to backup the rights)
2. Cygwin and the Amanda source code: very functional but you have to install a Linux
emulator on your Windows box... I don't like the idea (what would you say if I told
you that you have to install a Windows emulator on your BSD to backup your BSD?)
Re: Win32 client (was: Re: Amanda GUI)
On Wed, Nov 05, 2003 at 10:26:37AM +0100, JC Simonetti wrote:
> [...]
> > But in the testing so far, we're finding some odd results:
> > * The actual program that the Win32 client uses to do the backups
> > appears to be an NT port of tar. But trying to restore a file
> > made from that backup on a FreeBSD system generates a message saying
> > that the file does not look like a tar archive.
> Sure... It's a Win32 tar archive...
I wasn't aware that the Win32 environment was sufficiently "special"
that tar archives were unportable between that and normal (UNIX)
environments.
> A tar archive includes: data of the file and data related to the file: name,
> rights... And rights are completely different between *nix and Windows...
OK; I'll take your word for it.
> Take your tar on a Windows box and untar it: it will be successful.
Well, I suppose it might be, if it were small enough to fit in the
available space on the Windows box, and if someone who had a clue about
the Windows environment (i.e., not me) did it. But it's a (Win32) tar
archive for the entire "C:" drive.
> > Also, "ls" showed each directory twice -- once as a directory; once as
> > a regular file.
> Which ls? In amrecover?
Yes.
> > * Trying to use the "amrestore" on the Win32 side, the "ls" command
> > doesn't seem to work.
> amrestore or amrecover? amrestore just dd's out the tape and, if you want, make a
> grep on the output. There's no ls...
Right; sorry: I screwed up. I meant "amrecover".
> > At some point, I would like my employer to contribute some resources
> > toward making this version of the amanda client solid enough to install
> > from the directions and run. This may include paying someone to
> > implement "selfcheck," for example, as well as other parts of the Win32
> > client that need attention. Speaking only for myself, I would be less
> > interested in a GUI for any of this, but that's just me.
> When I tested the Win32 client, I needed a selfcheck. This was for production
> systems, not workstations (so you may find my solution not useful). My selfcheck was
> something like:
> int main() {
> return 0;
> }
That's fine (and resembles /usr/src/usr.bin/true/true.c, without
the BSD copyright that the version I use has), but I have no Win32
development environment. At the rate things are going, we're looking
for some help in doing some work in such an environment so we can
create executables that will actually work; I have no reason to
believe that a physical presence here (in Fremont, California) is
especially necessary.
Thanks,
david
--
David H. Wolfskill [EMAIL PROTECTED]
Re: Win32 client (was: Re: Amanda GUI)
[...]
> But in the testing so far, we're finding some odd results:
>
> * The actual program that the Win32 client uses to do the backups
> appears to be an NT port of tar. But trying to restore a file
> made from that backup on a FreeBSD system generates a message saying
> that the file does not look like a tar archive.
Sure... It's a Win32 tar archive...
A tar archive includes: data of the file and data related to the file: name, rights...
And rights are completely different between *nix and Windows...
Take your tar on a Windows box and untar it: it will be successful.
>
> Also, "ls" showed each directory twice -- once as a directory; once as
> a regular file.
Which ls? In amrecover?
>
> * Trying to use the "amrestore" on the Win32 side, the "ls" command
> doesn't seem to work.
amrestore or amrecover? amrestore just dd's out the tape and, if you want, make a grep
on the output. There's no ls...
>
> At some point, I would like my employer to contribute some resources
> toward making this version of the amanda client solid enough to install
> from the directions and run. This may include paying someone to
> implement "selfcheck," for example, as well as other parts of the Win32
> client that need attention. Speaking only for myself, I would be less
> interested in a GUI for any of this, but that's just me.
When I tested the Win32 client, I needed a selfcheck. This was for production systems,
not workstations (so you may find my solution not useful). My selfcheck was something
like:
int main() {
return 0;
}
---
Jean-Christian SIMONETTIemail: [EMAIL PROTECTED]
SysAdmin Wanadoo Portails phone: (+33)493004911
Sophia Antipolis, France
---
Re: Win32 client (was: Re: Amanda GUI)
On Tue, Nov 04, 2003 at 09:35:24AM -0800, David Wolfskill wrote: > > [Re: win32 amanda client from sourceforge) > > But in the testing so far, we're finding some odd results: > > > > * Trying to use the "amrestore" on the Win32 side, the "ls" command > doesn't seem to work. > > At some point, I would like my employer to contribute some resources > toward making this version of the amanda client solid enough to install > from the directions and run. This may include paying someone to > implement "selfcheck," for example, as well as other parts of the Win32 > client that need attention. Speaking only for myself, I would be less > interested in a GUI for any of this, but that's just me. Has anyone got "amrecover" for a file backed up via the win32 client to actually work? If so, how? If not, it is possible that my employer would be willing to pay someone to bring it sufficiently up-to-date that it actually works. (Since the backup image is created OK, we are expecting that this ought not be a huge amount of work for someone with a reasonable ability & willingness to develop in/for the win32 environment.) It would be Nice(tm) if, aas an additional result, it would be possible to do an amrecover from the UNIX side against a backup created in the win32 side and have a reasonable expectation that some arbitrary set of the files could be restored. [I note that I was given a pointer to "star", which may well help with the latter task, but does nothing, as far as I know, for restoring files in the win32 environment.] Thanks, david -- David H. Wolfskill [EMAIL PROTECTED]
Win32 client (was: Re: Amanda GUI)
On Tue, Nov 04, 2003 at 09:09:34AM -0500, Bort, Paul wrote: > > Perhaps I find the time to implement something like this in the next > > weeks...but to be honest before having a GUI for amanda I > > would prefer seeing a windows client *duck* :) > No need to duck! Lots of people would like this, just search for 'SAMBA' > in the mailing list archives. I looked at this "back in the day", and it > breaks down to two parts: A tar clone that can backup and restore files > under NT, and amandad. There are instructions for building amandad under > Cygwin, and there was a SourceForge project for an AMANDA client that had > (IIRC) 90% of a working NT tar, with ACLs. If you combine the two with a > little elbow grease, you could have a Windows client in an afternoon. If > you need to do it without a full Cygwin installation, you could probably > just copy the right files and registry entries out of an existing one. > (I know you can run Cygwin's ssh.exe with just one other DLL, I think it's > cygwin1.dll.) I have had recent exposure to this My employer seeks to provide "backup" services for clients, some of whom evidently have data that they value enough for it to be backed up, but so little that they have chosen to host it on a Microsoft platform. (Yes, I confess that I find this self-contradictory.) And for many (most? all?) of such cases, placing the data on a CIFS/SMB/Samba "share" is (apparently) not acceptable. After seeing the price tag for a proprietary product that would support both the systems I care about (FreeBSD) and the Microsoft environments -- as well as seeing the ugly messages about data overruns from the proprietary product (vs. the clean output in the logs from running amanda) -- we decided to put a bit more effort into coercing the win32 amanda client to work. It's our intent to put together some documentation telling how to make this work (for some plausible definition of "work"), if that would be useful. But in the testing so far, we're finding some odd results: * The actual program that the Win32 client uses to do the backups appears to be an NT port of tar. But trying to restore a file made from that backup on a FreeBSD system generates a message saying that the file does not look like a tar archive. Also, "ls" showed each directory twice -- once as a directory; once as a regular file. * Trying to use the "amrestore" on the Win32 side, the "ls" command doesn't seem to work. At some point, I would like my employer to contribute some resources toward making this version of the amanda client solid enough to install from the directions and run. This may include paying someone to implement "selfcheck," for example, as well as other parts of the Win32 client that need attention. Speaking only for myself, I would be less interested in a GUI for any of this, but that's just me. Peace, david -- David H. Wolfskill [EMAIL PROTECTED]
Re: Another Amanda + Win32 backup problem
Hi,
> Thanks Chris it appears you have found my problem.
[...]
> After issuing strings /opt/amanda/libexec/sendbackup | grep
> amandapass it returns nothing.
I assume you have used your path in the statement above? /opt is not the
default amanda directory.
> So back to compiling amanda.
> I have compiled amanda 2.4.4 and 2.4.4p1 with the following
> ./configure --with-smbclient=/usr/local/samba/bin/smbclient
> --with-user=operator --with-group=sys --with-config=SElvl0 --wit
> h-suffixes --with-libraries=/usr/local/lib
>
> After doing a make, I so another search for amandapass in sendbackup
>
> /amanda-2.4.4p1/client-src$ strings - sendbackup* |grep amandapass
^^
What is this hyphen doing there?
> Do you have any other suggestions? Is there possibly something else
> I'm missing?
I just had a look at the sources here:
[EMAIL PROTECTED] grep amandapass *.c
findpass.c: if ( (fp = fopen("/etc/amandapass", "r")) ) {
selfcheck.c:testfd = open("/etc/amandapass", R_OK);
selfcheck.c:printf("ERROR [/etc/amandapass is world
readable!]\n");
selfcheck.c:printf("OK [/etc/amandapass is readable, but
not by all]\n");
selfcheck.c:printf("OK [unable to stat /etc/amandapass:
%s]\n",
selfcheck.c:printf("ERROR [unable to open /etc/amandapass:
%s]\n",
It looks as if the path "/etc/amandapass" is hard coded.
Christopher
--
==
Dipl.-Ing. Christopher Odenbach
HNI Rechnerbetrieb
[EMAIL PROTECTED]
Tel.: +49 5251 60 6215
==
RE: Another Amanda + Win32 backup problem
Thanks Chris it appears you have found my problem. (see below) > -Original Message- > From: Christopher Odenbach [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 30 September 2003 5:14 PM > To: Jason Tedesco; [EMAIL PROTECTED] > Subject: Re: Another Amanda + Win32 backup problem > > > > Hi Jason, > > > I am trying to backup a win32 host with Amanda and keep running into > > problems. I compiled Amanda with smbclient full path. When I try > > executing an amcheck I receive the following error. > > > > Amanda Backup Client Hosts Check > > > > WARNING: mymachine.host.org: selfcheck request timed out. > Host down? > > Client check: 1 host checked in 30.019 seconds, 1 problem found > > > > (brought to you by Amanda 2.4.4p1) > > > > I also receive this error in my logfile. > > ERROR planner Request to mymachine.host.org timed out. > > > > I increased the etimeout in amanda.conf although that did not change > > a thing. I can use smbclient to mount my drive without a > problem, and > > the directory shard on the win32 host has no permissions set. > > > > This is what I have below in my disklist > > mymachine.host.org //mymachine/temp comp-root-tar > > I think you have not quite understood how amanda's samba backups work. > > The first entry in the disklist should point to the > unix/linux host that > actually starts smbclient. This can be (but does not have to be) your > tape server. Your tape server is actually quite a good idea > to prevent > unneccessary data transfer through your network. > > The second entry contains usually the disk. This is the point where > samba jumps into: If the disk is something like > ///, then > the backup is done via smbclient to the host . > > So: correct your disklist entry to something like > > yourtapeserver.host.org //mymachine/temp comp-root-tar > > > The reason why I have amandapass in two directories is because I am > > unsure which one will be used by amanda on a solaris 8 box. > > Try this on the solaris box (that is on your tape server!): > > [EMAIL PROTECTED]>>strings /opt/amanda/libexec/sendbackup | grep > amandapass > /etc/amandapass > > This is the correct path. > > Greetings, > > Christopher > > -- > == > Dipl.-Ing. Christopher Odenbach > HNI Rechnerbetrieb > [EMAIL PROTECTED] > Tel.: +49 5251 60 6215 > == > > After issuing strings /opt/amanda/libexec/sendbackup | grep amandapass it returns nothing. So back to compiling amanda. I have compiled amanda 2.4.4 and 2.4.4p1 with the following ./configure --with-smbclient=/usr/local/samba/bin/smbclient --with-user=operator --with-group=sys --with-config=SElvl0 --wit h-suffixes --with-libraries=/usr/local/lib After doing a make, I so another search for amandapass in sendbackup /amanda-2.4.4p1/client-src$ strings - sendbackup* |grep amandapass Do you have any other suggestions? Is there possibly something else I'm missing? Thanks. Regards, # jason
Re: Another Amanda + Win32 backup problem
Hi Jason, > I am trying to backup a win32 host with Amanda and keep running into > problems. I compiled Amanda with smbclient full path. When I try > executing an amcheck I receive the following error. > > Amanda Backup Client Hosts Check > > WARNING: mymachine.host.org: selfcheck request timed out. Host down? > Client check: 1 host checked in 30.019 seconds, 1 problem found > > (brought to you by Amanda 2.4.4p1) > > I also receive this error in my logfile. > ERROR planner Request to mymachine.host.org timed out. > > I increased the etimeout in amanda.conf although that did not change > a thing. I can use smbclient to mount my drive without a problem, and > the directory shard on the win32 host has no permissions set. > > This is what I have below in my disklist > mymachine.host.org //mymachine/temp comp-root-tar I think you have not quite understood how amanda's samba backups work. The first entry in the disklist should point to the unix/linux host that actually starts smbclient. This can be (but does not have to be) your tape server. Your tape server is actually quite a good idea to prevent unneccessary data transfer through your network. The second entry contains usually the disk. This is the point where samba jumps into: If the disk is something like ///, then the backup is done via smbclient to the host . So: correct your disklist entry to something like yourtapeserver.host.org //mymachine/temp comp-root-tar > The reason why I have amandapass in two directories is because I am > unsure which one will be used by amanda on a solaris 8 box. Try this on the solaris box (that is on your tape server!): [EMAIL PROTECTED]>>strings /opt/amanda/libexec/sendbackup | grep amandapass /etc/amandapass This is the correct path. Greetings, Christopher -- == Dipl.-Ing. Christopher Odenbach HNI Rechnerbetrieb [EMAIL PROTECTED] Tel.: +49 5251 60 6215 ==
RE: Another Amanda + Win32 backup problem
Does the share have a large amount of data ? One of our file servers over here does and sometimes the amcheck also times out. Bert De Ridder PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be "Jason Tedesco" <[EMAIL PROTECTED]> 30/09/2003 08:57 To <[EMAIL PROTECTED]> cc <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> Subject RE: Another Amanda + Win32 backup problem Sorry that was just a typo, they do have 2 slashes in amandapass -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, 30 September 2003 4:54 PM To: Jason Tedesco Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Another Amanda + Win32 backup problem Your entries in amandapass should also have 2 slashes -> //mymachine/temp username%password HTH Bert De Ridder PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be "Jason Tedesco" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 30/09/2003 08:45 To <[EMAIL PROTECTED]> cc Subject Another Amanda + Win32 backup problem I am trying to backup a win32 host with Amanda and keep running into problems. I compiled Amanda with smbclient full path. When I try executing an amcheck I receive the following error. Amanda Backup Client Hosts Check WARNING: mymachine.host.org: selfcheck request timed out. Host down? Client check: 1 host checked in 30.019 seconds, 1 problem found (brought to you by Amanda 2.4.4p1) I also receive this error in my logfile. ERROR planner Request to mymachine.host.org timed out. I increased the etimeout in amanda.conf although that did not change a thing. I can use smbclient to mount my drive without a problem, and the directory shard on the win32 host has no permissions set. This is what I have below in my disklist mymachine.host.org //mymachine/temp comp-root-tar I also have a username and password set out in /etc/amandapass and /usr/local/etc/amandapass . The reason why I have amandapass in two directories is because I am unsure which one will be used by amanda on a solaris 8 box. /mymachine/temp username%password Any advice would be appreciated. Regards, Jason
RE: Another Amanda + Win32 backup problem
Sorry
that was just a typo, they do have 2 slashes in
amandapass
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Sent: Tuesday, 30 September
2003 4:54 PMTo: Jason TedescoCc:
[EMAIL PROTECTED]; [EMAIL PROTECTED]Subject: Re:
Another Amanda + Win32 backup problemYour entries in amandapass should also have 2 slashes
-> //mymachine/temp
username%passwordHTHBert De RidderPeopleWare NV - Head OfficeCdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38
Fax: +32 3 448.32.66 PeopleWare NV - Branch Office GeelKleinhoefstraat 5B-2440 GeelTel: +32 14
57.00.90Fax: +32 14 58.13.25http://www.peopleware.be
"Jason Tedesco"
<[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED]
30/09/2003 08:45
To
<[EMAIL PROTECTED]>
cc
Subject
Another Amanda + Win32
backup problem
I am trying to backup a win32 host with Amanda and keep running
into problems. I compiled Amanda with smbclient full path.When I try
executing an amcheck I receive the following error.Amanda Backup
Client Hosts CheckWARNING:
mymachine.host.org: selfcheck request timed out. Host down?Client
check: 1 host checked in 30.019 seconds, 1 problem found(brought to
you by Amanda 2.4.4p1)I also receive this error in my
logfile.ERROR planner Request to mymachine.host.org timed out.I
increased the etimeout in amanda.conf although that did not change a
thing.I can use smbclient to mount my drive without a problem, and the
directory shard on the win32 host has no permissions set.This is what
I have below in my disklistmymachine.host.org //mymachine/temp
comp-root-tarI also have a username and password set out in
/etc/amandapass and /usr/local/etc/amandapass . The reason why I have
amandapass in two directories is because I am unsure which one will be used by
amanda on a solaris 8 box./mymachine/temp
username%passwordAny advice would be
appreciated.Regards,
Jason
Re: Another Amanda + Win32 backup problem
Your entries in amandapass should also have 2 slashes -> //mymachine/temp username%password HTH Bert De Ridder PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be "Jason Tedesco" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 30/09/2003 08:45 To <[EMAIL PROTECTED]> cc Subject Another Amanda + Win32 backup problem I am trying to backup a win32 host with Amanda and keep running into problems. I compiled Amanda with smbclient full path. When I try executing an amcheck I receive the following error. Amanda Backup Client Hosts Check WARNING: mymachine.host.org: selfcheck request timed out. Host down? Client check: 1 host checked in 30.019 seconds, 1 problem found (brought to you by Amanda 2.4.4p1) I also receive this error in my logfile. ERROR planner Request to mymachine.host.org timed out. I increased the etimeout in amanda.conf although that did not change a thing. I can use smbclient to mount my drive without a problem, and the directory shard on the win32 host has no permissions set. This is what I have below in my disklist mymachine.host.org //mymachine/temp comp-root-tar I also have a username and password set out in /etc/amandapass and /usr/local/etc/amandapass . The reason why I have amandapass in two directories is because I am unsure which one will be used by amanda on a solaris 8 box. /mymachine/temp username%password Any advice would be appreciated. Regards, Jason
Another Amanda + Win32 backup problem
I am trying to backup a win32 host with Amanda and keep running into problems. I compiled Amanda with smbclient full path. When I try executing an amcheck I receive the following error. Amanda Backup Client Hosts Check WARNING: mymachine.host.org: selfcheck request timed out. Host down? Client check: 1 host checked in 30.019 seconds, 1 problem found (brought to you by Amanda 2.4.4p1) I also receive this error in my logfile. ERROR planner Request to mymachine.host.org timed out. I increased the etimeout in amanda.conf although that did not change a thing. I can use smbclient to mount my drive without a problem, and the directory shard on the win32 host has no permissions set. This is what I have below in my disklist mymachine.host.org //mymachine/temp comp-root-tar I also have a username and password set out in /etc/amandapass and /usr/local/etc/amandapass . The reason why I have amandapass in two directories is because I am unsure which one will be used by amanda on a solaris 8 box. /mymachine/temp username%password Any advice would be appreciated. Regards, Jason
RE: Amanda win32 Client
I also looked at the project on sourceforge for the Win32 client. The task that I found too daunting to contemplate when I tried this was interfacing to the Win32 file system. The win32 client project included a TAR that they claimed worked on NT and picked up ACLs. So really the remaining task is a TCP/IP daemon that can accept and execute commands from the AMANDA server. Maybe I'll dig up some of my old Perl scripts... > -Original Message- > From: Christophe Kalt [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 11, 2003 11:35 AM > To: [EMAIL PROTECTED] > Subject: Re: Amanda win32 Client > > > On Sep 03, Kurt Yoder wrote: > | Anyone on this list interested in being paid to re-do the Windows > | client? Ideally, I'd want something with an easy-to-use installer. > | Should work more consistently than the current Windows client, and > | file restores should be simple. I don't care if it's a ground-up > | reimplementation, or what language it's in. > > You should.. this shouldn't be a reimplementation, just a > port. The old win32 client was kind of a port, but since it > was done separately and not merged, it drifted off the unix > code. > Not fun to do, i started looking into it a while back, but the > best approach by far. >
Re: Amanda win32 Client
On Wed, Sep 03, 2003 at 03:19:58PM +0200, Uwe Beger wrote: > All my important win boxes (actually only Win2K) do a standard M$ backup on > a samba share, which is backed up by amanda. > Advantages: immediate recovery possible > Disadv.: disk space BackupPC (http://backuppc.sourceforge.net/index.html) looks like a possible replacement for MS backup for the first phase of this scheme. It looks as though it could save a lot of disk space compared to MS backup, since it optimizes multiple identical copies of a file into a single copy on the backup disk. So for backing up a cluster of Windows boxes, you'd only need backup-disk space for one copy of Windows, not N. (Same principle could apply to other O/S's of course, and indeed BackupPC says it works on Linux too. Not sure about other Unices...) For the same reason, it'd also save huge amounts of tape. You wouldn't be plopping modified multi-gigabyte backup archives into your spool every night, most of whose contents were identical to the previous night's. As I say, it looks cool (and GPL too!) but I've never tried it. Does anyone here have any experience with it? (Well, someone must, since it got a mention in Jon's survey.) What do you think of it? -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: Amanda win32 Client
On Sep 03, Kurt Yoder wrote: | Anyone on this list interested in being paid to re-do the Windows | client? Ideally, I'd want something with an easy-to-use installer. | Should work more consistently than the current Windows client, and | file restores should be simple. I don't care if it's a ground-up | reimplementation, or what language it's in. You should.. this shouldn't be a reimplementation, just a port. The old win32 client was kind of a port, but since it was done separately and not merged, it drifted off the unix code. Not fun to do, i started looking into it a while back, but the best approach by far.
RE: Amanda win32 Client
JC Simonetti said: > Concerning you and Uwe Beger, could you please tell me the > approximative size of your Windows backups per day? Do you back > up a production site, workstations? > > Okay, I lied a little bit here, I don't do it all via NTBackup. These are SQL Server boxes I'm backing up, currently two of them. I have the SQL Server do it's backups to the same samba share, and then NTBackup backs up all the system stuff. The windows backups are about 3Gig each. The SQL data is about 500Meg for the one box and about 6Gig for the other. The 6Gig SQL backup takes about 17 minutes to complete, the Windows backup takes around 10 minutes. Josh
Re: Amanda win32 Client
Anyone on this list interested in being paid to re-do the Windows client? Ideally, I'd want something with an easy-to-use installer. Should work more consistently than the current Windows client, and file restores should be simple. I don't care if it's a ground-up reimplementation, or what language it's in. Any takers? Approximate asking price to do the job? Anyone else want to chip in money to make this happen? JC Simonetti said: > You have 3 ways to backup Windows by Amanda: > 1. Win32 client: good luck, since its development has been stopped 2 > years ago > 2. Windows shares and Samba client on your Amanda box: not so good > because of the rights of the files that are bot backed up > 3. Amanda standard client installed under Cygwin on your Windows > box: OK, but you have to install Cygwin first; and I'm not sure I > like this solution, just because I have to install a "Linux > emulator" on a Windows box (can you imagine yourself installing a > Wine on your Linux just to make some administrative operations? I > don't). -- Kurt Yoder Sport & Health network administrator
Re: Amanda win32 Client
Concerning you and Uwe Beger, could you please tell me the approximative size of your Windows backups per day? Do you back up a production site, workstations? On Wed, 3 Sep 2003 08:33:35 -0500 "Josh Welch" <[EMAIL PROTECTED]> wrote: > JC Simonetti said: > > > > You have 3 ways to backup Windows by Amanda: > > 1. Win32 client: good luck, since its development has been > > stopped 2 years ago > > 2. Windows shares and Samba client on your Amanda box: not so > > good because of the rights of the files that are bot backed up > > 3. Amanda standard client installed under Cygwin on your Windows > > box: OK, but you have to install Cygwin first; and I'm not sure I > > like this solution, just because I have to install a "Linux > > emulator" on a Windows box (can you imagine yourself installing a > > Wine on your Linux just to make some administrative operations? I don't). > > > > In my case, I have adopted 3 different solutions, depending on > > the boxes I back up: > > 1. Samba > > 2. Cygwin > > 3. backup Windows computers with official Windows backup solutions > > > > > > --- > > Jean-Christian SIMONETTIemail: [EMAIL PROTECTED] > > SysAdmin Wanadoo Portails phone: (+33)493004911 > > Sophia Antipolis, France > > --- > > > > I have taken to using NTBackup on my Win2K boxes to back up to a samba share > on a box a set up for the purpose. Stuff a couple of big IDE disks in an old > Dell desktop and you've got a very cheap NAS. > Too bad NTBackup doesn't do software compression, however. > > Josh --- Jean-Christian SIMONETTIemail: [EMAIL PROTECTED] SysAdmin Wanadoo Portails phone: (+33)493004911 Sophia Antipolis, France ---
RE: Amanda win32 Client
JC Simonetti said: > > You have 3 ways to backup Windows by Amanda: > 1. Win32 client: good luck, since its development has been > stopped 2 years ago > 2. Windows shares and Samba client on your Amanda box: not so > good because of the rights of the files that are bot backed up > 3. Amanda standard client installed under Cygwin on your Windows > box: OK, but you have to install Cygwin first; and I'm not sure I > like this solution, just because I have to install a "Linux > emulator" on a Windows box (can you imagine yourself installing a > Wine on your Linux just to make some administrative operations? I don't). > > In my case, I have adopted 3 different solutions, depending on > the boxes I back up: > 1. Samba > 2. Cygwin > 3. backup Windows computers with official Windows backup solutions > > > --- > Jean-Christian SIMONETTIemail: [EMAIL PROTECTED] > SysAdmin Wanadoo Portails phone: (+33)493004911 > Sophia Antipolis, France > --- > I have taken to using NTBackup on my Win2K boxes to back up to a samba share on a box a set up for the purpose. Stuff a couple of big IDE disks in an old Dell desktop and you've got a very cheap NAS. Too bad NTBackup doesn't do software compression, however. Josh
Re: Amanda win32 Client
I prefere #3 All my important win boxes (actually only Win2K) do a standard M$ backup on a samba share, which is backed up by amanda. Advantages: immediate recovery possible Disadv.: disk space At 13:26 03.09.2003, JC Simonetti wrote: You have 3 ways to backup Windows by Amanda: 1. Win32 client: good luck, since its development has been stopped 2 years ago 2. Windows shares and Samba client on your Amanda box: not so good because of the rights of the files that are bot backed up 3. Amanda standard client installed under Cygwin on your Windows box: OK, but you have to install Cygwin first; and I'm not sure I like this solution, just because I have to install a "Linux emulator" on a Windows box (can you imagine yourself installing a Wine on your Linux just to make some administrative operations? I don't). In my case, I have adopted 3 different solutions, depending on the boxes I back up: 1. Samba 2. Cygwin 3. backup Windows computers with official Windows backup solutions
Re: Amanda win32 Client
Hi Jon! Thank you for your reply! Does that mean that it isn't possible to backup Windows Client with Amanda? Ones again, thank you very much for your reply! - Christoffer tir, 2003-09-02 kl. 17:33 skrev Jon LaBadie: Not an authoritative answer by any means, so I make it off list.
Re: Amanda win32 Client
You have 3 ways to backup Windows by Amanda: 1. Win32 client: good luck, since its development has been stopped 2 years ago 2. Windows shares and Samba client on your Amanda box: not so good because of the rights of the files that are bot backed up 3. Amanda standard client installed under Cygwin on your Windows box: OK, but you have to install Cygwin first; and I'm not sure I like this solution, just because I have to install a "Linux emulator" on a Windows box (can you imagine yourself installing a Wine on your Linux just to make some administrative operations? I don't). In my case, I have adopted 3 different solutions, depending on the boxes I back up: 1. Samba 2. Cygwin 3. backup Windows computers with official Windows backup solutions --- Jean-Christian SIMONETTIemail: [EMAIL PROTECTED] SysAdmin Wanadoo Portails phone: (+33)493004911 Sophia Antipolis, France --- On 03 Sep 2003 08:35:52 +0200 Christoffer Dahl Petersen <[EMAIL PROTECTED]> wrote: > Hi Jon! > > Thank you for your reply! > Does that mean that it isn't possible to backup Windows Client with > Amanda? > > Ones again, thank you very much for your reply! > > - Christoffer > > tir, 2003-09-02 kl. 17:33 skrev Jon LaBadie: > > > Not an authoritative answer by any means, so I make it off list. > >
Amanda win32 Client
Hi I have tried the Amanda win32 Client. My question is: can I only do a backup of an entire drive and not a specified folder? Best regards Christoffer
Backing Up Win32 Registry
>From: JC Simonetti <[EMAIL PROTECTED]> > >Have you tried to backup an entire registry and restore it with the regedit method? >Because I think of a problem: the registry is composed of data but these data also have access rights. "regedit" does not display them (whereas "regedt32" does). I am currently logged into my WinXP box (2.5GHz P4) as a member of the Administrators group. >From CygWin: $ cd d: $ cd temp $ regedit /e bak1.reg $ regedt32 /e bak2.reg $ diff bak1.reg bak2.reg diff generates no output. >Just a last remark. When you want to restore registry, you must have a valid registry, whatever solution you choose (regedit, regedt32, regrest...). So if your computer crashes completely you have to reinstall a basic Windows before restoring anything else. Not true. The whole point of the `/c' flag on regedit is that it CREATES a NEW, VALID registry, containing ONLY the keys found in your source file. >From comments found via Google, (no, I have not tried it myself) if needs be, you can boot to a floppy or cdrom and run `regedit /c ...' and then be able to boot the system normally. (assuming your only problem was a corrupt / deleted registry) I have a few machines sitting in my boneyard at home. I'll see if I can get the time tonight to: grab one, install a random Windows version, back up the registry to a cdrom, delete several key registry files, verify that the system no longer boots, boot to a floppy, and restore the registry via `regedit /c'
Re: Win32 Backup?
"Steve Loughran" <[EMAIL PROTECTED]> wrote: >> One way I have done it is to use MS's backup program to backup to a >> samba share on a freebsd box. MS backup will happily backup to a samba >> share. Then I just backup all that stuff using amanda. > >beware of backing up via NT Backup to a samba share, always verify the >contents of the file. I ran into a problem wher it appeared to be backing up >just fine, and created a huge BKF file, but it was full of zeros and >unusable... I've been using ntbackup to files on samba share for a number of weeks now, haven't seen any problems. I do have the verify flag on. Perhaps it's the samba version or config, or maybe networking issues? Just a thought. I did have to alter my original schedule/dump type in ntbackup. I was getting tape overruns due to that fact that amanda has no control of the w2k boxes schedule/dump type. It would be very cool if some smart win programmer could write wrappers for ntbackup.exe so that amanda could control it directly. Also, I copy over the ntbackup log files at the end of the script. Seems it can only have 10 log files at a time. Ntbackup in w2k is pretty useful. Although Veritas did write it for them. -- toby bluhm philips medical systems, it support, mr development, cleveland ohio [EMAIL PROTECTED] 440-483-5323
Re: Win32 Backup?
> One way I have done it is to use MS's backup program to backup to a > samba share on a freebsd box. MS backup will happily backup to a samba > share. Then I just backup all that stuff using amanda. beware of backing up via NT Backup to a samba share, always verify the contents of the file. I ran into a problem wher it appeared to be backing up just fine, and created a huge BKF file, but it was full of zeros and unusable... Steve
Re: Win32 Backup?
I've had weird stuff happen to me when writing across samba mounts -- the files would quietly disappear under the Nethood pseudo-directory, eating up disk space while being inaccessible. Associating the mounts with drive letters seems to avoid this.
Re: Win32 Backup?
Anthony A. D. Talltree wrote: I've never had to do this, but an approach that I'd probably persue would be to use Symmantec/Norton Ghost to create occasional disk images that would get xferred via Samba to a *ix filesystem. I'd try real hard to keep important data off of the M$ machine's local disks. One way I have done it is to use MS's backup program to backup to a samba share on a freebsd box. MS backup will happily backup to a samba share. Then I just backup all that stuff using amanda. I've used MS backup on XP Pro and w2kpro this way and it works pretty well for my needs. -- Michael Perry | Do or do not. There is no try. -Master Yoda [EMAIL PROTECTED] | http://www.lnxpowered.org
Re: Win32 Backup?
I've never had to do this, but an approach that I'd probably persue would be to use Symmantec/Norton Ghost to create occasional disk images that would get xferred via Samba to a *ix filesystem. I'd try real hard to keep important data off of the M$ machine's local disks.
Re: Win32 Backup?
> > I've used Amanda before in a Unix-only shop, but now am interested in > > backing up Win32 clients. > > > > I see Amanda.Org still seems to hold the official line of "use smbclient > > to backup Win32 clients," but there's a port of Amanda client to Win32 > > at http://sourceforge.net/projects/amanda-win32 which appears to have > > about 5-15 downloads daily for the last week or two. > > I can't tell you much, but I can tell that the official 2.4.4 version > supports the cygwin environment. There have been a number of messages on > this recently -- search the archives. Okay, I searched the archives. There is some conjecture that the Win32 client is not too recent, but there doesn't seem to be anything concrete. Someone else said the 'sbmclient' method gives problems when the user setup to do the backups on the Win32 client don't have permissions to back up the machine. Cygwin method requires first installing Cygwin on every client, right? smbclient method requires only creating a user on every client. So unless every Win32 client has Cygwin installed... would it be safe to say that The One Right Way to do Win32 backups is: - Setup a local administrator on the client (say, "amanda") - Use smbclient at the server to backup - Don't use the Win32 client at SourceForge (it's out-of-date) ? -- pv
Re: Win32 Backup?
On 4 Mar 2003 at 10:54am, philo vivero wrote > I've used Amanda before in a Unix-only shop, but now am interested in > backing up Win32 clients. > > I see Amanda.Org still seems to hold the official line of "use smbclient > to backup Win32 clients," but there's a port of Amanda client to Win32 > at http://sourceforge.net/projects/amanda-win32 which appears to have > about 5-15 downloads daily for the last week or two. > > What can you tell me about the Win32 port of Amanda client software? Is > it appropriate for backing up a heterogenous Win'95, Win'98, Win'XP, > Win'2K network? What are the 'gotchas'? I can't tell you much, but I can tell that the official 2.4.4 version supports the cygwin environment. There have been a number of messages on this recently -- search the archives. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Win32 Backup?
Hi, I've used Amanda before in a Unix-only shop, but now am interested in backing up Win32 clients. I see Amanda.Org still seems to hold the official line of "use smbclient to backup Win32 clients," but there's a port of Amanda client to Win32 at http://sourceforge.net/projects/amanda-win32 which appears to have about 5-15 downloads daily for the last week or two. What can you tell me about the Win32 port of Amanda client software? Is it appropriate for backing up a heterogenous Win'95, Win'98, Win'XP, Win'2K network? What are the 'gotchas'? -- pv
Re: amanda-win32 project
Paolo, I tried many times to get amanda-win32 to work. The "port" is very old and doesn't look like anyone is working on it currently (I haven't looked lately). I decided to rewrite my the code from scratch. I am having some problems with the current amanda server that should be worked out in the next week or so. I will keep this list informed. Jim > Hi > > Does anyone have any information on the usability status of the > amanda-win32 > project? > > Paolo
RE: amanda-win32 project
Hi Jim Indeed I saw the same thing (the last files on sourceforge are from June 2001!). I've downloaded the source too see if there is anything I could do to patch it enough to make it work, but it seemed just like a scaled down version of the original amanda source (I only scanned it briefly last night). I think that allot of work to be done to bring it to a stable enough version that the general community of amanda can use it. I will try to turn it to something useful. I'm a very inexprienced programmer so it might take me ages to produce something :( Paolo -Original Message- From: Jim Buttafuoco [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 6:14 PM To: Paolo Supino; '[EMAIL PROTECTED]' Subject: Re: amanda-win32 project Paolo, I tried many times to get amanda-win32 to work. The "port" is very old and doesn't look like anyone is working on it currently (I haven't looked lately). I decided to rewrite my the code from scratch. I am having some problems with the current amanda server that should be worked out in the next week or so. I will keep this list informed. Jim > Hi > > Does anyone have any information on the usability status of the > amanda-win32 > project? > > Paolo
amanda-win32 project
Hi Does anyone have any information on the usability status of the amanda-win32 project? Paolo
Re: Thoughts on Win32
[EMAIL PROTECTED] wrote: Greetings, I am about to attempt to archive my Win32 hosts with amanda. I was wondering what the list users experience has been with samba and/or the Win32 amanda client. Thank you, Andrew I've had great luck with Samba. I have avoided the win32 client mainly because it doesn't appear to be under development any longer. Others have reported success with cygwin and compiling amanda on each win client. =G=
Thoughts on Win32
Greetings, I am about to attempt to archive my Win32 hosts with amanda. I was wondering what the list users experience has been with samba and/or the Win32 amanda client. Thank you, Andrew
RE: Thoughts on Win32
Andrew, Here are the methods currently available, that I know of, and my opinions on them: 1. SAMBA via smbclient: easiest to set up, but direct restores are tricky; better to restore to the *nix box running smbclient and then move the files back yourself. Works best when you just backup critical data directories. This is what I'm currently using for my Windows boxen. 2. SAMBA via smbmount: looks like a regular tar to AMANDA, but you have to keep the mount connected, and I'm not sure it will handle spaces in filenames as well. I never got this working the way I wanted, but that was mostly my lack of SAMBA knowledge. 3. NFS: There is an NFS server implementation available from Microsoft as part of "Unix Services for Windows". In theory, you could NFS mount and backup with tar. It appears that most people use SAMBA instead of sending more money to Redmond. 4. Amanda-Win32 client: I looked at this and stopped looking when I got to the part where it doesn't work with amcheck. Maybe they've fixed that since spring '02, I haven't had time to keep up with it, but since my backups run overnight, I need amcheck to let me know all is well before I go home. 5. Amanda Client under Cygwin: A very recent development on the amanda-hackers list (Many thanks to Doug and Joshua) is a patch for compiling the real AMANDA source under Cygwin. I've gotten it working with some kludginess on one server, and all of the problems I'm having seem to be coming from my lack of understanding of Cygwin. This is under active development and looks very promising. If you're ok with installing Cygwin on your Windows machines, I'd give this a try. Any other thoughts? > -Original Message- > From: [EMAIL PROTECTED] [mailto:ahall@;secureworks.net] > Sent: Thursday, October 24, 2002 1:32 PM > To: [EMAIL PROTECTED] > Subject: Thoughts on Win32 > > > Greetings, > > I am about to attempt to archive my Win32 hosts with amanda. I was > wondering what the list users experience has been with samba > and/or the > Win32 amanda client. > > Thank you, > > Andrew >
Re: Thoughts on Win32
On Thu, 24 Oct 2002, Galen Johnson wrote: > [EMAIL PROTECTED] wrote: > > >Greetings, > > > >I am about to attempt to archive my Win32 hosts with amanda. I was > >wondering what the list users experience has been with samba and/or the > >Win32 amanda client. > > > >Thank you, > > > >Andrew > > > > > > > I've had great luck with Samba. I have avoided the win32 client mainly > because it doesn't appear to be under development any longer. Others > have reported success with cygwin and compiling amanda on each win client. > > =G= > > In reading the list archives I found a message that stated that due the the fact that the ctime is not perserved it causes amanda to run a full backup every run. Is this still the case? Andrew
RE: Thoughts on Win32
Don't know. I use it for DB dumps, so I want a full backup every time anyway. > -Original Message- > From: [EMAIL PROTECTED] [mailto:ahall@;secureworks.net] > Sent: Thursday, October 24, 2002 2:22 PM > To: Galen Johnson > Cc: [EMAIL PROTECTED] > Subject: Re: Thoughts on Win32 > > > > > On Thu, 24 Oct 2002, Galen Johnson wrote: > > > [EMAIL PROTECTED] wrote: > > > > >Greetings, > > > > > >I am about to attempt to archive my Win32 hosts with amanda. I was > > >wondering what the list users experience has been with > samba and/or the > > >Win32 amanda client. > > > > > >Thank you, > > > > > >Andrew > > > > > > > > > > > I've had great luck with Samba. I have avoided the win32 > client mainly > > because it doesn't appear to be under development any > longer. Others > > have reported success with cygwin and compiling amanda on > each win client. > > > > =G= > > > > > > > In reading the list archives I found a message that stated > that due the > the fact that the ctime is not perserved it causes amanda to > run a full > backup every run. Is this still the case? > > Andrew >
Re: Thoughts on Win32
[EMAIL PROTECTED] wrote: On Thu, 24 Oct 2002, Galen Johnson wrote: [EMAIL PROTECTED] wrote: Greetings, I am about to attempt to archive my Win32 hosts with amanda. I was wondering what the list users experience has been with samba and/or the Win32 amanda client. Thank you, Andrew I've had great luck with Samba. I have avoided the win32 client mainly because it doesn't appear to be under development any longer. Others have reported success with cygwin and compiling amanda on each win client. =G= In reading the list archives I found a message that stated that due the the fact that the ctime is not perserved it causes amanda to run a full backup every run. Is this still the case? Andrew If it does then it claims otherwise in the backups. I've gotten up to a level 2 on some of my smbclient based backups. =G=
RE: Installing from source (was Re: Amanda & win32 / MacOS clients)
> Amanda has a lot of configure-time options, user and group being required
> ones. Going through those can not only give you a more
> customized install
> (e.g., all my clients were compiled with --with-index-server set,
> so I can
> run amrecover without command line options) but also can give a
> new user a
> better understanding of how amanda works.
Agreed.
>
> I do prefer RPMs for almost everything I do. But I still install amanda
> from source for the customization benefits.
I like using RPMs whenever possible, primarily to keep source off production
systems and for maintainability ("geez, again, which software is installed
on this box?").
When I feel the need to custom-compile software, I build my own RPM spec and
source code patches as needed and use that RPM instead. Gives you the best
of both worlds.
Bernhard
Re: Installing from source (was Re: Amanda & win32 / MacOS clients)
On Thu, 17 Oct 2002 at 8:56am, Doug Meredith wrote > - Original Message - > > From: "Joshua Baker-LePain" <[EMAIL PROTECTED]> > [...] > > Source is the preferred way to install amanda. > > Yours maybe, not mine. :) Seriously, if I have a reputable source of an > RPM, why is this less desirable than going to the source? Amanda has a lot of configure-time options, user and group being required ones. Going through those can not only give you a more customized install (e.g., all my clients were compiled with --with-index-server set, so I can run amrecover without command line options) but also can give a new user a better understanding of how amanda works. I do prefer RPMs for almost everything I do. But I still install amanda from source for the customization benefits. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Installing from source (was Re: Amanda & win32 / MacOS clients)
- Original Message - > From: "Joshua Baker-LePain" <[EMAIL PROTECTED]> [...] > Source is the preferred way to install amanda. Yours maybe, not mine. :) Seriously, if I have a reputable source of an RPM, why is this less desirable than going to the source? Doug -- Doug Meredith Skyridge Systems Inc. (506) 854-7997 www.skyridge.com
Re: Amanda & win32 / MacOS clients
On Wed, 16 Oct 2002 at 9:59pm, Jason Hines wrote > This is a pretty heavy traffic list, so I won't bore you all with my > setup details and planned usage for Amanda, but I'm about to install the > new Amanda 2.4.3 on a RH7.3 server (Anyone working on RPMs btw?) and had > some questions. Source is the preferred way to install amanda. > * What is the status (if any) of any clients written for MacOS and/or > Windows. Is the only non-unix solution to use Samba? A possible Win client was very recently discussed -- check the archives. I *think* some people have managed to compile amanda under OSX, but I also recall there being "issues" with this. The samba support works well. > * I will not be using a tape device. How is the support for backing up > to disk? You want the file: driver. Look in amanda(8) installed with 2.4.3 for all the gory details. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Amanda & win32 / MacOS clients
Hi, This is a pretty heavy traffic list, so I won't bore you all with my setup details and planned usage for Amanda, but I'm about to install the new Amanda 2.4.3 on a RH7.3 server (Anyone working on RPMs btw?) and had some questions. * What is the status (if any) of any clients written for MacOS and/or Windows. Is the only non-unix solution to use Samba? * I will not be using a tape device. How is the support for backing up to disk? Thanks, and I apologize if I missed these topics in the FAQ. jason
Re: win32
On Sep 19, Brian Jonnes wrote: | On Thu 19 Sep 02 16:32, Christophe Kalt wrote: | > Also, it seems that it would be much less work to actually | > port the existing (UNIX) amanda source (at least or at most?;) | > the client parts. Having a separate project really doesn't | > seem right. | | Erm... ever tried to port code from Unix to Windows? yes, i've done it a few times, and have maintained programs that could be compiled natively on either platform. Depending on what the application is/does and how it was written, it isn't hard at all. this doesn't say anything about how feasible this would be for amanda, i haven't looked at the code this closely.
Re: win32
Brian, Tried that, but there is alot of UNIXism in amanda. I did go the cygwin route a couple of years ago. It kind of worked. I am currently rewriting the whole client side in perl. To get it to work you just have to download ActiveState perl and my script, that's it. I am also looking at using this perl code to backup UNIX/Linux plus any other type of systems (ie. OSX) that supports perl. Should have some code for people to look at early next week. Jim > On Thu 19 Sep 02 16:32, Christophe Kalt wrote: > > Also, it seems that it would be much less work to actually > > port the existing (UNIX) amanda source (at least or at most?;) > > the client parts. Having a separate project really doesn't > > seem right. > > Erm... ever tried to port code from Unix to Windows? > > Ever wonder why there is so little Opensource Windows code? > > ..Brian > -- > Init Systems - Linux consulting > 031 767-0139082 769-2320[EMAIL PROTECTED]
Re: win32
On Thu 19 Sep 02 16:32, Christophe Kalt wrote: > Also, it seems that it would be much less work to actually > port the existing (UNIX) amanda source (at least or at most?;) > the client parts. Having a separate project really doesn't > seem right. Erm... ever tried to port code from Unix to Windows? Ever wonder why there is so little Opensource Windows code? ..Brian -- Init Systems - Linux consulting 031 767-0139082 769-2320[EMAIL PROTECTED]
Re: win32
On Sep 18, JC Simonetti wrote: | If someone is interested in going through the development | of this client, we might start the development again... But | I cannot do it alone, I do not have enough time. What i don't understand is why noone's actually looked at writing a native port of amandad or why NTTAR is used rather than ntbackup or some other native tool. (I don't believe NTTAR will work for everything, for instance MS Exchange..) IMO, the samba hack is a nasty kludge, and totally inappropriate for a lot of things as it doesn't handle extended attributes (such as ACLs). The amanda-win32 looked promising, but nothing's been happening with it for a long time as people have mentioned. And it is based on the PW32 SF project which is in the same state of abandonment as amanda-win32, so you're actually looking at 2 projects to maintain, not just one. Also, it seems that it would be much less work to actually port the existing (UNIX) amanda source (at least or at most?;) the client parts. Having a separate project really doesn't seem right.
Re: win32
Excludes currently support the standard amanda format. But since it's written in perl you can use ANY valid perl re to exclude files. Jim > If it handles exclusions, hell yes. > > My users are a lot of analysis engineers and I need to be able to > exclude some HUGE interim files made during analasys processing. > > Jim Buttafuoco wrote: > > >I tried for days to get it to work, NO luck. > > > > > >I decided to rewrite the amandad in perl (doesn't need any external programs other >than Perl and a few modules). > > > >I currently have a VERY alpha version of this working here. I should be ready to >release 0.02 next week. > > > >Is anyone interested? > > > >Jim > > > > > > > >>On Wed, 11 Sep 2002, Galen Johnson wrote: > >> > >>>Hello gang, > >>> > >>>A while back I had sent a request regarding backing up windows machines > >>>without having to deal with samba. Someone had responded with the win32 > >>>Amanda client on sourceforge. I have looked it up and it seems like > >>>it'll do what I want. However, it hasn't been touched in 18 months. Is > >>>anyone currently using this with Amanda 2.4.3.b4? > >>> > >>I downloaded this package but have been unable to get it to work - anyone > >>using it successfully? > >> > >>*** Qmail-Scanner Envelope Details Begin *** > >>X-Qmail-Scanner-Mail-From: "[EMAIL PROTECTED]" via maat.reeusda.gov > >>X-Qmail-Scanner-Rcpt-To: "[EMAIL PROTECTED]" > >>X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.266484 >secs) > >>*** Qmail-Scanner Envelope Details End *** > >> > > > > > > > > > > > >
Re: win32
If it handles exclusions, hell yes. My users are a lot of analysis engineers and I need to be able to exclude some HUGE interim files made during analasys processing. Jim Buttafuoco wrote: [EMAIL PROTECTED]"> I tried for days to get it to work, NO luck. I decided to rewrite the amandad in perl (doesn't need any external programs other than Perl and a few modules). I currently have a VERY alpha version of this working here. I should be ready to release 0.02 next week. Is anyone interested?Jim On Wed, 11 Sep 2002, Galen Johnson wrote: Hello gang,A while back I had sent a request regarding backing up windows machines without having to deal with samba. Someone had responded with the win32 Amanda client on sourceforge. I have looked it up and it seems like it'll do what I want. However, it hasn't been touched in 18 months. Is anyone currently using this with Amanda 2.4.3.b4? I downloaded this package but have been unable to get it to work - anyone using it successfully?*** Qmail-Scanner Envelope Details Begin ***X-Qmail-Scanner-Mail-From: "[EMAIL PROTECTED]" via maat.reeusda.govX-Qmail-Scanner-Rcpt-To: "[EMAIL PROTECTED]"X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.266484 secs)*** Qmail-Scanner Envelope Details End ***
Re: win32
I tried for days to get it to work, NO luck. I decided to rewrite the amandad in perl (doesn't need any external programs other than Perl and a few modules). I currently have a VERY alpha version of this working here. I should be ready to release 0.02 next week. Is anyone interested? Jim > On Wed, 11 Sep 2002, Galen Johnson wrote: > > > Hello gang, > > > > A while back I had sent a request regarding backing up windows machines > > without having to deal with samba. Someone had responded with the win32 > > Amanda client on sourceforge. I have looked it up and it seems like > > it'll do what I want. However, it hasn't been touched in 18 months. Is > > anyone currently using this with Amanda 2.4.3.b4? > > I downloaded this package but have been unable to get it to work - anyone > using it successfully? > > *** Qmail-Scanner Envelope Details Begin *** > X-Qmail-Scanner-Mail-From: "[EMAIL PROTECTED]" via maat.reeusda.gov > X-Qmail-Scanner-Rcpt-To: "[EMAIL PROTECTED]" > X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.266484 secs) > *** Qmail-Scanner Envelope Details End ***
Re: win32
On Tue, 17 Sep 2002 15:58:26 -0400
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> --- In [EMAIL PROTECTED], JC Simonetti <[EMAIL PROTECTED]> wrote:
>
>
>
> >
> > Well... You're right, I got the actual state of the Sourceforge
> project and did not touch to anything to the sources. Everything goes
> well.
> > For your bugs :
> > 1. selfcheck bug is not a bug, it's just that selfcheck is not
> provided in the Win32 version. If you are suck with the amcheck
> errors, do the same thing as me : "selfcheck.c : int main() {return
> 0;}", and if you are lazy compiling such a thing, I've attached it
> here.
> > 2. sendsize crash ? Well... Er... Er... Er... Where ??? I've had
> some problems with sendsize, but it corrected itself with the
> "-udp=10080 -no-exit" parameters to the amandad.exe program. I did not
> examine precisely the source code but the "-no-exit" seems to be very
> important...
> >
> > What I've done with this project? Well... Just got it from
> Sourceforge and installed it on W2K boxes: what I've done is installed
> it as a WinNT service. I am running it with an Amanda 2.4.3b2 server
> on a Linux box, and no errors reported yet (1,5 Go backed up every
> night). Not checked with omre recent versions.
> >
> >
> > --
> > Jean-Christian SIMONETTI email: [EMAIL PROTECTED]
> > SysAdmin Wanadoo Portails phone: (+33)493004911
> > Sophia Antipolis, France
> > --
>
> Are you SURE there are no errors? I tested this yesterday. It
> appears that sendbackup only logs the errors tothe debug file in
> /tmp/amanda. Also, each sendbackup process overwrites this file.
>
> It also appears that this doesn`t support excludes. Amandad reports
> the standard exclude list path, but I couldn,t get it to work.
>
> You previously mentioned that amanda maps the archive bit to the UNIX
> execute bit. It is actually the win32 tar that does this. I believe
> Samba also doed this to help preserve the Windows permissions.
>
> This appears to be early alpha quality software, not ready for
> production. Unfortunately, it also appears to be abandoned :-(
>
> Bruce Osborne
>
I am sure there are no errors. I am currently backing up 6 servers for a total amount
of 2 Go, everything goes perfectly well.
Concerning the exludes, it is written that this feature does not work from now on.
Concerning the NT rights, Samba does NOT preserve them. Samba backs up the bits from
the files, and if their names are in US-ASCII (whoops, I'm french, don't forget the
accentuated characters) the names are also backed up (I've got problems with special
characters translation and no recover possible for some files, due to their names that
had been changed.
And as for the general quality, I think you're right when you speak about alpha
quality. But when I see the smbtar feature, I prefer an alpha quality that works (I
managed to make it work in my environment) rather than a solution that tells me
everyday "? ERRDOS - ERRbadshare opening remote file \EF\EFinfo2.SDC (\EF\)" and that
I am not sure to be able to recover the data I am backing up...
The actual version of Win32 Amanda is yet in development version (not even in unstable
mode, to speak Debian-like). But I prefer this solution, as I managed to make it work,
rather than the smbtar I couldn't make it work correctly.
If someone is interested in going through the development of this client, we might
start the development again... But I cannot do it alone, I do not have enough time.
Re: win32
--- In [EMAIL PROTECTED], JC Simonetti <[EMAIL PROTECTED]> wrote:
>
> Well... You're right, I got the actual state of the Sourceforge
project and did not touch to anything to the sources. Everything goes
well.
> For your bugs :
> 1. selfcheck bug is not a bug, it's just that selfcheck is not
provided in the Win32 version. If you are suck with the amcheck
errors, do the same thing as me : "selfcheck.c : int main() {return
0;}", and if you are lazy compiling such a thing, I've attached it
here.
> 2. sendsize crash ? Well... Er... Er... Er... Where ??? I've had
some problems with sendsize, but it corrected itself with the
"-udp=10080 -no-exit" parameters to the amandad.exe program. I did not
examine precisely the source code but the "-no-exit" seems to be very
important...
>
> What I've done with this project? Well... Just got it from
Sourceforge and installed it on W2K boxes: what I've done is installed
it as a WinNT service. I am running it with an Amanda 2.4.3b2 server
on a Linux box, and no errors reported yet (1,5 Go backed up every
night). Not checked with omre recent versions.
>
>
> --
> Jean-Christian SIMONETTI email: [EMAIL PROTECTED]
> SysAdmin Wanadoo Portails phone: (+33)493004911
> Sophia Antipolis, France
> --
Are you SURE there are no errors? I tested this yesterday. It
appears that sendbackup only logs the errors tothe debug file in
/tmp/amanda. Also, each sendbackup process overwrites this file.
It also appears that this doesn`t support excludes. Amandad reports
the standard exclude list path, but I couldn,t get it to work.
You previously mentioned that amanda maps the archive bit to the UNIX
execute bit. It is actually the win32 tar that does this. I believe
Samba also doed this to help preserve the Windows permissions.
This appears to be early alpha quality software, not ready for
production. Unfortunately, it also appears to be abandoned :-(
Bruce Osborne
mail2web - Check your email from the web at
http://mail2web.com/ .
Re: win32
On Thu, 12 Sep 2002 12:23:25 -0400
Galen Johnson <[EMAIL PROTECTED]> wrote:
> JC Simonetti wrote:
>
> >amrecover is possible. You extract the tarball archive on your backup server and
>upload it to the Windows box, and there you untar it with the WinTar provided with
>Win32 Amanda (different of course from the GNU tar, due to NT file rights...).
> >
> >amrestore is possible, but I don't like the ability of the client to log in as root
>without password on the backup server, so I tested the solution but did not put it in
>production. amrestore is also helped by a GUI written in Python (need to install a
>Python interpreter on your Windows box, easy way but not so easy to automatically
>deploy).
> >
> >
> >
> >
> >>Have you, or will you, put the changes out for others?
> >>
> >>
> >
> >
> >Will be done. See my previous mail ;)
> >
> >
> Can I assume from what you've been saying that you've actually gotten
> the amanda-win32 project from sourceforce to compile properly? What
> about the selfcheck bug? Or sendsize crashes that were reported? these
> questions assume you are using amanda-win32. I've tried contacting the
> current maintainer with no success. All the source files are about 18
> months old and CVS hasn't been touched in as long.
>
> Also, what version of amanda have you gotten it to work with? There was
> a previous response from someone who couldn't get it to work on the more
> recent code.
>
> =G=
>
Well... You're right, I got the actual state of the Sourceforge project and did not
touch to anything to the sources. Everything goes well.
For your bugs :
1. selfcheck bug is not a bug, it's just that selfcheck is not provided in the Win32
version. If you are suck with the amcheck errors, do the same thing as me :
"selfcheck.c : int main() {return 0;}", and if you are lazy compiling such a thing,
I've attached it here.
2. sendsize crash ? Well... Er... Er... Er... Where ??? I've had some problems with
sendsize, but it corrected itself with the "-udp=10080 -no-exit" parameters to the
amandad.exe program. I did not examine precisely the source code but the "-no-exit"
seems to be very important...
What I've done with this project? Well... Just got it from Sourceforge and installed
it on W2K boxes: what I've done is installed it as a WinNT service. I am running it
with an Amanda 2.4.3b2 server on a Linux box, and no errors reported yet (1,5 Go
backed up every night). Not checked with omre recent versions.
--
Jean-Christian SIMONETTI email: [EMAIL PROTECTED]
SysAdmin Wanadoo Portails phone: (+33)493004911
Sophia Antipolis, France
--
<>
Re: win32
JC Simonetti wrote: >amrecover is possible. You extract the tarball archive on your backup server and >upload it to the Windows box, and there you untar it with the WinTar provided with >Win32 Amanda (different of course from the GNU tar, due to NT file rights...). > >amrestore is possible, but I don't like the ability of the client to log in as root >without password on the backup server, so I tested the solution but did not put it in >production. amrestore is also helped by a GUI written in Python (need to install a >Python interpreter on your Windows box, easy way but not so easy to automatically >deploy). > > > > >>Have you, or will you, put the changes out for others? >> >> > > >Will be done. See my previous mail ;) > > Can I assume from what you've been saying that you've actually gotten the amanda-win32 project from sourceforce to compile properly? What about the selfcheck bug? Or sendsize crashes that were reported? these questions assume you are using amanda-win32. I've tried contacting the current maintainer with no success. All the source files are about 18 months old and CVS hasn't been touched in as long. Also, what version of amanda have you gotten it to work with? There was a previous response from someone who couldn't get it to work on the more recent code. =G=
Re: win32
On Thu, 12 Sep 2002 11:16:11 -0400 Jon LaBadie <[EMAIL PROTECTED]> wrote: > On Thu, Sep 12, 2002 at 09:35:57AM +0200, JC Simonetti wrote: > > On Wed, 11 Sep 2002 12:02:09 -0400 (EDT) > > Samuel Nicolary <[EMAIL PROTECTED]> wrote: > > > On Wed, 11 Sep 2002, Galen Johnson wrote: > > > > > > I downloaded this package but have been unable to get it to work - anyone > > > using it successfully? > > > > Well... I was a bit tricky but I managed to make this work with > > Amanda 2.4.3b2 and W2K clients (not NT4). The major problems in fact > > were to transform this slight piece of code into a W2K Service (to make > > it work even if you have not an Administrator account always opened) > > (quite a bit tricky to to find information at Microsoft's). Another > > problem was due to the Windows flag "archive" that seems to be read by > > Amanda exactly like the Unix "executable" flag. > > > > Now I am backuping some W2K servers, in production. Everything goes well :) > > > > Important follow-ups: > > Can you also amrecover/amrestore? amrecover is possible. You extract the tarball archive on your backup server and upload it to the Windows box, and there you untar it with the WinTar provided with Win32 Amanda (different of course from the GNU tar, due to NT file rights...). amrestore is possible, but I don't like the ability of the client to log in as root without password on the backup server, so I tested the solution but did not put it in production. amrestore is also helped by a GUI written in Python (need to install a Python interpreter on your Windows box, easy way but not so easy to automatically deploy). > > Have you, or will you, put the changes out for others? Will be done. See my previous mail ;)
Re: win32
I'll post here a little howto as soon as I find time. Don't hesitate to remind me of that if I forget. (one week could be a correct timeout for me I think if I have not too any problems...) On Thu, 12 Sep 2002 09:01:18 -0500 Tony Shadwick <[EMAIL PROTECTED]> wrote: > Care to share what you went through? I remember there's an exe you have to > run to turn any program into a service (anyserv.exe?) as I've had to do it > for a perl script before. > > Would be nice to get it all under the same backup system. > > On 9/12/02 2:35 AM, "JC Simonetti" <[EMAIL PROTECTED]> wrote: > > > On Wed, 11 Sep 2002 12:02:09 -0400 (EDT) > > Samuel Nicolary <[EMAIL PROTECTED]> wrote: > > > >> On Wed, 11 Sep 2002, Galen Johnson wrote: > >> > >>> Hello gang, > >>> > >>> A while back I had sent a request regarding backing up windows machines > >>> without having to deal with samba. Someone had responded with the win32 > >>> Amanda client on sourceforge. I have looked it up and it seems like > >>> it'll do what I want. However, it hasn't been touched in 18 months. Is > >>> anyone currently using this with Amanda 2.4.3.b4? > >> > >> I downloaded this package but have been unable to get it to work - anyone > >> using it successfully? > > > > > > Well... I was a bit tricky but I managed to make this work with Amanda 2.4.3b2 > > and W2K clients (not NT4). The major problems in fact were to transform this > > slight piece of code into a W2K Service (to make it work even if you have not > > an Administrator account always opened) (quite a bit tricky to to find > > information at Microsoft's). Another problem was due to the Windows flag > > "archive" that seems to be read by Amanda exactly like the Unix "executable" > > flag. > > Now I am backuping some W2K servers, in production. Everything goes well :) > > > > > > -- > > Jean-Christian SIMONETTI email: [EMAIL PROTECTED] > > SysAdmin Wanadoo Portails phone: (+33)493004911 > > Sophia Antipolis, France > > -- >
Re: win32
On Thu, Sep 12, 2002 at 09:35:57AM +0200, JC Simonetti wrote: > On Wed, 11 Sep 2002 12:02:09 -0400 (EDT) > Samuel Nicolary <[EMAIL PROTECTED]> wrote: > > On Wed, 11 Sep 2002, Galen Johnson wrote: > > > > I downloaded this package but have been unable to get it to work - anyone > > using it successfully? > > Well... I was a bit tricky but I managed to make this work with > Amanda 2.4.3b2 and W2K clients (not NT4). The major problems in fact > were to transform this slight piece of code into a W2K Service (to make > it work even if you have not an Administrator account always opened) > (quite a bit tricky to to find information at Microsoft's). Another > problem was due to the Windows flag "archive" that seems to be read by > Amanda exactly like the Unix "executable" flag. > > Now I am backuping some W2K servers, in production. Everything goes well :) > Important follow-ups: Can you also amrecover/amrestore? Have you, or will you, put the changes out for others? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: win32
Care to share what you went through? I remember there's an exe you have to run to turn any program into a service (anyserv.exe?) as I've had to do it for a perl script before. Would be nice to get it all under the same backup system. On 9/12/02 2:35 AM, "JC Simonetti" <[EMAIL PROTECTED]> wrote: > On Wed, 11 Sep 2002 12:02:09 -0400 (EDT) > Samuel Nicolary <[EMAIL PROTECTED]> wrote: > >> On Wed, 11 Sep 2002, Galen Johnson wrote: >> >>> Hello gang, >>> >>> A while back I had sent a request regarding backing up windows machines >>> without having to deal with samba. Someone had responded with the win32 >>> Amanda client on sourceforge. I have looked it up and it seems like >>> it'll do what I want. However, it hasn't been touched in 18 months. Is >>> anyone currently using this with Amanda 2.4.3.b4? >> >> I downloaded this package but have been unable to get it to work - anyone >> using it successfully? > > > Well... I was a bit tricky but I managed to make this work with Amanda 2.4.3b2 > and W2K clients (not NT4). The major problems in fact were to transform this > slight piece of code into a W2K Service (to make it work even if you have not > an Administrator account always opened) (quite a bit tricky to to find > information at Microsoft's). Another problem was due to the Windows flag > "archive" that seems to be read by Amanda exactly like the Unix "executable" > flag. > Now I am backuping some W2K servers, in production. Everything goes well :) > > > -- > Jean-Christian SIMONETTI email: [EMAIL PROTECTED] > SysAdmin Wanadoo Portails phone: (+33)493004911 > Sophia Antipolis, France > --
Re: win32
On Wed, 11 Sep 2002 12:02:09 -0400 (EDT) Samuel Nicolary <[EMAIL PROTECTED]> wrote: > On Wed, 11 Sep 2002, Galen Johnson wrote: > > > Hello gang, > > > > A while back I had sent a request regarding backing up windows machines > > without having to deal with samba. Someone had responded with the win32 > > Amanda client on sourceforge. I have looked it up and it seems like > > it'll do what I want. However, it hasn't been touched in 18 months. Is > > anyone currently using this with Amanda 2.4.3.b4? > > I downloaded this package but have been unable to get it to work - anyone > using it successfully? Well... I was a bit tricky but I managed to make this work with Amanda 2.4.3b2 and W2K clients (not NT4). The major problems in fact were to transform this slight piece of code into a W2K Service (to make it work even if you have not an Administrator account always opened) (quite a bit tricky to to find information at Microsoft's). Another problem was due to the Windows flag "archive" that seems to be read by Amanda exactly like the Unix "executable" flag. Now I am backuping some W2K servers, in production. Everything goes well :) -- Jean-Christian SIMONETTI email: [EMAIL PROTECTED] SysAdmin Wanadoo Portails phone: (+33)493004911 Sophia Antipolis, France --
Re: win32
On Wed, 11 Sep 2002, Galen Johnson wrote: > Hello gang, > > A while back I had sent a request regarding backing up windows machines > without having to deal with samba. Someone had responded with the win32 > Amanda client on sourceforge. I have looked it up and it seems like > it'll do what I want. However, it hasn't been touched in 18 months. Is > anyone currently using this with Amanda 2.4.3.b4? I downloaded this package but have been unable to get it to work - anyone using it successfully?
win32
Hello gang, A while back I had sent a request regarding backing up windows machines without having todeal with samba. Someone had responded with the win32 amanda client on sourceforge. I have looked it up and it seems like it'll do what I want. However, it hasn't been touched in 18 months. Is anyone currently using this with amanda 2.4.3.b4? =G=
amindexd EOF problem - win32 client
Has anyone been able to restore with the amanda-win32 client? The backup appears to be going well but when I try to restore I am unable to pull up the index through the amrestore-gui client. here is the amindexd.debug file amindexd: debug 1 pid 8506 ruid 28 euid 28 start time Mon Jul 22 15:13:17 2002 amindexd: version 2.4.3b3 < 220 mentat AMANDA index server (2.4.3b3) ready. > SECURITY USER root bsd security: remote host mec-denver.mcguireinc.com user root local user amanda amandahosts security check passed < 200 Access OK > DATE 2002-07-22 < 200 Working date set to 2002-07-22. > SCNF testing < 200 Config set to testing. > HOST mec-denver < 200 Dump host set to mec-denver. > DISK /mnt_d/ - 2002-07-22 0 testTape2 1 - 2002-07-19 0 testTape1 1 < 200 Disk set to /mnt_d/. > TAPE < 200 /dev/tape > ORLD / Uncompress command: /bin/gzip -dc '/usr/adm/amanda/test/index/mec-denver/_mnt__d_/20020722_0.gz' 2>/dev/null | sort > '/usr/adm/amanda/test/index/mec-denver/_mnt__d_/20020722_0' < 200- Opaque recursive list of / < 200 Opaque recursive list of / ? unexpected EOF Removing index file: /usr/adm/amanda/test/index/mec-denver/_mnt__d_/20020722_0 amindexd: pid 8506 finish time Mon Jul 22 15:13:17 2002 ~ It looks like the EOF is the problem does anyone know what could cause that? Gene Heskett wrote: >On Thursday 18 July 2002 12:33, Marc Mengel wrote: > > >>On Thu, 2002-07-18 at 10:39, Bruce Lilly wrote: >> >> >>>[EMAIL PROTECTED] wrote: >>> >>> >>>>Dear amanda-users, >>>> >>>>Has anyone given any thought to (or done) a port of amandad to >>>>Windows-XP?] >>>> >>>> >>See: >> http://sourceforge.net/projects/amanda-win32/ >>They have been seeking beta testers, etc. for some time. >>I suspect their stuff runs on XP, but I also suspect the >>folks on that project know lots more about Windows variants >>than I do... >> >>Amanda-hackers -- shouldn't we have a link to their project on the >>main Amanda page, next to the SAMBA links? >> >>Marc >> >> > >Much as we'ed like to be a bit political here, this being primarily >a *x type list, I have to agree with Marc. Only by inviting the >windows users in can we make it 100% compatible on a faster >timetable, and widen the userbase of amanda. > >And the best way is to put that link right under the samba link(s). >It should be wrapped up in some text that encourages said windows >user to join this list and contribute their experience and >expertise to other windows users coming in later. > > >
RE: Win32 Amanda Client on Sourceforge?
I downloaded it and installed it, everything seemed ok until I ran amcheck. It appears to have no support for the SELFCHECK command. So I'm sticking with Samba until I have time to play with it again. Advance warning of backup problems is too important to me to give up for a native client. > -Original Message- > From: Morse, Richard E. [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 27, 2002 7:19 PM > To: '[EMAIL PROTECTED]' > Subject: Win32 Amanda Client on Sourceforge? > > > Hi! How stable is the Win32 Amanda Client found on > SourceForge? I have a few > NT/Win2K boxes that I would like to add to my backup, and I'm > looking at the > different options available... > > Thanks, > Ricky > > - > Richard MorseSystem Administrator > MGH Biostatistics Center 50 Staniford St. Rm 560 > [EMAIL PROTECTED] 617/724-9830 >
Win32 Amanda Client on Sourceforge?
Hi! How stable is the Win32 Amanda Client found on SourceForge? I have a few NT/Win2K boxes that I would like to add to my backup, and I'm looking at the different options available... Thanks, Ricky - Richard MorseSystem Administrator MGH Biostatistics Center 50 Staniford St. Rm 560 [EMAIL PROTECTED] 617/724-9830
Status of the amanda-win32 project?
Saw it on Sourceforge: http://sourceforge.net/projects/amanda-win32/ Anyone tried it? -- |Colin Smith: [EMAIL PROTECTED] |
Re: [Amanda-users] Win32 client portrange...
On Wed, Dec 12, 2001 at 08:46:28AM +1100, Jason Thomas wrote: > no you just want the udp port that it listens on. and maybe the tcp > port. try: > start amandad -udp=10800 -no-exit sorry wrong port: 10080 msg08936/pgp0.pgp Description: PGP signature
Re: [Amanda-users] Win32 client portrange...
On Tue, Dec 11, 2001 at 10:53:40AM -0500, Chris Noon wrote: > Hello all, > I'm trying to get the win32 client up and running. I followed Kurt Yoder's > instructions (below), but amcheck is still timing out. I'm almost certain > that it has to do with the tcp/ip ports amanda is using. My server was > compiled with the following: > --with-portrange=5,50100 --with-udpportrange=850,860 > > I'm running the win32 client with the following command: > start amandad -tcp=5,50100 -udp=850,860 -no-exit no you just want the udp port that it listens on. and maybe the tcp port. try: start amandad -udp=10800 -no-exit have a look at the code for the win32 client the server is trying to connect to the amanda port which is from memory 10800. so you need the win32 client to listen on that port. tcp/udp don't take a range they specify the port to bind to. but only for debugging purposes. you also need to define the ROOT_DRV variable, I did it in my autoexec.bat: set ROOT_DRV=c: this is a pw32 environment variable. you may want to rebuild the win32 client and specify the port range to configure. the amanda win32 to client is built using pw32 not cygwin. http://pw32.sf.net I think. its almost the same as cygwin but free with no gui installer. zip files! good luck. > I've tried many permutations of that command, but with no luck. Any one > have some insight on how to correctly specify tcp/udp ports to the win32 > client? > > Many thanks in advance, > > Chris Noon > [EMAIL PROTECTED] msg08929/pgp0.pgp Description: PGP signature
Win32 client portrange...
Hello all, I'm trying to get the win32 client up and running. I followed Kurt Yoder's instructions (below), but amcheck is still timing out. I'm almost certain that it has to do with the tcp/ip ports amanda is using. My server was compiled with the following: --with-portrange=5,50100 --with-udpportrange=850,860 I'm running the win32 client with the following command: start amandad -tcp=5,50100 -udp=850,860 -no-exit I've tried many permutations of that command, but with no luck. Any one have some insight on how to correctly specify tcp/udp ports to the win32 client? Many thanks in advance, Chris Noon [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Kurt Yoder Sent: Wednesday, October 17, 2001 2:29 PM To: Jon LaBadie Cc: [EMAIL PROTECTED] Subject: Re: Win32 client setup Jon LaBadie wrote: > I did not feel the installation instructions were too clear. > Maybe I have not found the correct ones. Pointers? This is very true; I had to fiddle a bit to make it work. Here's what I did: -download the "amanda-clients-bin" latest zip file and unzip it -make a folder "usr" in one of your drives -move the amanda folder into it; path to binaries should be \usr\amanda\bin and so forth -copy pw32.8.dll from the "bin" folder to "libexec" and "sbin" folders -copy \usr\amanda\share\amanda-win32-clients\.amandahosts to \usr\amanda\etc\amanda\ -add your amanda master to the \usr\amanda\etc\amanda\.amandahosts -start your amanda test: run \usr\amanda\libexec\rc.amandad.bat (an empty dos window should pop up) -add entries to the amanda master's disklist; use the form " /mnt_ ", one for each disk on each nt host; my disklist entry for my nt host looks like "gandalf /mnt_c user-tar", etc -run amcheck on the master, make sure you see the server connecting on the nt host; you should see its name show up in the window on the nt machine that rc.amandad.bat opened -if the test was successful, close rc.amandad.bat and install \usr\amanda\libexec\amandad.exe as a service named "amandad" (use srvany.exe from the nt resource kit for this); service should be a system account and start up automatically -suggested registry entries for the amandad service are in \usr\amanda\share\amanda\amandad.reg; double click on this file to install its keys -make sure the drive letter and path in the registry's hklm/system/ccs/services/amandad/parameters key matches where amandad.exe is actually installed -start up the amandad service > Two questions, does the W32 client anticipate the cygwin package > is installed on the M$ box? Though I did not see it stated, I > got that impression. Cygwin is not necessary. > Second, I came across a page describing environment variables > that need be set. Something about the PW32 environment (Posix > Win 32??). Are these set on the unix amanda server or on the > client when started from the service routines? I didn't set any environment variables on the NT machine.
Re: Win32 client setup
Jon LaBadie wrote: > I did not feel the installation instructions were too clear. > Maybe I have not found the correct ones. Pointers? This is very true; I had to fiddle a bit to make it work. Here's what I did: -download the "amanda-clients-bin" latest zip file and unzip it -make a folder "usr" in one of your drives -move the amanda folder into it; path to binaries should be \usr\amanda\bin and so forth -copy pw32.8.dll from the "bin" folder to "libexec" and "sbin" folders -copy \usr\amanda\share\amanda-win32-clients\.amandahosts to \usr\amanda\etc\amanda\ -add your amanda master to the \usr\amanda\etc\amanda\.amandahosts -start your amanda test: run \usr\amanda\libexec\rc.amandad.bat (an empty dos window should pop up) -add entries to the amanda master's disklist; use the form " /mnt_ ", one for each disk on each nt host; my disklist entry for my nt host looks like "gandalf /mnt_c user-tar", etc -run amcheck on the master, make sure you see the server connecting on the nt host; you should see its name show up in the window on the nt machine that rc.amandad.bat opened -if the test was successful, close rc.amandad.bat and install \usr\amanda\libexec\amandad.exe as a service named "amandad" (use srvany.exe from the nt resource kit for this); service should be a system account and start up automatically -suggested registry entries for the amandad service are in \usr\amanda\share\amanda\amandad.reg; double click on this file to install its keys -make sure the drive letter and path in the registry's hklm/system/ccs/services/amandad/parameters key matches where amandad.exe is actually installed -start up the amandad service > Two questions, does the W32 client anticipate the cygwin package > is installed on the M$ box? Though I did not see it stated, I > got that impression. Cygwin is not necessary. > Second, I came across a page describing environment variables > that need be set. Something about the PW32 environment (Posix > Win 32??). Are these set on the unix amanda server or on the > client when started from the service routines? I didn't set any environment variables on the NT machine.
Re: Win32 client setup
Wayne Richards wrote: > > I've got the Win32 client setup and running in a console window on an NT box > running NT4.0 SP6a. It works well. I've also setup amanda as a service > according to the instructions. However, the service does not start. It hangs > for a while and then gives an error: > > Error 2186: The service is not responding to the control function. > > Now, I went to the MS support site and found the 2186 error. The solution > given was to upgrade to the most current SP. So I checked my machine and it > had SP6a, but there was a hotfix that wasn't loaded (Q246009), so I loaded it > and restarted the system. > > The service is to run under the user 'amanda' as a local user with > administrative rights including the right to 'login as a service'. It's setup > as a 'Manual' service so it does not try to start at boot, even though that's > what I would prefer. The server is a Sun E3000 and has no problem backing up > the NT box when the client is running in the foreground in a console window or > command window. > > Has anyone had any luck with the Win32 client as a service? > > I found the client at: > http://sourceforge.net/projects/amanda-win32/ Yes, I've been using it for several weeks. It seems it's a bit buggy though. I've had it refuse to work on two machines until I rebooted. Then it works for awhile, but eventually does the same thing a few days later, and I need to reboot again. I've also had one of the machines refuse to work (Dr Watson errors) until I deinstalled Python and WxPython, which are necessary for the client's amrestore; weird. I have my service running using the "system account", with "interact with the desktop" left unchecked. I would try this first. I also have my service starting up automatically at bootup. Also, don't forget to edit the registry settings of the service to point to the correct path of the amanda installation. -Kurt
Win32 client setup
I've got the Win32 client setup and running in a console window on an NT box running NT4.0 SP6a. It works well. I've also setup amanda as a service according to the instructions. However, the service does not start. It hangs for a while and then gives an error: Error 2186: The service is not responding to the control function. Now, I went to the MS support site and found the 2186 error. The solution given was to upgrade to the most current SP. So I checked my machine and it had SP6a, but there was a hotfix that wasn't loaded (Q246009), so I loaded it and restarted the system. The service is to run under the user 'amanda' as a local user with administrative rights including the right to 'login as a service'. It's setup as a 'Manual' service so it does not try to start at boot, even though that's what I would prefer. The server is a Sun E3000 and has no problem backing up the NT box when the client is running in the foreground in a console window or command window. Has anyone had any luck with the Win32 client as a service? I found the client at: http://sourceforge.net/projects/amanda-win32/ --- Wayne Richards Phone: 330 796-4462 Goodyear Tech CenterFax:330 796-3947 Department 431A e-mail: [EMAIL PROTECTED] PO Box 3531 Akron, OH 44309-3531
