I have set up amanda on our Fedora Core 6 machine and am able to back up correctly on there. I installed the Windows Client on our 2003 server and it passes the amcheck. I thought I had achieved success, however when I try to do an amdump i get a timeout on trying to estimate the size of the dump on the windows server and nothing gets written to the vtape from the windows server. Has anyone ...
What version of Windows client are you using?
Please check sendsize logs on the Windows client directory C:/Cygwin/tmp/amanda/
Please post the contents of sendsize logs if you need help in figuring out the problem.
Thanks,
Paddy
Here is the sendsize debug file. I see there is an error about an illegal seek - but i dont know how to interpret it. It appears that gnutar gets the correct files sizes....
endsize: debug 1 pid 5284 ruid 3199 euid 3199: start at Thu Feb 22 00:45:05 2007
sendsize: version 2.5.1p3
Reading conf file "/etc/amanda/amanda-client.conf".
Reading conf file "/etc/amanda/DailySet1/amanda-...
>sendsize[3480]: gnutar: error opening >/var/lib/amanda/gnutar-lists/galinda.qdtechnology .com_cygdrive_c_amanda_pickup_ 0: No >such file or directory
is there a directory on the server called /var/lib/amanda/gnutar-lists? If so, can amandabackup user read/write to it?
Well I finally gave up and started using SAMBA. Not the way I wanted to do it but I just cant get the windows client to work!
Has anybody gotten it to?
-A
I had a similar error in my backup summaries, and it turns out that it was a configuration issue on the server side. There were no errors in the sendsize log file, aside from a few errors regarding file paths being too long. Turns out I had specified "root" instead of "amandaroot" as the username in /etc/amandahosts on the server for my windows hosts.
Are you still having this problem?
I changed our "etimeout" to something like 3600 to scan our 150GB fileserver, and it still timed out.
Then I broke the server up into multiple DLEs in addition to the extended timeout and it seemed to work better. For example, instead of using:
f:/some/file
I used:
f:/some/file/here
f:/some/file/there
f:/some/file/fun
Not sure...
Hi!
I have a similar problem. my case is that the log backup returns the error:
planner: ERROR Request to 172.20.0.223 failed: timeout waiting for REP
I changed the etimeout but it did not solve the problem. I have two machines, one has windows XP (in spanish) and other is Windows 2000 (in English) and backup only works on Windows 2000.
The logFile is:
Quote:...
garaemon garaemon is offline replied 3 months, 1 week ago
Hi!
I have a similar problem. my case is that the log backup returns the error:
planner: ERROR Request to 172.20.0.223 failed: timeout waiting for REP
I changed the etimeout but it did not solve the problem. I have two machines, one has windows XP (in spanish) and other is Windows 2000 (in English) and backup only works on Windows 2000.
The logFile is:
Quote:...
Well I finally gave up and started using SAMBA. Not the way I wanted to do it but I just cant get the windows client to work! Has anybody gotten it to? -A
What version of Windows client are you using? Please check sendsize logs on the Windows client directory C:/Cygwin/tmp/amanda/ Please post the contents of sendsize logs if you need help in figuring out the problem. Thanks, Paddy
>sendsize[3480]: gnutar: error opening >/var/lib/amanda/gnutar-lists/galinda.qdtechnology.com_cygdrive_c_amanda_pickup_ 0: No >such file or directory is there a directory on the server called /var/lib/amanda/gnutar-lists? If so, can amandabackup user read/write to it?
Are you still having this problem? I changed our "etimeout" to something like 3600 to scan our 150GB fileserver, and it still timed out. Then I broke the server up into multiple DLEs in addition to the extended timeout and it seemed to work better. For example, instead of using: f:/some/file I used: f:/some/file/here f:/some/file/there f:/some/file/fun Not sure if that is a good idea, but it worked, though it is incredibly...
Hi! I have a similar problem. my case is that the log backup returns the error: planner: ERROR Request to 172.20.0.223 failed: timeout waiting for REP I changed the etimeout but it did not solve the problem. I have two machines, one has windows XP (in spanish) and other is Windows 2000 (in English) and backup only works on Windows 2000. The logFile is: Quote: Zmanda Windows Client Version 2.6 Zmanda Windows Client, Copyright 2006-2007 Zmanda...
Hi! I have a similar problem. my case is that the log backup returns the error: planner: ERROR Request to 172.20.0.223 failed: timeout waiting for REP I changed the etimeout but it did not solve the problem. I have two machines, one has windows XP (in spanish) and other is Windows 2000 (in English) and backup only works on Windows 2000. The logFile is: Quote: Zmanda Windows Client Version 2.6 Zmanda Windows Client, Copyright 2006-2007 Zmanda...
Another client of mine has passed away this morning.... Another client of mine has passed away this morning. when my current client passes, that'll be two this week (if she passes this week). 9:37 AM Aug 6th, 2008 from web
Novo Windows Client TechCenter: O Windows Client... Novo Windows Client TechCenter: O Windows Client TechCenter agora é a nova página inicial da série Springboa.. http://tinyurl.com/5nbqro
07:59 PM June 09, 2008
from twitterfeed
Novo Windows Client TechCenter: O Windows Client... Novo Windows Client TechCenter: O Windows Client TechCenter agora é a nova página inicial da série Springboa.. http://tinyurl.com/5nbqro
7:59 PM Jun 9th from twitterfeed
@ evernote I used evernote on Windows mobile, iPod... @ evernote I used evernote on Windows mobile, iPod touch, Windows client, and on Linux using the web client. #evernote_scansnap about 10 hours ago from Seesmic
Thread profile page for "Windows Client Passes AMCHECK But..." on http://www.zmanda.com.
This report page is a snippet summary view from a single thread "Windows Client Passes AMCHECK But...", located on the Message Board at http://www.zmanda.com.
This thread profile page shows the thread statistics for: Total Authors, Total Thread Posts, and Thread Activity