NetWorker Blog

Commentary from a long term NetWorker consultant and Backup Theorist

  • This blog has moved!

    This blog has now moved to nsrd.info/blog. Please jump across to the new site for the latest articles (and all old archived articles).

  •  


     


     

  • Enterprise Systems Backup and Recovery

    If you find this blog interesting, and either have an interest in or work in data protection/backup and recovery environments, you should check out my book, Enterprise Systems Backup and Recovery: A Corporate Insurance Policy. Designed for system administrators and managers alike, it focuses on features, policies, procedures and the human element to ensuring that your company has a suitable and working backup system rather than just a bunch of copies made by unrelated software, hardware and processes.

  • This blog has moved!

    This blog has now moved to nsrd.info/blog. Please jump across to the new site for the latest articles (and all old archived articles).

  •  


     


     

  • Twitter

    Error: Twitter did not respond. Please wait a few minutes and refresh this page.

«
»

Basics – Directed Recoveries

Posted by Preston on 2009-09-21

Hi,

This blog post can now be read at the NetWorker Information Hub.

About these ads

This entry was posted on 2009-09-21 at 05:36 and is filed under Basics, NetWorker. Tagged: , , , . You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

2 Responses to “Basics – Directed Recoveries”

  1. tbozzio said

    2009-10-22 at 21:01

    This is a fantastic guide Preston.

    I would add 1 extra point to resolve issues that I have seen when running directed recoveries:

    7. Place the destination client name [short name, long name & all aliases – 1 per line] in the /nsr/res/servers file on the source client. Restart nsrexecd afterwards.

    • Preston said

      2009-10-23 at 04:45

      I can’t say I’ve ever observed that need before. However, that almost sounds like it’s caused by some permissions problem — or maybe name resolution. Regardless, thanks for the suggesting it – if someone encounters problems with the traditional method as well they may find that your suggestion helps get them over the line :-)

Sorry, the comment form is closed at this time.

«
»
 
Follow

Get every new post delivered to your Inbox.

%d bloggers like this: