Jump to content

lhlo

Members
  • Content count

    16
  • Joined

  • Last visited

Community Reputation

1 Neutral

About lhlo

  • Rank
    Member

Recent Profile Visitors

240 profile views
  1. Well, I thank you DavidHertzberg for refreshing my vocabulary; I had to look up how to spell "condescension". I hope your life outlook improves while others on the forum fill your ever-so-big loafers that you can't imagine anyone doing. Fortunately, I have encountered others in this forum, previously, who were actually helpful and not out to prove something to the world.
  2. Hi folks: Simple request and just seeking an understanding of which "concepts" I should be looking at in the user guide to accomplish what is needed. Retrospect Windows Pro 9.5 on Windows 7 Pro. My 1TB drive used exclusively for backups is almost full so I bought a 4TB drive to replace it. My naivety suggested that a simple copy of the drive (sadly, Acronis that came with WD drive was useless in that regard) and... voila! Doesn't appear to be the case. After doing a simple drag-and-drop of the backup folders, as an alternative to a disk clone, from the old drive to the new and plugging in the new. No "voila". I rebuilt the catalogue files (don't know if I needed to but Retrospect wasn't seeing the same old backups on the new drive but, after the rebuild, it did see them and backups now appear to be working on the new drive with the backups as previously configured). However, the size of the available room for backups has not expanded to meet the new, larger drive capacity. So, what is needed (conceptually) to make 4TB-ish available for Retrospect backups and not just the 1TB-ish that it presently sees (and has almost filled)? I had a quick look at the backup set configuration and saw no way to simply increase the size. I saw that I could "add a new member" and, perhaps, I could add a new member in the remaining 3TB of the 4TB drive but that would be a poor second choice to simply giving the current backup set more room. Thank you for your thoughts.
  3. I would agree with this except the backup being initiated when I "relaunch" corresponds to the drive that was already connected (and is still connected) and available the night before. (looking at the earlier response) Wasn't aware of "timeout for missing media" which I will look at and make sure is set. (but, then again, I can't even figure out the interface for this forum so that I reply directly to the previous post. lol)
  4. 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.
  5. That did the trick. Thanks, again, Lennart.
  6. Thanks, Lennart. After "forgetting" the C drives and then re-adding, should I expect Retrospect to pick up where it left off in terms of incremental backups. Or will it be starting fresh - i.e. no history and a full backup will occur?
  7. I upgraded the Win 7 Pro system HD to an SSD. I previously (i.e. earlier today when I discovered backups weren't happening for the past week - since the drive upgrade) found that, after the drive upgrade, the System Restore showed I had two C drives (One was "missing" - presumably because there were retained restore points that are locked to the HD thatw as removed). Anyway, that was removed so it shows just one C drive now. In Retrospect, I try to manually run an existing script and get the error "Volume OS is not available". How can I get Retrospect to see the new drive as the same drive it has been backing up for years and just continue on? I note that if I edit the script and click on Sources, the popup shows "OS (C:)" When I click on Add, the Source Selection window shows: Local Disk (C:) OS (C:) OS (C:) <and other things such as flash drives, external drives> Expanding Local Disk (C:) shows just two folders Doprocess TCWin (both of which a re related to the same software) The first OS (C:) expands to what appears to be the full drive contents The second OS (C:) expands solely to 2016.03.16 So, how do I reconnect Retrospect to the new hard drive and continue incremental backups?? Thank you.
  8. Question: There are several top tier, general purpose, broadly used cloud services, none of which are supported by Retrospect's latest "cloud" offering. It seems that "industrial scale" is the name of the game. As a user of Retrospect in a small office I find this puzzling, disappointing and annoying. Now, if I want to configure this office to store backups in the cloud I have to continue to work around the limitations of Retrospect, or sign up for yet another cloud service. A licence of retrospect is less than $200. How about supporting, or at least providing some best practices for using, cloud services that clients buying at that price point are likely to already use? Thank you.
  9. Given the plethora of cloud services and, one assumes, an growing number of businesses that use Retrospect making use of said services, why doesn't Retrospect Support publish a few "how to" papers for a few of the larger cloud providers? E.G Here's how to put your backup set on Dropbox, or Sugarsync, or Box, or Mozy, or .... (pick a few that make sense) How hard can it be?
  10. That was the one I was provided earlier by sales and was of almost no use.
  11. I am stunned. A bit more searching took me to the Retrospect 8 reviewer's guide in which is a "how to" to backup to cloud. How good a recipe provided is as yet undetermined. http://download.retrospect.com/partners/press_tools/reviewers_guides/retrospect8_reviewers_guide.pdf They will document for a reviewer, apparently, but not provide docs for the users! I am going to go through the step-by-step and see what happens.
  12. I'm looking and will try. Retrospect provides next to nothing in terms of instruction for backing up to cloud. They directed me to 2 paragraphs in a document about backing up to a private cloud. It mentions WebDAV and rsync and that's about it. Less than useful.
  13. Sadly, it looks like I will have to backup to a local folder/disk which is marked to sync in SugarSync to get it to the cloud. Fortunately we don't have a great deal of data and the waste of space can be dealt with. Now I'll just have to refresh on the file structure that Retrospect creates for the backups to see how that will impact things; Hopefully no show-stoppers will present themselves. Or store it in another cloud. Do you know of any cloud service that works remarkably well (i.e. it works and is easily configured) with Retrospect?
  14. Cloud only folder is available through Windows Explorer once the SugarSync app is installed on Windows. One can access via the following as well: \\SUGARSYNC_LOCAL\SugarSyncDrive\CloudOnly\RetrospectBackupSetC. Who knows what the actual "white box" details are of how Windows accesses the folder.
  15. Alas, it doesn't work when push comes to shove. I can jump through hoops to get the SuagrSync "cloud only" drive recognized in Retrospect and assigned to a Backup Set but when I try to actually backup, there is no joy; i.e. nothing is saved aside from the initial folder structure which Retrospect did create as the first step of a supposed backup. Retrospect Support - cloud backup should, be a no-brainer-don't-need-a-PhD-to-configure process. I do not understand.
×