You’re offline. This is a read only version of the page.
5
We are currently in the process of migrating away from our NAV 2013R2 environment. We have the app installed on a VM and the database on another. Later this year we expect to be upgrading some servers and possibly decommissioning some others. The NAV environment will be impacted by this, however we expect we will be done with it before we begin our server work. I was wondering what the best option might be for archiving the NAV environment but still having it available in the event we may need to spin it up again for audit or other accounting requirements. One thought was to consolidate the app and DB to a single VM and then shutdown the VM and keep it backed up and near line in the event it is required. But I really do not have much experience when it comes to NAV and was hoping to get some ideas and best practices from the community.
I agree on the SQL backup. Regardless of any connectivity issues, you could still retrieve data for an auditor via SQL queries.
And in case this was your concern, combining both the service (app) and the SQL db onto 1 server vm is not an issue at all. Seems like a good solution to me.
In addition to creating the virtual machine i would recommend you also take a separate backup of the SQL database and store that in a safe storage outside your VM in case something should happen to your VM.
I witnessed a similar case where then only had it in a WM then someone by accident had deleted the WM because they thought it was not used anymore. So take a full sql backup in addition to the WM.
Hi, One thing to note is the license, if your license is expired, you will not be able to open NAV anyway.
As for how you configure the server, if there are not many users accessing NAV, I recommend putting it in a virtual machine as well.
Hope this helps.
Thanks.
ZHU
#1
Sohail Ahmed
858
#2
YUN ZHU
773
Super User 2025 Season 1
#3
Mansi Soni
569
Share
Report
All responses (
Answers (
