dstranathan
Occasional Forum Poster
Posts: 48
|
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)
Edited by dstranathan on 07-25-10 05:13 AM. Reason for edit: No reason given.
|
 Maser
Retrospect Veteran
Posts: 1968
|
In response to dstranathan
This should be a KB article as it seems to come up a lot...
The basic thing to do:
1) stop the engine. Wait up to 10 minutes after clicking the "stop" button in the Pref Pane. At 10 minutes (if not before) -- it should stop.
2) Move the catalog file for the media set out of it's normal location.
3) Start the engine. The grooming script will fail because it can't find the catalog file.
4) Fix/delete the grooming script.
5) Rebuild the catalog (recommended). Or put the catalog file back and see if you can use it.
|
Daniels
Gold Club Member
Posts: 464
|
In response to Maser
It is also suggested that you upgrade to 8.2 Beta 2.
|
hmseiden
Occasional Forum Poster
Posts: 166
|
In response to Maser
This should be a KB article as it seems to come up a lot...
Yep.
Here's a caveat that seems important if you intend to repair or rebuild a backup set... Disable all scripts so Retro doesn't try to use them before a repair/rebuild begins!
In my case of a blown groom, I found another 4KB file with the same name(?), it was in the directory where the backup catalogs reside. Deleted.
Able to pull in (Finder copy) an old saved catalog to allow a repair (faster). Now verifying/resynchronizing the catalog...
Will post further results.
Henry
Retrospect Desktop + Client pack: Engine 8.2.0, Console 8.2.0(399)
Local CPU (Server): Mac Mini, Intel Dual Core 2GHz/3GB RAM, 120GB; 2x1TB FW800 ext. drives, OS X 10.6.4
Client 6.3.029 desktop : Mac Pro 2.66GHz Dual Core, 5GB RAM, OS X 10.6.4
Client 6.3.029 laptops : MacBook Pro 2.53GHz/4GB Intel 5,1; MacBook Dual Core 2GHz/2GB, OS X 10.6.4
|
|
hmseiden
Occasional Forum Poster
Posts: 166
|
In response to hmseiden
After 23 hrs. total trying to replace/restore/rebuild the catalog, 13 hrs. on a "Resynchronizing..." display, I gave up and ditched the media set altogether. My next oldest backup was two days old and decided to go with that, deleting this catalog and media files. Did new backups of clients overnight (last one has just completed).
BTW, on what may be a related topic, I previously increased my network speed to 1000Mb/s (GigE). And speed increased for this backup. I'm guessing that Retro's net throughput increased <2x for a network speed boost of 10X. Are there any figures measuring this?
Henry
Retrospect Desktop + Client pack: Engine 8.2.0, Console 8.2.0(399)
Local CPU (Server): Mac Mini, Intel Dual Core 2GHz/3GB RAM, 120GB; 2x1TB FW800 ext. drives, OS X 10.6.4
Client 6.3.029 desktop : Mac Pro 2.66GHz Dual Core, 5GB RAM, OS X 10.6.4
Client 6.3.029 laptops : MacBook Pro 2.53GHz/4GB Intel 5,1; MacBook Dual Core 2GHz/2GB, OS X 10.6.4
|
|
Maser
Retrospect Veteran
Posts: 1968
|
In response to hmseiden
I don't have a cite for this, but "real world" network performance is not 10x faster going from 100Base-T to Gigabit Ethernet. I think Gigabit tops out (on a Mac) at around 30Mb/s.
But, from what I remember when we went through this years ago, going from 100Base-T to Gigabit usually only results in a 2-3x speed increase (faster with larger files)
|
08-09-10 02:03 AM - 