Jump to content

Don Lee

  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Don Lee

  1. Console 16.6 appears inadequate. It appears that this bug is in 16.1 server. I am using 16.1 because until very recently, I had Mac OS X 10.6 machines, and 16.1 is the last version that supports Mac OS X 10.6.
  2. I upgraded my server to Retro 16.1 recently, and started using Console 16.1 as well. I immediately started having trouble with the options on the clients being cleared. All of the "Allow client to:" options would be cleared every time I "touched" a client with the console. This is not a problem with Retro console 14.6, nor console 16.6 It's pretty annoying on the 16.1 console.
  3. A few comments: The amount of data moved is the biggest factor in backup speed. I am experimenting with grooming to do what I think you are doing. Rather than doing a recycle backup , I've thought about grooming the media sets down to one backup. That way, you never really do a "full" backup - much faster. Firewire 800 is not so fast these days. For some operations, disk speed is key. Thunderbolt drives may be the ticket. For many things on Retrospect, CPU speed of the server is the bottleneck. Make sure you have plenty.
  4. Page 15 in the Mac v13 documentation says: (under "what's new") Portable Backup Sets/Media Sets Retrospect v11 for Windows and Retrospect v13 for Mac now allow customers to move the member folders of disk sets to new locations and let Retrospect know by simply editing the members and picking the new location. There are scenarios where moving these files is preferable to a set transfer. Oops.
  5. I don't see anything in the forum about this, but it appears to me to be a serious bug. I cannot seem to "move" a disk media set. I have - many times in the past - moved a disk media set from one disk to another. Manually changing the path name in the "member" and/or rebuilding the catalog would restore the "moved" set to be usable. In Retro 14.6.1 (mac) _and_ Retro 12.6.1 (Windows) I am having the same problem. If the files of a disk media set are copied from one disk to another, it is not possible to "restore" it to health. It seems quite impossible. I've tried several permutations of repair, rebuild, manual manipulation of the path(s), and even removing the catalog before rebuild. The best I can do is get it to show "green" in the console and then when I try to use it, the execution gets stuck on "waiting for media". If I try to "find" the media (member(s)), it either ignores me (Mac) or fails with an error (Windows). Has anyone else seen this? I'm guessing it is a new bug in a recent upgrade, because this used to work. No, I have not tried to re-install an old version to see if that would work.
  6. As far as I can tell, the Mac "console" is only properly supported with the Mac engine. It can control the Windows engine, but Retro support tells me that's risky, and unsupported. (and can cause corruption) There is no "console" app for Windows as far as I know.
  7. I have been playing with grooming, and became interested in the difference between "performance-optimized" and "storage optimized" grooming. What's the difference - exactly? I looked in the documentation, and found that the main docs are here: https://www.retrospect.com/en/support/kb/grooming-tips-and-troubleshooting Unfortunately, the first item on that page is: "1. Choose your grooming mode: "Performance-optimized grooming" or "Storage-optimized grooming". See Documentation for more details." Note that the "Documentation" link goes to a page that says not a word about grooming. Where is the answer to my question? Is the difference between "performance" and "storage" optimized grooming described anywhere? Thanks,
  8. My thoughts exactly, although I was not aware of my "competitor" saskia. Years ago, in a galaxy far away, I used to use Retrospect's script hooks, and as I recall, they were quite useful. It seems it is time to explore the new incarnation of those hooks. I will, of course, report back. P.S. "fair" is indeed a four-letter word. ;->
  9. Thanks. I'll have to try the new header/footer. This is nice, but would be even nicer if it had some variables to plug in from Retro. The marketing collateral also implies that I can customize the "daily email report", and I don't see any docs at all on that. The Mac daily report is easy on the eyes and helpful. The Windows engine generates something different, that looks like it was intended to be machine readable, and is much less helpful.
  10. OK. I give up. Where is the documentation that tells me how/where I can customize the email reports on backups and the daily summary email? (which I really like on the Mac)
  11. I have both Windows and Mac installations, and I have recently updated a Windows site to v12.5, and a Mac site to 14.5. I see the emails from these systems is different now. The mac version produces "pretty" HTML formatted emails, including the new "backup report", which is very nice. The same option exists on Windows, but produces a mass of raw text that I have not yet deciphered. It may be a machine-readable report that imports nicely somewhere, but I don't know where. I assure you that it is not very "human readable". Is this expected? Am I missing some option somewhere that causes the emails to be "pretty" from Windows Retro v12.5? What is intended to be don with this "report"? Now I am generally NOT a fan of "pretty" email. I would much prefer plain text in 90% of the cases, but…. in this case the output from Windows is a little too opaque, even for me. Thanks for your help,
  12. FWIW, I did restore files from teh reported error messages, and they came back intact. My limited testing verified that these are not "real" errors.
  13. FWIW - Retrospect support told me that these are not real errors, only errors in the verify process. The data and datasets are intact. I will read the "dzelenik" posts...
  14. I have seen BIG improvements in the time taken to "sync" when initially bringing up the console on the Mac. Kudos to Retro Dev. Performance improvements that let me be more efficient with my time are always appreciated and welcome. Thank you.
  15. The Mac console code may be "common" and might compile and run on Windows, or it may be very Mac-specific and be a ton of work to port. I certainly don't know. If the former, it might be pretty easy to get the Windows "console" going. I think that would be a significant feature/improvement. If the latter, it may be not worth the substantial trouble. It is interesting, though, that the engine on BOTH platforms runs the same "communications" machinery, even though on Windows it is almost completely unused. Odd, but interesting….
  16. Running mac retro on mac os x 10.8. Go to media sets. Choose a good-sized one. Press "verify". Before the first verify is complete, pick another set. Press "verify". Note that the second verify is not queued. Note that the second verify does not execute, but the media set becomes "busy". Pressing "verify" again on the same media set (the busy one) results in the error enclosed. This is a bug. I tried re-starting the console, and the busy does not clear. I will likely have to restart the engine.
  17. Oh, and by the way - This is the second "verify" run, which produces the same output as the first verify. I don't think it's disk errors. At least not so far.
  18. I'm running Mac Retro on Mac OS X 10.8 on a Mac mini. I *just* upgraded a few days ago. I normally run a verify script on the media sets, primarily to get early warning on failing media/disks. This run, I see this: --Script Summary-- * Script: Verify * Date: 7/2/2017 4:08 PM * Errors: 1 * Warnings: 0 * Performance: 30148.2 MB/minute * Duration: 00:15:52 * Server: virtue --Log-- + Executing Verify at 7/2/2017 3:53 PM To Backup Set v9_daily_EIMS_last... "EIMS3/EIMS_3.3.9/Mail Folder/mcinteriors.com/design/Drafts" chain broken 6/5/2017 11:55:09 PM missing 6/7/2017 11:55:37 PM missing 6/13/2017 11:55:28 PM verified 6/14/2017 11:55:08 PM verified 6/15/2017 11:55:24 PM verified 6/16/2017 11:55:46 PM verified 6/17/2017 11:55:12 PM verified 6/19/2017 11:55:19 PM verified 6/20/2017 11:55:15 PM verified 6/21/2017 11:55:08 PM verified 6/22/2017 11:55:29 PM verified 6/23/2017 11:55:20 PM verified 6/26/2017 11:55:12 PM verified 6/27/2017 11:55:26 PM verified 6/28/2017 11:55:17 PM verified 6/29/2017 11:55:26 PM verified 6/30/2017 11:55:25 PM verified 7/2/2017 4:08:57 PM: 1 execution errors Completed: 9862 files, 466.7 GB Performance: 30148.2 MB/minute Duration: 00:15:50 Note: the media set is 69 GB, not 466 GB. The count of files is right. That was the count on the media set copy operation that ran yesterday to create this media set. What do these messages mean? Can I infer that my 6/5 and 6/7 snaps are "missing", but the others are OK? Can I still use this backup set, or is it toast? Do tell It would be nice to have an explanation without my needing to run tests.
  19. The answer to my two questions: 1. The backups are OK, but the Mac Retro provides no way to create the DR (Disaster Recovery) CDs. 2. See above. Retrospect does not provide a way to generate DR disks on Macs. You have to have a windows system. You'd probably have to download a trial version of Retro just for this purpose.
  20. I want to add to this thread a note about the "console". I have a Mac laptop, with a copy of the Mac Retro "console" on it. Just 'cuz, I fired up the console, and lo and behold, it *works* on the WINDOWS Retro server. As far as I can tell, I get the full function of the Mac engine/console via the Mac console when operating/controlling the Windows Retro server. There are a few things missing (things in the Retro Windows application that do not exist on the mac), but all in all, when I can, I find that I *prefer* to maintain/manage the Windows Retro server from the Mac console. There are a number of advantages. Way back when I posted this thread, I had no idea this would work. Turns out that it does. I hope it's supported. ;->
  21. Anyone else hit this bug? Does anyone else "rotate" their backups as I do? Anyone else know if this has been fixed in Retro Mac v14?
  22. To close the loop - my -3043 error went away. I only saw it once, and have not seen it since.
  23. I'm getting this error: Date: 5/23/2017 9:40 AM Can't use Open File Backup option for OS (C:) on TLOlibrary, error -3043 (the maximum number of Snapshots has been reached) Windows 7 for the Retro backup machine. Windows 7 for the client. NTFS FS backed up. Retrospect Trial. (windows v12) What does this mean? The backup seems to run anyway, but is it somehow incomplete? How do I "fix" it?
  24. Just for grins, I restored a file using the client GUI. This was just a test. I restored to a new folder at the root level of the C drive. (The client does not provide for a "subvolume" def?) When I did the restore - of a file that was about 8K - it took quite a while. It restored two things in my new folder. One was the file. The second thing was a folder called "Windows" that had several folders in it, and many subfolders. These were apparently "VSS" related. What's up here? Anyone care to explain what the extra gink was? When I did the same restore from the server GUI, and used a subvolume for the target, I got just the desired file restored, and it took just the brief time expected. Also, when I went to the server GUI and tried to define the "new folder" as a subvolume, Retro would NOT do it. It would just ignore me. I could define other folders as subvolumes, but not the folder I had created by the client to act as target for the restore. When I RENAMED the folder, the server GUI let me define it as a subvolume. What's up here?
  25. I am backing up a laptop Windows 7 system with a Windows Retro 12 server. Retro whines in the backup: +Normal backup using Weekly_laptops at 5/12/2017 2:47 PM (Execution unit 2) 5/12/2017 2:47:54 PM: Finished scanning backup set data files To Backup Set Weekly_Laptops... [*] T-7: VssWSnapVolume: DoSnapshotSet failed, winerr -2147212513, error -3045 Can't use Open File Backup option for OS (C:) on PASTORS-NB, error -3045 (there is insufficient storage space to complete the operation) I went to the Retrospect KB, and retrieved this: https://www.retrospect.com/en/support/kb/3045_there_is_insufficient_storage_space_to_complete_the_operation_and_3405_can_backup_system_state However, I followed the directions, and there are three partitions, none of which called the "System Reserved" partition. There is a small (35 MB) unnamed partition, a "Recovery" partition, and the C: drive. I tried "deleting the log" from the "recovery partition, but that did not fix the problem. I presume that the registry (system state) failed to back up, which means that the "bare metal" restore would not work. This is something I need. What's up with this? Can I fix it?
  • Create New...