Navision Recovery

fredp1

Hi,

If you needed to perform a restore due to a disaster, what would be the steps to get a "company" up and running?

We are using Nav 5, on SQL 2005 and also run Reporting Services. All backups are been performed by BackupExec. 1 job for all files using Advance Open File Agent and 2nd job that uses the SQL Server Agent to backup the db's. We are running 2 NAS servers and have some shared tables used by Nav and 3rd party apps.

If we assume that the old server/box is trashed can someone check the steps for a recovery?

I would get the O/S instaleld and the backup software.
Restore all O/S files, system state/registry via tape
Restore all SQL databases using the Backupexec SQL agent via tape

Is it more complex than that or is there a few catches?


Also, if we just restored the Navision production database, then we would need to install the client, the NAS servers, the license
and apply any other permissions needed to make the 3rd party apps work?
Then restore the SSRS report server db's

Thanks

rdebath

The only way to be sure is to try it. In addition to proving the backups a full "DR test" would give you some practice and real world timings. If you don't have a spare machine, or virtual machine, you can rent them.

Anyway, related information; this is a barebones restore of just the Navision database. You need an SQL backup of just the DB, (master too would be nice though) the Install CDs and the License files & keys. NASs are usually very quick to reinstall so all you really need is the settings. Other applications are are more of a problem.

You may need this if you get some sort of gradual corruption of the machine and it's backups (eg a really evil virus).

SQL Restore to SQL
------------------
Procedure for SQL restore, assuming master database has NOT been backed up:

1)       Install windows join to the domain and install MS-SQL 
2)       Install the xp_ndo.exe 
2a)      If on 3.70A the stored procedure xp_enumuserids has to be created
         manually.
3)       Install Navision Client 
4)       Restore the SQL Backup
5)       Start Navision client 
6)       Change to real License (FLF)
7)       Connect to database 
8)       Upload the real License (FLF) to the database (Tools->License->Upload)
9)       Perform Tools->Security->Synchronize 
10)      If the Sync fails complaining about database users, 
         add them through enterprise manager and repeat Sync
11)      If the Sync fails complaining about windows users, 
         delete them from Navision and repeat Sync

NOTE: This loses passwords for any database users as they are stored 
      in the master database.

DenSter

You can ask for lists like this all you want, but they are absolutely useless when you have to actually restore the system. You need real world experience. What you need to do is practice. Do it. There's nothing like actually restoring your system to find out that you are not backing up one of the most important elements in your setup, or that your backup procedure is wrong. I once had a customer that saved their backup files on the Transaction log disk, because there was so much "wasted space". Guess what would happen if their disk has a bad sector?

About your 3rd party add-ons, you need to inventory what you have and how to set everything up, and create your own checklist from there. If you are using a software program to back up your databases, you need to know how to use it to restore them.

fredp1

Hi,

Thanks for the replies. We will test it in a real live (test) enviroment, but it helps to make sure that your on the right path to start off with.

Cheers
Fred

rdebath

DenSter wrote:

Guess what would happen if their disk has a bad sector?

If all you had to guard against was bad sectors then putting several copies onto the transaction disk would be a GOOD idea. In fact basic mirroring (+spare) would be enough.

OTOH a short in the power supply that pushes 240 volts onto the 5 volt bus could pop the top off every chip in the machine and put pretty arc patterns onto all the hard disks.

A little bit of water in the wrong place would do the trick...

DenSter

rdebath wrote:

If all you had to guard against was bad sectors then putting several copies onto the transaction disk would be a GOOD idea. In fact basic mirroring (+spare) would be enough.

They put everything on one disk, because they thought that the unused disk space was wasted otherwise. Data file, transaction log, and backups, all on one disk, not an array but one disk, and no regular backup. A disk failure is all that needs to happen to lose everything.

The point is that you need to think about each configuration, because there's always something that makes it unique. Asking the forum for a list is not going to really help if you don't actually practice disaster recovery. You can tell someone to do it one way, but then there is something about their situation that makes it so you can't do that.

honeycrippen12

Good info...Well guys...I don't have any personal knowledge about it but here's a site in my knowledge that disaster recovery plan which provides that kind of services so use it. It might have been useful for u.

Honey