Jump to content


  • Posts

  • Joined

  • Last visited

dstranathan's Achievements


Newbie (1/14)



  1. I cant get the Email Notifications to work at all. Not only does the Test button fail, but both successful and failed jobs do NOT notify me as expected. Its broken. Kind of an important feature for me. Bummer.
  2. Im no longer able to send Email Notifications with Retro 8.2. It worked fine with Retro 8.1 before the upgrade to 8.2. My email server, DNS, and network infrastructure has not changed. Im running an Exchange 2007 server. No auth required. I have tried simple hostnames, FQDN's and static IPs. None of them work. The test messages never arrive in my Inbox. Has anyone else seen Email Notification issues with Retro 8.2?
  3. I just built a new Retro 8.2 server. Installed 8.1 and upgraded to 8.2. Created all new Catalogs, Sources, Scripts and Media Sets. Updated my clients to the recent version too. Everything looks golden - until I try and backup something... Started to run my brand new backup scripts at night. All my scripts are complaining that they are "Requesting New Media". No clue why. All my (new, empty) Media Sets are stored on a empty 3 TB volume which his mounted (And Retro 8.2 can see and browse it with no problems). No permission issues here. I then rebuilt the Retro server again. Killed all my Scripts, Catalogs and Media Sets and built them AGAIN from scratch. Same problem. Retro 8.2 still thinks the Media Sets are either full or missing I guess. No clue why. Whats up? Any ideas?
  4. I just noticed that all my Media Sets have what appears to be weird group ownership permissions. The owner is "root" (which makes perfect sense), but the group owner is "_installer". This is true for all of my 10+ Media Sets. Example output from the bash shell ls -al command below: backup01:Retrospect admin$ ls -al drwxr-sr-x 9 root _installer 4096 Jul 27 13:02 . drwxrwsrwx@ 3 _installer _installer 33 Aug 21 09:37 .. -rwxr-xr-x 1 root _installer 0 Jul 27 12:47 EMC drwxr-sr-x 3 root _installer 38 Jul 27 12:47 Media Set 1 drwxr-sr-x 3 root _installer 35 Jul 27 12:48 Media Set 2 drwxr-sr-x 3 root _installer 37 Jul 27 12:49 Media Set 3 ... The "_installer" account is an Apple default local account for the PKG Installer services (GID 96). It is my guess that EMC/Dantz/Roxio would not assign this group to Retrospect Media Sets. I just doesn't make sense. Can you guys take a look at your Media Sets and tell me what they look like please? I cant find any documentation on Media Set ownership. Im still running 8.1 by the way. Havnet applied the 8.2 update yet. Ill wait a while...
  5. I have a 'Grooming media' task that's currently running. I can't stop it. Its trying to Groom a Media Set that has recently moved to a new volume. Classic "chicked and egg" dilema. I cant stop the task to tell Retro 8 that the Media Set has moved, and thus its stalled wanting media - ironic eh?. I can't pause the Grooming task, nor can I stop the Grooming task (nothing happens when I click the Stop button) I cant stop the Retro 8 server daemon from the Preference Pane either. I have to kill it (kill -9) from the command line. When Retro restarts, the Grooming task starts up so fast that I cant get to the Admin Console GUI fast enough to stop it before it begins again. I have tried rebooting the physical Xserve server etc. Nothing works. I moved my other Media Sets to the new volume with no problems (and they run fine), but this particular Media Set cant be moved because its locked (because its running right now and I cant modify it). Im in limbo! Why wont it stop when I tell it to? How do I stop the Grooming process from running? All I want to do is this: 1) Stop the Grooming activity! Stop I say. 2) Tell Retro 8 that I have moved this particular Media Set to a new volume (easy to edit the Media Set's path once its not in a locked "running" state) 3) Resume my normal scripts and activities again. If it needs to groom now, fine. Groom away. Any advice? Is there a best practice procedure for this? Specs: Mac OS X 10.5.8 Retro 8.1 Xserve 2007 NAS storage (not local)
  6. Retro was trying to groom a catalog this week. Looks like it had problems. I was informed that one of my catalogs was corrupted, so I ran the verification tool (didn't try to repair it - just verify). Its been running the Verification process for 24+ hours. So I decided to stop it. It refuses to stop. Any ideas? Should I kill the Retro server process from the System Pref Pane? How do you handle these types of issues?
  7. I have a Retro 8 server which has 5 Media Sets on a single 1TB SAN network volume (I back up to disk, not tape). I backup 5 clients. Each client has its own dedicated Media Set. Each Media Set has 1 member. Very simple and clean configurations. When I created the Media Sets originally, I told Retro to allow all the 5 Media Sets to use up to 100% of the SAN volume as needed (which is 1TB in size and a fully redundant RAID). For some reason, some of the Media Sets claim to be "full" (red) and others are green or yellow. This is strange, considering all of the Media Sets share the same disk. The "Capacity" and "Percentage Used" columns appear to be incorrect. How can I control the Media Set sizes one they have been created? Is there a way to verify the capacity and edit/adjust the capacity if needed? Is it a bad idea to keep multiple Media Sets on the same disk/volume? Seems natural to me...
  8. Thanks Stewart. Appreciate the info. Can you post some details on your environment? • Did you upgrade from 10.5 to 10.6? Server or "regular" OS X? • What hardware are you running on? • What other services are you running? • are you staying on the current OS or are you considering reverting back? • What was the driving factors behind the OS upgrade?
  9. I have a dedicated Xserve running Retrospect Server 8. The server is running Mac OS X Server version 10.5.8 (Leopard Server). The server also provides 2 other services, including both SUS (Apple Software Update) and DeployStudio (via NetBoot NetRestore). My Xserve mounts a network SAN volume which stores all of Retrospect's Media Sets. Normally I would never consider an in-place upgrade. I generally follow tried and true best practices when it comes to patches, updates and upgrades. I usually opt for clean installs regarding my Mac OS X server infrastructure. But Apple has touted that In-Place upgrades are actually quite feasible these days. Not to sound lazy or anything, but it sure would be nice if I could just install the OS X 10.6 Server upgrade from the DVD installer, put in a new license code, fire up Retrospect's backup engine and get back to work. My main concern is how Retrospect 8 will respond to the OS upgrades. Nothing will change in terms of the Retro binaries, versions and paths. The server will maintain it's original hostname, IP address, serial numbers, licenses and other critical resources (including the NAS volume with my Media Sets). Im not worried about my SUS and NetBoot services, Im sure they will be fine. Its Retrospect that I need to focus on. A couple key questions before I make a upgrade decision: 1) Generally speaking, has anyone had any luck running Retrospect 8 under Mac OS X 10.6.x (Snow Leopard Server)? 2) Has anyone done an in-place upgrade of Mac OS X Server on a Retrospect 8 server? Comments and feed back are greatly appreciated.
  10. OK, here's the grooming info from the Users Guide (p 236-237) The grooming options are: • No grooming: When the backup drive fills up, Retrospect asks for another hard drive on which to store additional backups. All of your backups on the original hard drive are preserved. • Groom to keep this number of backups: Specify the number of back- ups you want to preserve for each source when the backup drive fills up, or when you run a scripted or manual groom operation. Retrospect then automatically “grooms†(i.e., deletes) all the other, older backups on the hard drive to make room for new data. • Groom to Retrospect defined policy: When the backup drive fills up, or when you run a scripted or manual groom operation, Retrospect uses its own grooming policy to delete old backups. At a minimum, Retrospect’s policy retains two backups for each source, saving the last backup of the day for each source from the two most recent days on which each source was backed up. Given enough space in the Media Set, Retrospect keeps a backup of each source for every day in the last week, a backup for each week in the last month, and a backup for each previous month. Normally, you set a grooming option and need to do no more. But since you can turn grooming on or off for a given Disk Media Set at any time, you may have a nearly-full Media Set that you want to groom immediately after you enable grooming for the set. Note: When you activate grooming for a Media Set, Retrospect will retrieve the point-in-time file and folder listings from the Media Set for each source, going back as far as the number of backups you’ve set to keep in the grooming options, and add them to the Media Set’s Catalog. Because Catalogs for Media Sets with active grooming policies need to store this additional data, they will be larger in size than Catalogs belonging to . To groom a Disk Media Set manually, select the Media Set in the list, and click Groom in the Media Set toolbar. Retrospect displays a dialog asking you to confirm the groom operation. Click Groom. Retrospect begins a Groom- ing operation, removing excess backups from the Media Set, according to the grooming options. You can monitor its progress in the Activities list. When Retrospect finishes, click the Past button in the scope bar of the Activity list for details on whether the grooming was successful. If the operation was not successful, click the Log tab for additional information.
  11. Can Media Sets Groom themselves without manual intervention or a script instructing them to do so? I have few Media Sets configured to Groom after 30 backups. This was setup when the Media Set was created. I haven't written (or ran) any Grooming scripts on these Media Sets yet. Today, I got an automated message from my Retrospect 8 server indicating one of the Media Sets had been groomed (reclaimed 36GB of space too). I was surprised to see this message, because I dont have any Grooming scripts written, and nothing related to Grooming has ever been executed by yet thus far. Other than setting my MEdia Sets to Groom after 30 backups, I havent done anything with Grooming at all. I was under the impression that the process of Grooming had to be: 1) Manually ran from the Retro Admin console. Or... 2) Scripted to run. So, apparently, based on my observations above, Media Sets are "self-cleaning" and can Groom themselves? Is this possible?
  12. Im not sure I clearly understand how Retro 8 behaves during and after a Grooming process. 1) According to the Summary pane of one of my Media Sets,I have a Media set that has been backed up 40 times. This is approx. 2 months of backups (running once per night during the week days). I decided that I am going to start Grooming this Media Set down and start keeping about 1 month's worth of backups instead. So I wrote a Grooming script to keep only 20 backups (approx 1 month of weeknight backups). So I decided to run the Grooming script on this particular Media Set for the first time. After the Grooming scripts was complete, the Summary pane for that particular Media Set still indicated that it had a total of 40 backups, as opposed to 20. I was surprised that the number of backups didnt change in the Summary pane. Does the Summary pane ever refresh the backup count value after a Grooming script runs? if not, ow do you guys know when to run your Grooming scripts? I want to run my Grooming Scripts manually for now on a as-needed basis, rather than having the Grooming process run automatically. I want to do this because I dont trust the Grooming process yet, and it it takes a really long time too, so Id rather run the Grooming when I have enough of a time window. But if I can tell how many backups have ran since the last Grooming process ran, I have no idea if I should Groom or not. 2) I noticed that after I ran the Grooming script, Retro complained that the catalog was corrupted and I was sent several errors. First it notifed me that the notification was completed: "Groomed 602.4 MB from Media Set m00522g19x." Then, 1 second later it sent me a faluire notification: "Grooming Media Set m00522g19x failed, error -2241 (Catalog File invalid/damaged)" But when I went to the Retro 8 Admin Console, I didn't seen any visual signs, icons, alerts that the Media Set was corrupt or damaged. Is this correct? I dont know which message to trust. It gets weirder... So I decide to Verify the Media Set that I was grooming just to be safe and make sure its not corrupted. After about 20 min of the Verification process, Retro is now alerting me that it needs a Media Set. This makes no sense. The Media set is 1 single file and there is plenty of free space (a few TB's) on the volume where the Media Set lives. Im only using about 20% of the allocated total space for the Media Set. This particular Media Set has 1 member. Its a very simple and small Media Set actually. I can tell if Retro wants a NEW Media Set for Some Reason or if it wants me to show it where the CURRENT Media Set is located. It makes no sense. Obviously the Verification process is doing something that I didn't expect it to do. why else would it prompt me for a Media Set? I have no idea what it ACTUALLY wants. Can someone chime in and help me figure out what is going on? Next I tried to do a "Repair" (repair the catalog). However, Retro kept prompting me for a Media Set (or a member of the Media Set). I'm positive that Retro knows exactly where the Media sets live. I dont understand why it is prompting me. What is it doing? OK Retro, you want a member, eh? OK, fine but WHICH member do you want me to show you? It doesn't tell me enough information. As a side note: • My Media Sets lives on NAS hard drives, not tapes. My data doesn't span physical drivers or tapes. Its all on a single volume. • The option to “Generate MD5 digests during backup operations†preference is enabled. • My Media Sets and Catalogs have never been moved or relocated. • I have Read the Users Guide. Page 227 covers these topics but doesn't help me.
  13. Just curious if you guy backup your Retro catalogs as part of a separate backup routine outside the normal backups, or if you perhaps use something other than Retrospect to back them up. My catalogs live in the default location (i.e; /Library/Application Supports/Retrospect), and I backup my Retro server's boot/system volume nightly (catalogs included). I have been considering running a separate rsync script to copy the catalogs to a network volume on another server as well. Seems like there is a chicken and egg paradox when you use Retro to backup its own Retro catalogs right? After all, Retro needs to write to the Retro catalog to record the contents and snapshots of the backups of its catalog which is stored in the Retro catalog that's getting backed up...by Retro. Therefore the catalog you are backing up is never totally accurate because its changing as you are backing it up. Its like the quantum mechanics allegory of Schrodinger's cat. :-)
  14. What is the best way to communicate suggestions and requests for future development of the Retrospect client and server products? I have a "bar napkin" full of ideas. Need to get them into the eyes and ears for EMC somehow...
  15. Thanks Mayoff. Will it be available in the original location that your posted? Is there a reason that its not?
  • Create New...