david_z

Quote: But my big problem is that once you get around 2.5 million files, you'll have trouble getting a full backup at all. I've been unable to get a full backup of my user home directories (400GB, 2.6 million files) at all. After spending all night copying files, Retrospect eventually gives up because it is unable to allocate enough memory when building the snapshot. One of our backup jobs is about 1.5 million files and about 550GB and we don't have problems with it. Our server is just a simple Windows XP Pro Pentium 4 2.8 with 1GB ram. It's just a cheap dell workstation that we've installed an Adaptec 29160 card and an Intel gigabit Ethernet card in. We use an Exabyte 10 tape autoloader. Just thought I'd add my 2 cents... David

Just as an update... I've been reading through all the other posts on the forum related to the 504 error with linux clients, and they suggest to update to the latest version because it was a known bug that was fixed. But I have newer versions that what is noted in the posts, and I still have the problem. Thanks! David

I am running Retrospect Multi-Server 7.5.370 with Driver Update and HotFix version 7.5.10.104 on a Windows XP Pro machine. It's attached to a Exabyte VXA-172 10 Tape SCSI Autoloader. Our backups have been working fine. We just recently decided to review some of the processes to make them better. One that we have tried to fix is the backup of a linux server. Before we were using SAMBA and mapping a drive to it on the Backup Server. We decided to give the Client software a try. So I installed retroclient-75_linux.rpm (Client Version 7.5.112) on our Fedora Core 4 Server. Everything started off great but about halfway into the backup it stopped with Code: Trouble reading files, error -540 (trouble creating service) Here is the log from the linux machine: Code: [root@itserver client]# cat /var/log/retroclient.log 1174507727: ConnStartListen: starting thread ConnStartListen for 127.0.0.1:0 1174507727: iplud: bound to address 0.0.0.0 1174507727: ipludAddMembership: adding membership for 0.0.0.0 1174507733: IPNSRegister(1): registered: "itserver.domain.com"/"2443df430f7990ba" 1174507733: ConnStartListen: starting thread ConnStartListen for 192.168.100.194:0 1174507739: IPNSRegister(1): registered: "itserver.domain.com"/"d6437525653ffe25" 1174509337: Connection established by 192.168.100.189:4320 1174509348: IPNSRegister(0): registered: "IT Server"/"d6437525653ffe25" 1174509358: ConnReadData: Connection with 192.168.100.189:4320 closed 1174509810: Connection established by 192.168.100.189:4331 1174510415: ConnReadData: Connection with 192.168.100.189:4331 closed 1174510428: Connection established by 192.168.100.189:4356 1174510442: ConnReadData: Connection with 192.168.100.189:4356 closed 1174510451: Connection established by 192.168.100.189:4359 1174510500: ConnReadData: Connection with 192.168.100.189:4359 closed 1174510504: Connection established by 192.168.100.189:4362 1174510534: ConnReadData: Connection with 192.168.100.189:4362 closed 1174510607: Connection established by 192.168.100.189:4370 1174510770: ConnReadData: Connection with 192.168.100.189:4370 closed 1174511461: Connection established by 192.168.100.189:4387 1174513768: TransStart: waitpid failed with error 10 1174513769: ConnReadData: Connection with 192.168.100.189:4387 closed 1174513769: Connection established by 192.168.100.189:4438 1174513783: connTcpConnection: invalid code found: 111 1174513784: ConnReadData: Connection with 192.168.100.189:4438 closed I did some digging and I think that it died on a file that is constantly held open by a end user's computer via samba share. I understand that it probably can't copy a file that is open, but shouldn't it just skip it and move on? Thank you for any help!! David