Jump to content

Search the Community

Showing results for tags 'grooming'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 11 results

  1. 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,
  2. I'm trying to enable the Performance-optimized grooming in v13, but each time I select that under Media Sets > Options, click Save, then click away and come back, it has reverted to Storage-optimized. Is there a trick to this? Does the set need to be recycled? Catalog compression turned off? Some other setting done/undone? Thx, Fred
  3. I would like to be able to delete just selected files in a grooming operation on a dataset. Also -the ability to see if a file is backed up in more than one dataset (and delete the duplicate copies) -the ability to compare a volume with all file files contained in a dataset (check to see if selectors are skipping any files that should be backed up or including any files that should not be backed up) -drag and drop folders or files into a selector window for includes and excluded -option for disk backup sets to eliminate the subfolder "1-datasetname." e.g. the directory structure now is /Retrospect/datasetname/1-datasetname/backup files. I would like to simplify that structure
  4. I wonder if I can ask for some guidance on how to consolidate my backups to release more space. Something like grooming, but not quite. As I understand it grooming removes according to a file's age. I would like to rip out backups of a particular source to create space in a (disk) media set in Retrospect 10 (Mac). Is there a way to do this? Also, if by doing this I free up very large amounts of space, I hope it is possible to consolidate the retrospect files onto a smaller number of disk volumes (members) to free up these disks for other uses.
  5. I have to start this question by saying that I am not an IT professional who has in-depth knowledge and training on Retrospect. I'm an "enthusiast" user with reasonable technical knowledge in general who uses Retrospect because it works very well to back up my home LAN, so I'm wiling to spend the money to buy Retrospect Professional. I need someone to point me in the right direction and then I will gladly read the manual to work out all the details. I use multiple datasets to back up various kinds of data, and I start a new dataset of each type either monthly, quarterly, or yearly. I have some datasets going back 5+ years now, and I would like to condense them so that I have just one copy of each file in each dataset, the newest version of that file. How do I go about doing that? Is this grooming, or it is something else? Whatever this process, can it be scripted? Can I select a dataset and then apply this script, without having to edit the script the way I normally do for backup processes? Again, once I am pointed in the right direction, then I will read the manual to work out the details. Thanks in advance. x509
  6. Sorry if this has been answered before -- I can't seem to search the forums anymore to check first before posting and the documentation and additional information on the site seems vague. I'm looking for clarification on the grooming functionality. If I understand correctly, it will essentially scan through and remove old backups. The part that I'm confused about is what it leaves behind. Am I correct in that grooming will remove all but the most recent backup for each and every file? In other words, it removes "older versions" from the backup. Thanks in advance.
  7. I manage some Retrospect backup sets with a size of about 14 TB. These are in use since Version 7.7. With December 2012 I changed to V8.0 - now the disaster: The monthly grooming ended with Assertion failure at "grx.cpp-1089". Then Retrospect (running unattended) started again and retried finishing grooming and failed again. - So there was no script started for about some weeks - no error was reported (mailed). When I recognized this problem I tried to rebuild the catalog - seemed to work fine until the next backup-script started - when trying to update the catalog it complained: Error -1100 (invalid Handle) and ended with a corrupted catalog - this behavior is reproducible. I tried to reproduce it with some ne (small) backup sets - created with V8.0 - it shows the same effect. Up to now I trusted Retrospect and recommend it to my customers. OS: Windows 7 version 6.1 (build 7601), Service Pack 1, (64 bit) Application: C:\Program Files\Retrospect\Retrospect 8.0\Retrospect.exe, version 8.0.0 (199) Exception occurred on 01.02.2013 at 18:03:54 Error info: Assertion failure at "grx.cpp-1089" Exception code: E0000000 ASSERTION Fault address: FD539E5D 0001:00008E5D KERNELBASE.dll
  8. henry-in-florida

    Quit a Groom?

    I mistakenly started a Groom and cannot quit it. Anybody know how to stop the Groom once it has begun? I hit stop and it's been saying "Please Wait..." for 12+ hours. I tried shutting off the Engine and restarting it to no avail. It did restart the clock on the groom but didn't change the status. Obviously the backup set cannot be used while in this mode, assuming it's still good. Any advice would be appreciated.
  9. i'm wondering about grooming under version 10. as a preface, i will say that i could never really get grooming to work the way i wanted it under versions 8 (where i mostly didn't experiment much due to a variety of other problems and issues) and version 9 (where my experiments met with poor results leaving me thinking that i must be doing something fundamentally "wrong" in terms of how the program was designed to work). my simplistic starting assumption is that with grooming, retrospect should be able to work somewhat like the way time machine does in that you could allocate some storage to it, let it start backing up and it would save everything (every version, every incremental backup, etc.) until it ran out of space, and then when the allocated space was depleted, it would start deleting the oldest, unused stuff to make way for new stuff. with a modest number of machines (3-4) and what seemed to me to be a modest number of backups (roughly 2x/week for a few months), i would find that my media sets would take a really really long time to groom (like ~3-4 days) under version 9. so now i've installed version 10 and i'm trying it out. my first attempt is to groom an existing media set with 1TB of storage and a few million files. so far it's been running almost 5hrs. as with previous versions, there are NO meaningful progress indicators of any kind during grooming, which is quite frustrating (edit: see followup note below about progress reporting). but if i had to guess, i would say that version 10 does not look like it is going to provide any kind of huge improvement. the web page describing mac version 10 says "IMPROVED! Automatic Disk Grooming Tell Retrospect how many backups to keep, and it will automatically remove older backups when it needs more space on disk-based storage. This technology allows Retrospect to perform faster, smaller Smart Incremental backups forever." this sounds like exactly what i'm looking for. questions: is there something i need to do in order to see this "improved" behavior and in particular to see faster grooming? for example, do i need to create new media sets? is there some kind of first-time cost when v10 reads v9 catalogs before this wonderful new feature kicks-in? any other advice on how to get "smart incremental backups forever" w/o having to recycle backup sets and hopefully without needing multi-day groom operations?
  10. I have wanted to upgrade my servers to retro 9 for a long time, and now that I am doing so, am really pleased that in my long-term back operations, Retro is doing exactly what I want. I have always wanted to "distill" my periodic backup sets to a smaller number of larger sets over time, as the backups aged. I wanted to keep all my snapshots, though. For reliability, I start new sets every month or quarter, and this results in duplication of data. Retro 9 will distill that duplication out, and leave me with just what I need when I copy the data off to archive sets. Grooming looks like it will do what I want even on existing sets without copying them. Nice work, guys.
  11. Hi, Is there an ETA on a fix for the issue when a grooming script is run and the drive is not present, tha tthe only way of canceling out is to hit choices and mark the memebr as missing. This is a royal pain as then you have to go back and uncheck the member as missing to be able to use the drive again later. Thanks, --Randy Starkey
×