Jump to content

mbennett

Members
  • Posts

    73
  • Joined

  • Last visited

  • Days Won

    7

mbennett last won the day on August 23

mbennett had the most liked content!

Contact Methods

  • Website URL
    http://www.claritysoftwaresystems.com

Profile Information

  • Gender
    Male
  • Location
    Fair Grove MO

Recent Profile Visitors

611 profile views

mbennett's Achievements

Newbie

Newbie (1/14)

13

Reputation

  1. I'd like to point out that I asked for and received help from Retrospect Support dozens of times during this project, mostly in the early phases. While I didn't always get the answer I wished for I always got an answer, so I knew where the lines were drawn and what could and would work. It helped immensely to move the project along, and I thank them again. They may not have been exactly aware of the full scope of what I was attempting, but certainly new the arena I was working in. Mark
  2. I think it's entirely possible that your Retrospect selectors are set to exclude trash or temporary files. Norton may also be scanning networked drives or other sources that aren't part of the backup set. I expect when you dig into it you'll find they're both correct on some level. Try cleaning up disk C:\ or other drives on your system that are being backed up, and empty the trash. Check your selectors. I've been fooled before about what's getting backed up, especially when I find an exclusion in a backup set that I'd forgotten about. This did raise an interesting idea in my mind. I can't find a file count for the entire drive, although as you show in your screen capture you can count files in each directory. Where did you find the window you show? Which version of Windows is that from? Retrospect does count the files, but I'm not sure that interprets to anything meaningful, just what has been backed up and can be restored. When I've restored from a Snapshot it does restore everything and puts the entire system back to that point in time including all files. Report back what you find.
  3. David Why don't you stick to the subject of this thread, which it so happens is not a personal grudge you have against Retrospect that dates back to 2017? It's because you have absolutely no pertinent information or knowledge of this subject at all, as you admitted in your first response. Start your own forum thread and beat that dead horse once and for all, leave this topic to those who are interested in the subject. Mark
  4. I found one mistake or at least an omission in my original document, where I made a statement that Synology does not team network interfaces. Some of their models do offer link aggregation, and you can find more information on that here. https://kb.synology.com/en-my/DSM/help/DSM/AdminCenter/connection_network_linkaggr?version=6 If you try this and test it, it would be very interesting to read details on exactly how you configured it, especially it if results in overall backup speed improvement. Mark
  5. David, I'm not soliciting hysteria over whether the post should have been made. Rather, I was more interested in a productive discussion about factual or procedural errors or improvements. AFAIK this post does not violate Forum rules, and this and and other similar posts should be encouraged because it expands the functionality of the product. You personally display a deep distrust and dislike of Retrospect and StorCentric, which is a recurring theme in nearly every one of your posts. Why are you here? Just asking, but I read a lot of your posts and they're nearly all non-responsive. It's interesting in a weird way. Mark
  6. David, Since Retrospect specifically documents support for competing NAS products in the knowledgebase, including Synology and QNAP, I think I'm pretty safe. Those two companies own a huge share of the consumer NAS market, so I'm pretty sure that a lot of users and dealers are already using them. If the forum admins take this down I'll just post it on my own website and let people search for it and find it. We're all on the same side in this war, offering alternative ways of securing data and backups. This is just one more tool, one more approach. If it's found and used successfully it only enhances Retrospect's capabilities, which is good for StorCentric. The NAS business seems to be extremely competitive. Drobo has a lot of good hardware diagnostics features. If Drobo wants to send me a free NAS to play with I promise I'll write up a similar treatment. (This is me holding my breath.) Nexsan is much more geared for enterprise or large business environments from my casual observation. I watched a terrific on-line demo a couple of months ago and immediately passed a link along to some people who I thought might be good prospects. I don't know anything about Vexata. The way I look at it Retrospect should be a big tent supporting multiple hardware devices, which it does now. Hope it stays that way. Mark
  7. Good Morning, I have been engaged in a long project to design a way to harden a Synology NAS so it can be used with Retrospect to make it ransomware-proof. I decided early on that I should make notes. Good thing. This is the result of months of work, and I hope it's useful to many users and dealers. Please leave notes and critiques, which I'll try to address as we go along. Good Luck, Mark Hardened Synology NAS.pdf
  8. The only possible idea I can offer is that if you can plug an external, lower resolution monitor into your laptop, and it it lights up (both very big "ifs" I realize) that may give you the ability to view a screen. I assume the second monitor is made accessible in the BIOS, so it's something to try.
  9. This is how I've been able to use the Disaster Recovery CD. I found my notes, so this should be pretty good, but I'm made a few edits. 1. Boot up with Retrospect emergency CD. Make sure you use the correct 32 / 64 bit version for the crashed system. 2. Initialize the drive every single time. If you completely start over for some reason just init the drive again, but make sure your situation is unrecoverable. Read the last paragraph. 2a. The biggest problem I've had at this point is obtaining the correct Network card driver. You can find that somewhere on the internet and put it on another CD or USB drive and load it as part of the initialization procedure. 3. Select to restore as client. The IP address will be displayed (requires DHCP to be running on the network.) 4. Go to the Retrospect server. Select to restore from the left menu bar, and create a new client during that process. It will find the client running, named "minit-xxxxxxx" and do not rename. Don't worry about the drive letters. (I have also gone to Configure | Clients and setup a new client there.) 5. Select the PC snapshot you want to restore, with the temporary client name as the target. Select the second bullet to restore the system state, registry and all files. 6. Once the restore is complete, reboot the client computer. If it doesn't boot it may be because the bit version was incorrect at step one, so try using a Windows emergency disk for the correct 32 / 64 bit system and repair the system. Generally speaking this works fine. The last time I used it the restore hung at about 98% complete and never finished. After almost an hour I eventually rebooted the client, cursing under my breath, and restarted the whole procedure. After I launched the restore job (new client name) Retrospect chewed for a few minutes and decided almost all of the files had been restored already, restored the very few remaining and the job was completed in less than ten minutes. I was extremely grateful. I hope some of this is useful for you. Good luck. Mark
  10. I think having duplicate names may be the issue, and it's ambivalent from the Retrospect POV. I'd rename the backup drive on the Retrospect server to "Backup2" in Windows. Then you'll need to rebuild the catalog for all of the backup sets. I think I'd do one as a test, since the rebuild will take a long time. This is just an opinion. The closest I've come to this is making a backup on a Windows 7 system where Drive C had one name, then installing Windows 10 on the same system overwriting everything. W10 uses a different drive naming convention, so I had to adjust a lot of scripts.
  11. In addition to what Nigel and David have mentioned above, there is a tunable in Preferences | General that limits the number of executions that can run at once. I think 16 is the default, but if you have the resources you can bump it up.
  12. If you got the simple restore to work and saved the job, you should be able to toggle back over to the advanced restore and look for differences. I don't do a whole lot of restoring. The most fun I've had with this type of thing was to define my Downloads directory and exclude it from being backed up. I took several runs at that before I could get it to work.
  13. I haven't tested this, but using the "Condition" dialog can be very tricky. I think instead of "Starts with" I would instead use "Match". Keep experimenting in that dialog because that's where the problem lies. In fact, I would delete the other conditions and do this as a building block. Start with one line and make sure it gets the results you expect, then add one more condition, test the results, then another until you see the only results you want. Also, when the restore starts pay close attention to any prompts, because there may be a question in there with a "Do you want to overwrite" with a reverse logic default answer. Newer versions haven't changed this that I know of.
  14. I think I'd call support on crossing platforms. But here are two things to try if you want. 1. Even going from one Windows system to another, the only sure fire way is to use the Transfer Backup Sets tool. I'm successfully moved the manager server setup, configuration and catalogs. But when you move the backup set to a new repository it won't work. Transfer takes care of that, but I'm not sure you can do that unless you can map a drive on Windows to the Mac's SMB share. 2. You should be able to create a new catalog from a backup set, simply by using the Repair a Catalog tool. If it repairs the catalog or creates a new one, you should then be in business. Running either function should be expected to take hours or days. Good luck.
  15. I suggest you simply remove the systems from the backup schedule on the weekend, therefore when you boot the systems on Monday morning there won't be a slowdown. You obviously already know how to launch a backup job manually, so just do that.
×
×
  • Create New...