UNSOLVED

saniej

updated

19 years ago

S

saniej

19 Posts

0

3196

July 18th, 2007 05:00

not in index nothing to recover

I have Windows 2003 SE as NW Server. Two Solaris 9 Client. When doing a directed recover with NW server as administering server, recovering from 1st solaris to second solaris client. im getting Warning: could not establish job id with jobd.
recover: /file not in index
recover: Nothing to recover

am i missing something or perhaps wrong config?

Thanks
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    839

    0

    Posted July 18th, 2007 05:00

    I never tried to do restore of Solaris box from Windows administrating box, but if that works then you might have an issue with permissions being set.
  • saniej

    19 Posts

    839

    0

    Posted July 18th, 2007 05:00

    hm...that's sad. I'm currently doing a POC for this potential customer. I hope there's someone out there who have tried this environment before.
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    839

    0

    Posted July 18th, 2007 06:00

    Well, have you set permissions first?
  • saniej

    19 Posts

    839

    0

    Posted July 18th, 2007 06:00

    yup i added two root@solarisbox in the administrators group from both client and edit the hosts and server.res file.

    what else did i miss sir?
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    839

    0

    Posted July 18th, 2007 07:00

    Did you check if local nsrla has directed recoveries enabled? I assume servers lists both server and admin box now...
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    839

    0

    Posted July 18th, 2007 09:00

    I quickly checked admin guide and from what I'm reading it should work. I think once you are on admin you have by default remote access all permissions, but perhaps just be safe you could explicitly add users to remote access too to both machines.
  • saniej

    19 Posts

    839

    0

    Posted July 18th, 2007 09:00

    nsrla...will try that one.

    yup both servers and admin box are in the list
  • saniej

    19 Posts

    839

    0

    Posted July 18th, 2007 10:00

    yup thats what i thought also..

    only, i already tried putting root@solarishostname on both clients remote access resource...

    ...why is it saying that the file is not in index when i could browse them using networker user? really wierd...im sure im just missing something
  • 616

    0

    Posted July 18th, 2007 12:00

    I just had another thought. I experienced a similar situation a few weeks ago.
    Be sure you can ping the unix clients to each other. I had to add host file entries (long and short name) on both client's for each other and for the backup server and storage node. In order to read the indexes of the source client I am pretty sure destination client needs to be able to hit the Networker service on the source client.
  • 740

    0

    Posted July 18th, 2007 12:00

    In the client config index path field try putting the path to the client's indexes.
    I am not sure about windows but Networker Server on a unix box the path for the indexes is /nsr/index.

    Find /nsr/index on your windows box and add that path in the client config.