Jump to content

p_smith

Members
  • Content count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About p_smith

  • Rank
    Occasional Forum Poster
  1. I have two similar desktop computers running Retrospect 5.5 under Win 2000 SP4. I am attempting to make backups from the two desktop computers to backup files that are stored on a file server elsewhere on the LAN. It is a push process from the desktop computers, each running Retrospect, rather than a client process. One desktop computer works every time, and the other desktop computer fails with a variety of errors. The two computers have identical network cards, drivers, protocols, network settings (DHCP from router), user priveleges, and file sharing permissions, so far as I know (I have checked several times). I am doing immediate backups, no script, no login. One of the computers works fine. The other one experiences a variety of errors, including: Before I can start the backup, I sometimes get a file open error -1100 (can't open backup file on remote computer). Sometimes it can create / open the backup file successfully. In that case it always appears to write the backup set completely without errors, but during the compare process it exhibits several types of errors: A chunk error A communications error. in which the compare hangs the computer runnint Retrospect and the log file contains entries like the following: Trouble reading: "1-Backup Set B" (50437), error -102 (trouble communicating) Trouble reading: "1-Backup Set B" (50511), error -102 (trouble communicating) Trouble positioning: "1-Backup Set B" (50511), error -102 (trouble communicating) Sometimes, but rarely, it runs all the way through the compare process and then reports compare errors, one of which is always the file RetroSnp.dat. If it makes it that far, when I try to add on to the backup set or restore, it says the catalog is damaged, and when I try to repair it, the software hangs and I have to reboot the computer. Nice variety of symptoms, huh? All of this seems to me like a network communication problem. Retrospect works fine storing the backup file locally. It fails only with a network file. I have read Dantz' article on disk backup network problems and done everything mentioned other than reinstalling the OS. I have reinstalled Restrospect, reinstalled all network software such as protocols, exchanged network cards (they are both Linksys LNE100TX ver. 5), moved NICs to different slots, reinstalled NIC drivers, exchanged cables, exchanged ports on the router, exchanged memory modules, and deinstalled all Microsoft hot fixes. Ordinary network operations such as file sharing, reading and writing work fine. According to Dantz, sometimes the high spead streaming can be more demanding and lead to troubles. All "normal" network operations like file sharing and file transfers using Windows Explorer work fine betweem all computers on the network. Does anyone have any ideas of what I could try short of reinstalling the OS? I will try that if desperate, but needless to say, I would prefer a quicker fix. Is it possible that disk drive cables could be causing the problem? Why would it allow writing to but not reading from the network disk? Nate, we discussed this about 6 months ago. Then it was only the problem of opening the remote file. Now, with persistence, it has gone past that into a whole variety of things.
  2. Thanks, Natew. Yes, that helps. Let's call the troublesome local computer A, the backup computer B, and another local computer C. I was able to save the backup set from A onto another shared volume on a differerent computer C. I cannot save the backup set from A to any volume on the backup computer, B. I can save a backup set to the backup computer B from the other local computer C. So it looks like computer A has the problem. In addition, I observe that computer A maintains a list of folders visible at the top level in the "My Network Places" that computer A previously accessed by a share. I cannot delete those pseudo folders (shortcuts?), even if the folders and/or the shares no longer exist. I'll conjecture that this retention of old folders in the list is the cause of a confilct. Any ideas how I can make that retention behavior go away?
  3. Yes, thank you, I did try mapping it as a drive, and it made no difference. Retrospect always fails (1101), and Windows always works to create files on the remote drive. Another push computer with what i think is an identical configuration works with Retrospect without the drive mapping. I should state again that Retrospect does create a small 2 KB file, "Backup Set A.rbf", on the remote drive before it fails with the 1101 error. This leads me to conjecture that it may not be the catalog / save-set file itself but something else that is hanging. Perhaps it is a log file or something. The 1101 error does not specify either the file name or the location of the file that is giving trouble. The error message is not very helpful.
  4. Ah, so my workaround will not back up the registry then. I guess I will try the client. Thanks again. I'll let you know if it works. May be a couple of days.
  5. Nate, Thanks for the reply. Unfortunately, logging into a volume does not seem to work, at least on my computer as I understand it. Recall that I am running Retrospect Pro 5.5 on the local machine, and I am trying to push the backup to a file on the remote machine that has shared folders. There are two problems with logging in. First, I think 5.5 does not permit changing properties of volumes as you suggested. Second, when I identify the remote (network) volume and put it in the local Retrospect's volume database, it basically makes that volume available as a source for backups, not a destination. I do not want to backup the remote volume. I want to backup a local volume © and send the backup save set to a file in a shared folder on the remote volume. If I understand correctly, I should not have to log in to do that. This is beause the remote folder is shared. The remote machine is set up for share-level access, and logging in is not a possibility (or if it is, I cannot find out how to do it). So, as usual, I am completely stumped. Why can the OS on the local machine access the shared folder on the remote machine in all respects, but Retrospect cannot access it? Again it is made doubly confusing by the fact that that another local machine with a supposedly identical sharing access and peer-to-peer network configuration works with Retrospect in this fashion, and I cannot find any difference between the two local machines. Why should one work and the other not work? This volume selection has not been a complete waste of time. It raises another possibility I had not considered. I might install Retrospect on the remote backup machine, define a volume there that resides on my current local machine, and have the backup machine pull the backup from my current local machine rather than push it, as I am now trying to do. One backup machine pulling from two other machines rather than two machines pushing to the backup machine. Does that make sense? I have never used the client in all of this. Do I need to install the clients before I can have the backup machine pull files? Even if the above works, I am still puzzled as to why I cannot use the pushing technique that I have been attempting. As I see it, the remote shared folder is just another place to put a file, and it should work. Is there something else that could be going wrong that has nothing to do with access to the remote shared folder? Like writing another file somewhere else? Could we be barking up the wrong tree?
  6. Thanks, Nate. I was using administrator on the local machine and I had the remote share set up for total contol by everyone, so it should have worked. It did, in fact, work when coming in from another machine, but not this problem machine. I can't tell what makes the two local machines different. The shares I created do not use passwords. I will try another share with passwords as you suggested. However, I do not know how to configure Retrospect 5.5 to log in to the remote machine with a particular username and password. Could you kindly explain that?
  7. Running 5.5 on local machine, I want to store my backup save set as a file on a remote machine in a peer to peer network. All machines are Windows 2000. File system on remote machine is shared with Everyone having full control. I am running Immediate Backup interactively on the local machine. I select the drive on the local machine to back up. I then select the location of the catalog to be on the remote machine in a shared folder (catalog is also the backup save set). It stores a short 2 KB file "Backup Set A.rbf" on the remote machine and then quits with "Error 1101 (file/directory not found)". I have no trouble creating and deleting oher kinds of files on the remote machine in the same folder, so the share seems OK. I have tried setting account / password various ways in the Retrospect Launcher service, but that makes no difference, and I would not expect it to, since this is an interactive job, not a Launch What makes this even stranger is that I have tried exactly the same thing from another local machine on the same network, using the same backup machine and shard folders, and it works fine. I've checked network settings and can see no difference between machines. I have done chkdisk on all machines and found no errors. I have reinstalled Retrospect on the problem local machine twice. Administrator account is used for the install. Is there another file, apart from the catalog, that it might be trying to create, and if so where would that be? The Retrospect user on the local machine has Administrator priveleges, so I don't understand how this could be a problem.
  8. Server-ML-29415-ML- Moved to Desktop, Workgroup and Server 5.x forum
×