Jump to content

tshubitz

Members
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tshubitz

  • Rank
    Occasional Forum Poster
  1. As I so far have not been very impressed with Retrospect 8's reliability, I decided to try and restore some files from a backup I've made in the past day or so. I kicked off Retrospect, chose "Past Backups", selected a backup, and then clicked on "Browse." I got a nearly blank window that shows a tiny bit of something (the past backup I presume) and an 'Ok' button that does nothing. (see attached PDF) I tried resizing the window and this made the 'Ok' button disappear along with the tiny bit of information for the past backup. I've tried hitting 'Return', clicking the 'Ok' button, hitting 'Esc', command-., nothing. Right now, Retrospect won't back out of this window and I'm unable to just "quit" the program. Unfortunately, I'm thinking that I'll have to force quit Retro to be able to get out of this window. Any ideas? - tim
  2. Dave, Thanks for the response. Yes, the Engine is being run on the same machine as the Console. I just happened to be doing this as I left the Console up when I went home last night. Remoted in to check in later in the evening. Anyway. I'm using 'Archive' as, to me anyway, that makes sense as to what I'm trying to do. I have a bunch of data spread all over the place (drives, disk images, etc.) that I want to push into Retrospect so that I can search my grand archive of everything that has accumulated over the years. I'm archiving the data and then recycling the drives that the old data was on. Does doing just a regular ol' backup make more sense? Is the Retrospect archive functionality really intended to be used for data that is ALREADY backed up but can be safely "archived" and removed from the "normal" backup? Thanks for your time. Have a wonderful day. - tim
  3. No, the destination is a Media Set (Archive_Set) that consists of three (3) SATA physical drives (volumes). The disk image is mounted to have the data within the image added to the archive. - tim
  4. Here ya go. This screenshot is taken while I was logged in remotely to the backup server. The situation here is as follows... - Retrospect was setup from scratch (no scripts, media sets, etc.) - Three "archive" disks (all SATA) were formatted and attached to the server via three separate Voyager Q's (2 via FW 800, 1 via FW 400) - Created Media Set 'Archive_Set' and added all three "archive" disks to the Media Set. - Created backup archive script and added the Media Set 'Archive_Set' as the backup location - Added 'Server Boot Mirror' (internally attached SATA), two disk images that were mounted (Macintosh HD), and a USB 2.0 connected ATA drive (User Temp Backup) - Hit 'Run' for the script Retrospect got through the 'Server Boot Mirror' drive and seemed to start on the first mounted disk image but eventually puttered out. No error, nothing. Just stopped after trying. - tim
  5. Robin, Yes, I have done this which is why I was a bit surprised that Retrospect didn't move on to the next member. - tim
  6. Is this just a cosmetic issue? Can it be safely ignored? Say I set "Use at most" to 100% and apply it. Is it applied even though Retrospect might not be showing 100%? Thanks! - tim
  7. Background ------------------ Retrospect Version 8.1 (build 150) - PowerPC-based Retrospect Engine Mac OS X Server 10.5.6 - xServe Dual 2.3 Ghz G5 - 3 GB RAM - 400 GB boot drive - Catalog files stored on boot drive where Retrospect is installed - Disk-based setup for initial archive (Archive_Set) 1. archive_disk_1 - 6 GB ATA - connected to server by: NewerTech USB 2.0 Universal Drive Adapter 2. archive_disk_2 - 75 GB SATA - connected to server by: NewerTech Voyager Q FireWire 800 3. archive_disk_3 - 75 GB SATA - connected to server by: NewerTech Voyager Q FireWire 800 - Drive being backed up - 75 GB SATA - connected to server by: NewerTech Voyager Q FireWire 800 End goal ------------------ Actually feel confident that Retrospect is actually using 100% of the available drive space of a disk member. Issue ------------------ Upon adding new members to my Media Set (Archive_Set), I set the "Use at most" option to 100% of available drive space. Sometimes Retrospect takes that value and applies it where other times Retrospect couldn't care less that I wanted to change whatever value it had in the "User at most" percentage field. Each time I've tried to do this I've had completely bare, formatted drives. Ideas? - tim shubitz
  8. Background ------------------ Retrospect Version 8.1 (build 150) - PowerPC-based Retrospect Engine Mac OS X Server 10.5.6 - xServe Dual 2.3 Ghz G5 - 3 GB RAM - 400 GB boot drive - Catalog files stored on boot drive where Retrospect is installed - Disk-based setup for initial archive (Archive_Set) 1. archive_disk_1 - 6 GB ATA - connected to server by: NewerTech USB 2.0 Universal Drive Adapter 2. archive_disk_2 - 75 GB SATA - connected to server by: NewerTech Voyager Q FireWire 800 3. archive_disk_3 - 75 GB SATA - connected to server by: NewerTech Voyager Q FireWire 800 - Drive being backed up - 75 GB SATA - connected to server by: NewerTech Voyager Q FireWire 800 - Method used to create "Archive_Set" - Retrospect console --> Media Sets --> Add - created "Archive_Set" with Media Set Type: Disk, Add - selected "Archive_Set", Members, + to add mounted drives - selected mounted drive, set "Use at most" to 100% for each drive, Add End goal ------------------ Once the current members of a Media Set (Archive_Set) are filled, I want to add another disk member (or four, or twelve, whatever) to the Media Set 'Archive_Set' and continue using the one archive set for all further archiving. In essence, I want to just keep growing the members in the "archive set" indefinitely continuing to archive across all members. Issue ------------------ Once I needed to add a new member to the Media Set 'Archive_Set', I first attempted to do this by using the same method as above. When I went to start a new archive of more data, Retrospect gave an error saying that the Catalog file was out of sync and to rebuild it. I used the rebuild procedure, again tried to archive the same data, and still received the same error of catalog out of sync. I then blew away the 'Archive_Set', associated Media Set, and started completely from scratch. I went through the same steps as above but instead added another disk member through the "Rebuild" process and added a new member this way. This last method seemed to work but, alas, Retrospect still refused to use the other members of the archive. Last comments ------------------ Perhaps I totally don't understand the thinking behind Retrospect's archive functionality but to me it seems that I should be able to do what I'm trying to do. I haven't found any documentation or other postings to the contrary. Any ideas? - tim shubitz
  9. Background ------------------ Retrospect Version 8.1 (build 150) - PowerPC-based Retrospect Engine Mac OS X Server 10.5.6 - xServe Dual 2.3 Ghz G5 - 3 GB RAM - 400 GB boot drive - Catalog files stored on boot drive where Retrospect is installed - Disk-based archive set 1. archive_disk_1 - 6 GB ATA - connected to server by: NewerTech USB 2.0 Universal Drive Adapter 2. archive_disk_2 - 75 GB SATA - connected to server by: NewerTech Voyager Q FireWire 800 3. archive_disk_3 - 75 GB SATA - connected to server by: NewerTech Voyager Q FireWire 800 - Drive being backed up - 75 GB SATA - connected to server by: NewerTech Voyager Q FireWire 800 End goal ------------------ Archive data spanning all three attached disk members without error and intervention by me. Issue ------------------ I had a Voyager Q-attached 75 GB SATA drive ready for archiving. The 75 GB drive was added to the archive script as the 'source' and the script was run. After Retrospect finished filling up the first member (6 GB ATA) of the archive Media Set, Retrospect stopped and did not move on to 'archive_disk_2' (75 GB SATA) which was already attached. No errors were reported. Retrospect just stopped. Last comments ------------------ I'm at a loss as I've completely wiped out all media sets, reformatted the three archive drives, recreated the archive set and associated media set. Same problem. Any ideas? - tim shubitz
  10. I just upgraded my Mac OS X server version of Retrospect to the new 5.1 and am hoping to use the Linux client capabilities to do backups of our SCO UNIX box. Under the Linux compatability environment the Linux Retrospect client installs and "runs" but I'm not able to connect to the client from the server. (I scan the SCO box and the port doesn't show itself open.) I've added (in the SCO environment) Retrospect to the services file (dantz 497/tcp) and tried to add it into inetd.conf (again, in the SCO environment). Maybe that doesn't need to be done, still new to SCO. When I HUP'd inetd I scanned the machine again and port 497 was open, though the Retrospect daemon was not running. Manually started the daemon and still no luck. Anyone else trying to do this? Any success? I feel I'm close but thought I'd throw this out there. Thanks for any advice and have a wonderful day. tim
×