Jump to content

carpeperdiem

Members
  • Posts

    16
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    New York, NY USA

carpeperdiem's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Ah. But then we lose all incremental versions and snapshots. I think a copy is what I need to do. I will contact support. I thought company reps surfaced from time to time? Thanks for your posts!
  2. I have the manual. And working in the app. It appears the ONLY way to "repair" or recatalog an older Storage Set is first convert it to a new Media Set using "repair". This function does nothing more than clone the old file into a new file, but it DOES NOT let you add to the backup. Really poor design. From there, I can either "copy" to a NEW file, or just restore as needed. The problem here is that let's say your V6 XYZ backup (92gb) needs to be restored from. You actually have XYZ-a and XYZ-b. Each @ 92gb, and XYZ-c stored off-site, right? 92gb x 3 -- you now want to restore from XYZ-a. You now have XYZ-a2, another 92gb, and you can't do anything with it (except restore). So we now have to choose -- do we "copy" to a new media set, another 92gb - then proceed with backing up new data to the new file (XYZ_2012-a, and of course, the -b and -c set -- we've now created 6 new 92gb+ files -- just to solve the data migration issue, I have to waste more than 1/2 a terrabyte of storage. Not to mention time involved. I can probably toss the 3 "intermediary" files (the files created by the "repair") - since these immediately copy to the new Media Sets, and are useless (except to restore from). HOWEVER, once the copy operation is done, the NEW Media Set should allow us to toss (or put into deep hibernation) the original (3) V6 files, right? What would you do? Where are the company reps? Can someone from the development team jump in on this and tell me that I have it all wrong and if I did a better job of RTFM I wouldn't be making this as complicated? PS -- anyone who tells me that I don't need 3 backup sets of the same data should go jump off a tall bridge. After paying for data rescue once and almost losing my business, we now have 3 copies of everything, one copy always offsite. Drives are afraid to crash on me now since they know there is no incentive in it for them.
  3. Hmm... can you share the process to "create a new catalog file from old storage set" ? Thanks.
  4. Ok. This is a 3 step process. 1. "rebuild" the V6 storage set file; 2. make a new Media Set 3. Copy from 1 to 2 - this requires editing the script. Freaking kludgey. I KNOW user interface designis hard, That's why you guys get the medium bucks, right? This will work for me. I'll report back if it doesn't. Thanks.
  5. OK. So for my XYZ StorageSet that is 92gb, V9 needs to make its own Media set that is also 92gb, just to restore from it. Yes? THEN - I will make NEW mediaset for the ongoing project (new and modified data). So that means for every project that need a restore, we immediately double the storage needs. I guess I can live with that if I understand the process. Where this is tricky from a data management perspective -- let's say within project XYZ there are 10 "groupings". And lets say from our 6 year old restore we open up "grouping 6". We edit the daylights out of it. It's still "grouping 6" but now it's been modified in 2012 -- so we name it, "grouping 6_2012". Fine. Now, 4 years from now, we need to restore some or all of XYZ project. We will have to be VERY careful to restore the 2012 data that replaces the older content... that's why a singel mediaSet is superior to multiple. If it were as easy as doing a full restore and then new Media Set - that would be tedious, but ok, but it blows up the snapshots and incremental nature of the backups. Did the designers of this application actually consider how people use it? Anytime now -- a Retrospect Dev should jump in and tell me what I'm not doing correctly here. Thanks.
  6. Dear Retro community, I played with the V9 demo now for an hour or so... OK, the geeks have taken over the world. And how UN-mac-like has the interface turned into? Standard UI functions all missing -- but forget all that/ let's talk WORKFLOW for an upgrader. LET'S SAY that my storage sets/archives/media set are all FILES. My work is project based-- so the XYZ project has its own master folder. This XYZ folder changes constantly. The XYZ folder can become 100gigs or more. At some point, the project is put to bed and there is a slim to none chance of additional data ever being added to it. Until XYZ project manager decides to resurrect a project element 6 years from now. Happens all the time! So I have a 92gb file (two, actually -- set A and set B, on different drives) for the XYZ project. This was created in Retro V6. Let's say XYZ's project manager called me today and asked me to go back into the project, restore one element and make a change. Workflow (please correct me if there is a better way): 1. Media Sets > Rebuild (find V6 storage set). Retro V9 makes a new file in V9 format. 2. Restore (search for files) -- note: poor user interface here! 3. Now I will modify the files that need to be worked on. WHY does Retro set permissions to the restore for admin only? This is AFU. More on this later. 4. Time to backup. Whoops. Can't backup to the "rebuilt" v9 file, can we? + Normal backup using Backup Assistant - 6/19/12 3:58 PM at 6/19/12 !Can't add to Backup Set XYZ-A, the Catalog File is locked 6/19/12 3:59:59 PM: Execution incomplete At this point, I truly wonder what the developers want me to do? I DO NOT want to start a new Media Set independent of the first set -- I want the ENTIRE XYZ project to live together, forever. Does this mean that I have to do a full RESTORE of the entire 92gb file, then do a fresh backup? But then I lose all snapshots and versioning. If I simply wanted a clone, I could do that without investing in Retrospect. I want the versioning and incremental data. So what is the "correct" way to migrate a V6 project to V9? What am I missing here? I guess I could make a NEW Media Set and call it "XYZ_2012 revisions" - and then move on... HOWEVER, what happens when (in 5 years) the project manager wants something from XYZ project -- and now we have to sort/search through two sets fo files for the restore. And this also adds to data set backup and catalog issues... more files to worry about (the backup of the backups). I'll rant on about the UI later -- but in the mean time I have to figure out if Retro has a future with me. Is there a better way to migrate from V6 to V9? Final question: what happens if my V6 Storage Set was a DVD? Tape?
  7. Um, intuitive file naming? PS -- I've been using Retro since 1991 -- I have NEVER seen an interface that was as confusing to me as version 9. I will rant on about V9's UI in another thread -- but I may not get that far...
  8. I am MIGRATING to a new machine. Obviously you can't run Lion on PPC. I am testing R9 on new machine - hoping to restore all V6 and earlier backups. An upgrade guide is needed. If Retrospect expects customers to read the forums and dig deep for this information, you will lose us.
  9. I am considering migrating from version 6.x desktop (running on G5/OS 10.5.8) to version 9.x running on 10.7.4 before I get too far here, the demo application (version 9.0.2) has version 8 documentation in the bundle as well as from the app. Is that an oversight, or is version 8 and version 9 mac one and the same? Doesn't give a customer a sense of "they know what they are doing now" when you see file version discrepancies in the docs. I UNDERSTAND that version 9 is a very new product. But version 6 has performed quite well for many years -- give me a good reason to upgrade? Did I simply get a bad build of the demo bundle? Thx J
  10. Hi Lennart, chkdsk /f returned a perfect drive. any other thoughts? still getting "net retry..." error after about 772 folders/4416 files. frustrated. :-(
  11. greetings... I am coming back to retrospect after a few years of avoiding it -- and I installed Retro 6.1.230 (workgroup) on my G5/2.7DP (PPC) running OSX 10.5.7 Backups from my other MAC clients (running a variety of OS's) all are fine. I AM NOT able to backup my WinXP machine -- and getting the same error: "Net retry..." about 533 folders into the scan. Yes, I have the most current WinXP client: Retrospect Client for Windows 7.6.107 -- I also tried 7.6.106 -- no change. I also tried 7.0.112 and 6.5.140 (each time doing a complete uninstall before installing new version, and restart) Retrospect will talk to the WinXP client, and in the general settings for the client, I have tried "back up selected volumes" -- or "back up client desktop" or "back up startup volume". No change. I have added exceptions to the Windows Firewall = port 497 for TCP and UDP, and retroclient (application). No change. At 533 folders (3322 files) the scan hangs, and then "net retry..." I can mount and drag copy the entire file structure of the WinXP machine from the mac. The network works just fine. There must be a fundamental problem here -- I have been using Retrospect since version 1 (1988?) -- I have used windows clients and mac clients for years -- what's DIFFERENT is that I am now trying to run retrospect from my studio workstation (G5/2.7DP OSX 10.5.7 8gigs ram) as opposed to an ancient G4 running 10.4.x CAN I back up a WinXP network client from Retrospect 6.1.230 running on a PPC mac/OSX 10.5.7? Thanks for your guidance. Jeremy PS --the network is wired ethernet. Throughput for days. If I try to drag copy files from the WinXP client to the G5, I can move data very quickly! The destination media is a file on the G5. Doesn't matter which drive (be it FW800 or eSATA or internal SATA or the NAS). I can also move data FROM the G5 to the WinXP machine. The network clearly works. Except with retro. :-( All help is appreciated!!!
  12. Thanks for the reply. So it sounds like this setting is benign (either in the OS or disabling it in Retro?) This disk is NOT a removable, it is a fixed SATA drive in the 2nd bay of a G5 mac. Can you think of a situation where I would want this setting enabled? I guess my question is as much about the Mac OS (why do I want this permissions setting) as it is about Retrospect... by leaving the Ignore ownership box checked in OS, what problems will i face with Retro? Thanks again for helping me understand this! Jeremy
  13. Hi - I am getting a warning in my logs on a network backup to a fixed hard drive: "Warning: volume XYZ has the Ignore ownership setting enabled." Should I be concerned? Why would I want to change the remote volume permissions? The remote volume is connected to an audio workstation and it is working beautifully -- I would hate to mess up anything on that end. The data on the remote volume is NOT a boot disk -- rather, it's just a bunch of content. It is backing up to a RAID as well as tape (on my server machine, via the gigabit network) Retro workgroup vers 6.1.126 mac osx 10.4.8 Thanks in advance for any advice or clarification. Jeremy
  14. thanks for the post... Anyone running the host/server software on 10.4.6?
×
×
  • Create New...