Jump to content

rsmogul

Members
  • Content count

    13
  • Joined

  • Last visited

Everything posted by rsmogul

  1. I'm getting an "error -540 (trouble creating service)" when trying to backup a server running Redhat Enterprise Linux rel. 4. Here is the clip from the log: - 3/3/2008 7:07:23 PM: Copying /home on xxxx While scanning volume home, Folder /home/homes/engineering/xxx/.p..., Scanning incomplete, error -1101 (file/directory not found) Folder /home/homes/engineering/xxx/.p..., Scanning incomplete, error -1101 (file/directory not found) Folder /home/homes/engineering/xxxx..., Scanning incomplete, error -1101 (file/directory not found) File "/home/applesharefolder/graphics/graphics/JP's Folder/Compilations/90 Millas/04 Píntame De Colores.mp3": can't read, error -1101 (file/directory not found) File "/home/applesharefolder/graphics/graphics/JP's Folder/Compilations/90 Millas/06 Yo No Cambiaría.mp3": can't read, error -1101 (file/directory not found) File "/home/applesharefolder/graphics/graphics/JP's Folder/Compilations/90 Millas/07 Bésame.mp3": can't read, error -1101 (file/directory not found) File "/home/applesharefolder/graphics/graphics/JP's Folder/Compilations/90 Millas/11 Volveré.mp3": can't read, error -1101 (file/directory not found) File "/home/applesharefolder/graphics/graphics/show/?men'sbb640.jpg": can't read, error -1101 (file/directory not found) Trouble reading files, error -540 (trouble creating service) 3/3/2008 7:16:01 PM: Execution incomplete Remaining: 1306194 files, 335.1 GB Completed: 294 files, 83.2 MB Performance: 85.9 MB/minute Duration: 00:08:37 (00:07:39 idle/loading/preparing) The particulars of my install: Windows 2003 Server Retrospect Multi Server v. 7.5.508 Driver Update and Hot Fix, version 7.5.13.100 We are running the Retrospect Client for Red Hat version 7.5.112 We actually have 3 different Linux servers all running the same Release of Redhat that have this problem. We also have run into the redhat client spamming "User Deferred", which we have solved by turning the client off and turning it back on. Hopefully someone can help us with this issue, we are needing to spend some more money on our backup solution and being able to backup these linux servers is a requirement. If we can get retrospect to work we will buy another server version, but if we cannot get it to work we will have to look elsewhere for for a solution. Thanks for any help!
  2. Cross posting in this split thread, since I muddied this one up: Ok, might have figure out what my problem was. DNS The clients need to be able to find the server by the DNS. We needed a record in DNS for the server and a reverse lookup. Once we added those records, I can see Sources. Now, I'll cross my fingers and see if I continue to see them after I get these scripts built.
  3. rsmogul

    Latest Issue - Can't communicate

    Ok, might have figure out what my problem was. DNS The clients need to be able to find the server by the DNS. We needed a record in DNS for the server and a reverse lookup. Once we added those records, I can see Sources. Now, I'll cross my fingers and see if I continue to see them after I get these scripts built.
  4. (split topic) When this problem first cropped up for me, i was running 10.4 server, and the "restart" retrospect engine didn't do anything in that OS. If I rebooted enough times the clients would show up again. After upgrading to 10.5.6 I can restart the engine from system preferences, but I haven't gotten the clients to show up for any length of time. I'll be curious to see if yours stays working.
  5. rsmogul

    Latest Issue - Can't communicate

    Yes, I can see clients on a different intel mac. FYI, I took the network patch cable out of my Windows 7.6 Retrospect Server and plugged it into the Mac 8 Retrospect server and still can't see any clients. Just to try to eliminate network hardware from possible causes list. Today, I reinstalled the 10.5 server and Retro 8. Still suffering from the problem of no clients. I briefly saw mutlicast clients, but cannot see those now.
  6. rsmogul

    Latest Issue - Can't communicate

    Ok, looks like it was configured "wrong". But i'm not sure how this happened. In "Preferences" under "Network" there is a "Default" connection. Looks like your IP address for the server should show up in the Connection Column. On my First Retrospect Engine it was just a dash - On the 2nd Retrospect Engine it had the machine IP. So I added another connection and chose the IP from the drop down. I deleted the "default" connection and set up the subnet addresses and masks for this new connection. I can now see the sources on the network. Could have something to do with there being 2 NIC's in the Xserve, and that I was running on the 2nd NIC. Not sure, but maybe this will help someone else with the problem. *********Actually, nevermind. This didn't seem to fix the issue. I think I looked at Sources on my working server. Sources are still not coming up on my First Retrospect Engine. Back to the drawing board.***********
  7. rsmogul

    Latest Issue - Can't communicate

    Ok, sure more specific. I'm discussing the First Retrospect Engine Machine, which was formerly a 10.4 server running Retrospect 6.1. Upgraded to retrospect 8 and at first it saw the "sources" or "clients" or "machines". Then it just up and stopped seeing the clients. So I upgraded to 10.5 server, an erase and install. As well as a fresh install of Retro 8. Still no "sources" or "clients" or "machines". We have over 100 machines on our network with the retrospect client installed. A mix of Windows XP, Mac OS, and Linux. These are currently being backed up by Retrospect 7.6 for Windows. I loaded a second 10.5 server up with retrospect 8, it seems to be able to see clients...but I haven't really set up a backup job with this one. (Yeah, I'll try that out...maybe it will stop working too.) We have as an example subnets like this: It's one big network with those vlans. 192.168.26.x 192.168.28.x 192.168.29.x 192.168.30.x 192.168.31.x Could be an incorrect config. At this point if I'm the only one in the world having the problem it would probably be something I'm doing wrong. I've gotten busy at work, so haven't been messing with this 24/7...hopefully freed up some time to look at backups again. So FYI: This thread started out with people having the same issue that I was having. Apparently they were fixed by the latest patch? (I'm running the latest right now.) We've been running some flavor of retrospect for more than 5 years. It's ok for what it is. We sure like the proactive backups...those are nice for laptop users.
  8. rsmogul

    Latest Issue - Can't communicate

    CallmeDave--The machines are on different subnets. But the one I'm having an issue with was formerly a retrospect 6.1 multiserver. With no issues. Now it has been wiped clean and installed fresh, and still has issues. As far as I know, there have been no changes to the network ports.
  9. rsmogul

    Latest Issue - Can't communicate

    Upgraded(erase and install option) my Mac OSX server from 10.4 to 10.5.6. Installed the retrospect engine 8.0.608.1...added the subnets and no clients are showing up. I have a 2nd engine installed on a DIFFERENT 10.5.6 machine and the clients do show up. Any ideas on this one?
  10. rsmogul

    Latest Issue - Can't communicate

    Looks like even after the 608 upgrade the sources still cannot be found. Uninstalled/reinstalled the engine. Deleted preferences. Just an update...
  11. rsmogul

    Latest Issue - Can't communicate

    I'm getting this same behavior. Clients that were previously setup cannot be communicated with. If I manually(enter IP) add them they start working again. If I try to scan for new sources to add, using either "Use subnet broadcast" or "Use multicast" it returns NO clients now. Just wanted to add to the reports...
  12. Thank you very much for this AndrewA. I SWEAR I searched for this error on the forums before posting and did not get the thread you linked as a result. Just so you know I wasn't being lazy. Thank you again, I'm going to try the work around in that other thread.
  13. Anyone know anything about this? Is retrospect just not good for backing up Linux? The error I'm getting when backing up is specifically a WINDOWS client error, and I'm not using a windows client. This is a paid for version of Redhat Linux too.
×