Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. Lennart_T

    Catalog file is locked.

    What does Windows Explorer say about the files? Are they really locked? Do you have permissions to write to them?
  3. Just started happening. None of my scripts or manual backups will work. + Normal backup using The Guys Friday at 12/14/2018 10:04 AM (Execution unit 1) Can't add to Backup Set New Guys, the Catalog File is locked 12/14/2018 10:04:00 AM: Execution incomplete
  4. I was able to ping (e.g., see) from all clients to Multicast port 497, and from the server as previously describer. However I did not ping to Multicast from anywhere. Still assuming a bidirectional pathway. That’s the implication - Multicast to a machine is blocked? Robin at Retrospect mentioned a Multicast check tool - Multicast Ping for use on two machines to send and receive from each other. See this web page from the developer Mr. Dunagan. When I used the app supplied (Multicast Ping) current version, I was unable to ping from one client to the server when the app was running simultaneously, obviously the very one having the issue in Retrospect. I believe I was successful open up that port (create a firewall "pinhole") on the router IP connection to the client to see if that makes a difference, it should have been opened on the machine when I installed the Retro Client. Perhaps it will open up now, when I retest the two-way ping between the Server and this particular Client. The other devices (client and server) communicate with no pinhole configuration on the router, so I have no idea what could have caused this issue. Either way, it's simply a matter of interest. Since Subnet protocol seems perfectly fine.
  5. Your ideas have merit, I made "friends" with my router already, David. A long time ago. However, the router is not so friendly as to allow me to remove select inactive IP's singly. I have several IPs that, while inactive now, become active when the WiFi in the device turns on and the devices go from active on wired connections to active on WiFi. So there is NBO REASON to remove inactive IPs en masse. Irrespective to activity there is no reason that this is an issue the Multicast shouldn't take care of (multiple inactive users)itself and there are many reasons I do not want to willy-nilly get rid of all active or inactive IP's. No thanks. No, that's not what I said as to the IP assignment of my machines. They're not on the same IP. If you saw that, then it's an error. Let's move on. I've already proven (at least to my own satisfaction, if not yours) that based on the article Retro published (shared with you earlier) that Multicast works at the network level. So I disagree that it's a router issue in the first place. The ping proves that the IP's re being discovered. What happens within Retro beyond that is a Retrospect problem. I have static IP for my clients and have done so in the past. I feel very comfortable with my router (using it and diagnosing the performance of it) and the system I've got now. Although it's not the fastest in overall throughput, it gets the job done. I'm not making more trouble for myself than it's worth restructuring everything over and over, for no potential gain when there're multiple ways to discover clients in Retro. Emailed with a Retro support rep (Kyle) who's got a few more ideas. He suggests making the Subnet broadcast source selections work instead of the Multicast. Tried setting it up. This works very well and both clients respond to it without a problem. Obviously Direct selection of sources is a backup and also works fine, so I've got two paths to source machines, the latter being the most cumbersome. Fine. So Subnet selection's what I'll use instead of Multicast. There's still no good explanation about why Multicast fails, but I'm willing (more than, actually) to let Multicast go it's merry way without me. As I said, I've had too many problems over the years with it to believe it's happenstance or router issues as you indicate. Actually don't care to go further unless Retro support wants to carry on. I'm of the opinion that Retro's implementation of Multicast is the issue. Now, that I present the problem to Retrospect, simply not going to pursue it further.
  6. bradp015 got an answer by first making this post in the Server, SBS and Multi Server forum. His Retrospect Mac 9 success report, including methodology, is 2 posts below it.
  7. Lennart's method to move a storage set to a diff. hard drive works great! For anyone else doing this with Retro 9 on mac: When I chose a diff drive for the storage set the pathname listed did NOT change to the new drive path. On doing a test backup I returned to the storage set to look at the path and i DID change. So perhaps after you change the path to the new drive, cycle things by visiting another tab in retro and then return to the path page. If that doesnt work do a small test backup and then check the path. i would but it will be diff. and list the new destination drive path..... thanks! brad p
  8. Lennart_T

    can't link to

    My GUESS it is a hard link that points to a file that no longer exists. https://en.wikipedia.org/wiki/Hard_link It might be repaired as per DavidHertzberg's suggestion.
  9. henry-in-florida, 2. Tomorrow is "Make Friends With Your Router Day". Start by getting the MAC addresses for each of your "client" machines from Apple Menu->About This Mac->Ethernet Cards, and writing them down. Then proceed with connecting to http://192.168.1.1, logging in with your password (if you haven't changed it, it's probably on a label attached to your router), and phoning your ISP's Tech Support (not Retrospect's). Once you've done that, you want to ask the T.S. person how to navigate to setting a fixed IP address for each client machine that you actually still have. On my Verizon Quantum Gateway, that's Advanced-> IP Distribution->Edit (assuming your "client" machines are booted, so they show the default IP addresses in the router). Enter the MAC address for each machine that you do have, and checkmark the box or whatever to make the listed dynamic IP address the static IP address. If any machines are listed that you don't have, find out how to delete them. 3. You said in your second post that you have two "client" machines with the same x.x.x.64 address. That's obviously a problem; look in System Preferences->Network for each of the "client" machines, and change the duplicate to a different IP address. Make sure that the static IP for that machine is changed accordingly in your router. 4. Do not set a static IP address for your "backup server" machine. That advice came from Alan in 2015.
  10. DavidHertzberg

    can't link to

    redleader, What kind of machine is FS SERVER? Is it some kind of NAS that runs under Linux or Windows? If so, try repairing that with the appropriate software. Also Retrospect 15.6.WHAT.WHAT? Try upgrading your "backup server" and Client(s) to Retrospect Mac 15.6.1.105, which doesn't seem to have the "bad release" problems of 15.6.0.
  11. Hi David, Thanks for your thoughts on the matter. Yes. I neglected to put that in my post. I am running 15.6.1(105) on both Clients, Engine and Server. When you say "fixed IP", what do you mean by that? The Server name is what I input, its IP address appears when upgrading on the app. I have always done that and this install is no different. Do you mean to leave the Server address set as the "default IP" of 227.0.0.1? That doesn't appear to work. Do you instead mean the machine's router IP? Yes, that is DHCP. Please reread. I mention three IP's as being those in use- two clients, and a server. They are respectively ending in: .64, .70 and .86. Please re-read the comments I made and the IGMP multicast document from Retrospect. They say that using the multicast model they licensed for port 497 should work. It does, but pings to that address reveal a huge number of devices (judging by their IP) very old devices no longer active but previously assigned to that port. I wondered if that is the issue? Perhaps this is a cause of my problem, not finding the actual devices in use? I recorded the output of the ping list and you'll see the results on the attached document in that comment.
  12. So what is the "can't link to" error ? Retrospect 15.6 Mac OSX 10.13.6 InstaSCan is OFF * Script: FSA SERVER FM WED - SERVER DATA * Date: 12/12/2018 10:14 PM * Errors: 23938 * Warnings: 1 * Performance: 1060.8 MB/minute * Duration: 00:14:05 * Server: FS SERVER --Log-- + Duplicate using FSA SERVER FM WED - SERVER DATA at 12/12/2018 10:00 PM (Execution unit 1) To volume FSA SERVER FM WED on FS SERVER DATA... Note: OS X System Integrity Protection may prevent the restoration of protected files and folders to FSA SERVER FM WED on FS SERVER DATA. - 12/12/2018 10:00:00 PM: Copying FileMaker Server on FS SERVER 12/12/2018 10:02:38 PM: Selector "EXCLUDE FM SERVER" was used to select 65247 files out of 65380. 12/12/2018 10:06:21 PM: Finished deleting 7 unnecessary files and 4052 unnecessary folders on destination 12/12/2018 10:06:25 PM: Copying: 17894 files (5.6 GB) and 37902 hard links *File "/Volumes/FS SERVER/Library/FileMaker Server/Data/Backups/Weekly_2018-11-19_2300/Databases/Fresh Start/RC_Data_FMS/JUPITER/PHOTOS/CONTRACTS/CL0000070220/CL0000070220_5.pdf": can't link to "/Volumes/FS SERVER/Library/FileMaker Server/Data/Backups/Weekly_2018-11-26_2300/Databases/Fresh Start/RC_Data_FMS/JUPITER/PHOTOS/CONTRACTS/CL0000070220/CL0000070220_5.pdf", error -1101 (file/directory not found) *File "/Volumes/FS SERVER/Library/FileMaker Server/Data/Backups/Weekly_2018-11-19_2300/Databases/Fresh Start/RC_Data_FMS/JUPITER/PHOTOS/CONTRACTS/CL0000070220/CL0000070220_5.pdf": can't link to "/Volumes/FS SERVER/Library/FileMaker Server/Data/Backups/Weekly_2018-12-03_2300/Databases/Fresh Start/RC_Data_FMS/JUPITER/PHOTOS/CONTRACTS/CL0000070220/CL0000070220_5.pdf", error -1101 (file/directory not found)
  13. henry-in-florida, First, have you updated your "backup server" machine and your Mac Clients to 15.6.1.105? 15.5 and 15.6.0 seem to have been "bad releases", at least for Retrospect Windows. Second, I was told years ago by the now-departed-from-Walnut-Creek Alan that the "backup server" should not have a fixed IP address. The one time I tried violating that, I had problems. Third, surely you shouldn't have two "client" machines assigned the same fixed IP address—such as .64.
  14. I found this Retro article related to Multicast: https://www.retrospect.com/en/support/kb/why_is_retrospect_communicating_with_address_224_1_0_38 Running terminal as described by the article (ping test of 224.0.0.1), I found a huge number of assignments, which repeat. Could this be the problem?? No idea how to fix it. The only relevant IP's are clients at .70, .64 (TWO CLIENTS), .86 (the Server). Can I delete the others (.121, .83, .81, .67)? It seems these may be IP's stored in my router that are no longer active for these clients or their predecessors. I don't see how this could be gumming up the works but I could force my router to forget inactive clients, I suppose. Ping Result_multicast_181212.rtf
  15. This is a bug of some long standing related to locating a client. I have found it regularly when needed to add or re-add it to the sources. Here's an example: I have TWO clients. Both work fine and can be located by IP with no trouble. Also, both exist on my network and Bonjour can locate them in MacOS. However multicast cannot find one of the two. The attached shows the story. Since updating to 15.6.x, I now have to add at least the missing client via it's IP rather than with multicast. I tried to turn the client software on and off, restart the machine and combinations reversing these two steps without success. Does anyone have an idea what causes multicast to behave so badly with network attached clients in Retro? Have also had the other client go missing from multicast and the opposite client show up instead in previous iterations of the process. I conclude that multicast is very unreliable. YMMV.
  16. Lennart_T

    What am I doing wrong?

    That is what you did wrong. You should NOT log out, you should just exit Remote Desktop.
  17. Earlier
  18. This may be a stupid question but I'm new to Windows Server.... I purchased Retrospect (Server version) and got on the server thru remote desktop, installed it, set up everything and logged off. Nothing ran without me being logged in thru RDP. So I disabled the timeout on RDP and am just leaving it connected. Works but it just seems like there has to be a way to have it run without being connected. Any help for a server newbie? Thanks
  19. x509

    Backups "freeze" part way with no error

    Fair, but ouch! I thought about this for a while, but if I wanted to enable concurrent backups, I wouldl have to completely restructure all my scripts as well as my source groups, and every time I redo my scripts, I find an issue a few days later. I can live with the lack of concurrence on my four main backup scripts, because I know they work. Still, it's good to know that I can run a grooming operation, even more than one, at the same time I'm doing backups. 🙄 x509
  20. David, I am actually familiar with pcap, but it's not exactly easy to use. If the problem occurred more frequently, I might need to debug the problem, but even for my personal use (where I am the "IT guy" at home), I have a list of issues to address. Of course if this LAN client goes dark more often, then I will need to investigate. I appreciate the help, still.
  21. How are the scripts set up? Proactive? Or scheduled, with a timeout for missing media? That is because it did not run at 5PM yesterday, so "better late than never".
  22. Sorry, I didn't notice it was the Windows part of the forum I posted in. (Still, after all those years...)
  23. DavidHertzberg

    Backups "freeze" part way with no error

    x509, If you want scripts doing Backups of the same LAN "client" drive to run concurrently, they must be backing up different Subvolumes of the same "client" drive. Even that is new for Retrospect Windows 12.6, as noted here. As j-polasektamu.edu's OP in that thread said nearly 3 months before 12.6 was released:
  24. x509

    Backups "freeze" part way with no error

    James, So "it's a feature, not a bug." So I just tried to run immediately some backup scripts that all work on different backup sets. I deliberately selected different Execution Units. Here is what I got: DELOS and APHRODITE are two LAN clients. The currently active script will back up from these clients. Is that why scripts Software Library and DATA are waiting? If so, major bummer. With some exceptions, all my backup scripts back up different files from both the server (this system) and the LAN clients.
  25. After a little creative searching on Wikipedia, I found this. YMMV; I haven't had a Windows machine in my home installation since I gave back the Windows 95 desktop to my employer upon being laid off in 2004. Up to that point, I was getting my Windows tech support from IT in our New Jersey office.
  26. Retrospect V9.0 on Win 7 Pro A single machine being backed up to three, alternating external drives (A, B and C). I have programmed three daily backups to run at 5:00PM, one for each drive. The one that is connected at the moment actually runs, the other two fail, as expected. The main problem is that, sometimes, I check the backup history and see that it hasn't actually backed up for a week or more and I don't really know where to begin to troubleshoot. I suppose I could ask the user (who powers up each morning and shuts down each night) to check, after starting, to make sure the external drive shows up in Explorer. If the drive is not visible, then problem identified. Let's say, for this purpose, the drive IS visible to the OS. Anyone have any ideas as to why backups would be failing for several days? I can't say if it is the same drive that has these multiple failures as the machine is presently unavailable to me. Somewhat connected, perhaps, are other odd behaviours I've seen. This is related to opening Retrospect on the desktop and I'll just note some things I've seen. 1. When I click on Retrospect, it take me to the Dashboard. Sometimes, after many seconds, the "main" retrospect window appears. Other times, it doesn't and I have to click on "relaunch" to make it appear. Sometimes, when I start up Retrospect, it decides that it is going to backup RIGHT NOW!! Even though it is not scheduled til 5PM and right now is 10AM. Why? 2. When I exit retrospect, it is unclear if it is killing the process as well as the window of if it just killing the window but the background process continues. There is a drop-down menu at the top of the main screen which appears to be a selection as to what to do when you exit Retrospect. It could well be that I just don't know how this is supposed to function. That is, when I exit from the Retrospect window, I do expect the process to continue running in the background and executing future scheduled backups. Looking for any tips. Also happy to be referred to the user guide. Thank you.
  27. JamesOakley

    Backups "freeze" part way with no error

    I am doing this, and it is working. But, if the two scripts require a lock on the same source volume or backup destination, the system will respect that and wait for the lock to exit. But where the scripts are truly independent, one doesn't hold the other up.
  1. Load more activity
×