mibuso.com
Home› NAV/Navision Classic Client

WHAT is Navision Documentation for Disaster Recovery?

SapotSapot Member Posts: 50
edited 2008-02-11 in NAV/Navision Classic Client
A client is scheduled to sign up for Disaster Recovery, who would maintain a server seperately in some location and in case of any disaster they would restore the NAVISION data in 48 hours.
Now in case of DISASTER what all is required to RESTORE NAVISION services to normalcy is to be documented.can anbody suggest me what is required to be DOCUMENTED?

Comments

  • bbrownbbrown Member Posts: 3,268
    48 hours? :?
    There are no bugs - only undocumented features.
  • kinekine Member Posts: 12,562
    Native or MS SQL Server?
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • bbrownbbrown Member Posts: 3,268
    Seriously, if SQL consider log shipping or mirroring. 48 hours seems like a long time for recovery considering the servers already exist. This would imply that the setup is already there and only the data needs to be restored.
    There are no bugs - only undocumented features.
  • SapotSapot Member Posts: 50
    Its Native DataBase
  • SapotSapot Member Posts: 50
    It's like they dont have any idea of any DATABASE, Recovery is to be designed for all implementations, and my role is to define or design for NAVISION in case of DISASTER.
  • kinekine Member Posts: 12,562
    It means you need to write something like:

    If there is some disaster, than man X will take backup of the database from place Y (folder, safe etc.), on backup computer A will start NAV client in this and this way/ or will place database copy into folder YZ and will start service xxxx...

    It means some step by step how to restore the backup with all informations like how the backup computer is prepared, what must be kept up-to-date etc. It means, if there is flood and IT admin is killed by accident, or is drunked somewhere, you need to do HOW TO steps for dummies.
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • SapotSapot Member Posts: 50
    Something like 1)Scope 2)Overview 3)PreConditions(necessary for the recovery of applications /services that need to run,database services that needs to be recovered first etc ) 4)Step by step recovery(which can be utilised to check for the sucessfull recovery of database) and finally 5)Testing. That's what is required to be documented.
  • kinekine Member Posts: 12,562
    If you know what you need to describe, what you are expecting from this forum?
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • SapotSapot Member Posts: 50
    May be i am not putting my point properly, The points that i have put in are of my opinion but...... this being my first experience i would like to know here
    How do i elaborate it and is there anything very important that you think i need to document in case of DISASTER, which should complete my NAVISION DATABASE recovery perfectly.
  • tcsrtcsr Member Posts: 1
    Any such type of documents to be legally viable, in case of failure of services. pls. include the clause of damages payment in case of fail in services and also consult a legal person to document it legally.
    Navision
  • idiotidiot Member Posts: 651
    A lot depends on the environment you're in, the type of hardware, backup procedures in place, etc...
    The best is to consult an IT Auditor & work closely with the management to come up with a plan that meets THEIR expectations.
    NAV - Norton Anti Virus

    ERP Consultant (not just Navision) & Navision challenger
  • hrishihrishi Member Posts: 21
    Hey guys, just wondering if anyone came up with a DR template plan please?
Sign In or Register to comment.