Hi,
Can anyone suggest me, whether it is required to signed out from GP when we are taking SQL backup? If no, will it create any error while restoring the DB?
*This post is locked for comments
Hi Mani,
You dont need to log out of GP while taking back up. But while restoring its advisable to logout all and do the same.
Hi Babu,
Thanks for your prompt response. Will I get any error when restoring the DB backup which was taken at GP users are logged in?
While I have to agree with Babu on this one - Mani we have found that leaving a user logged into the GP system when you do a backup can sometimes cause issues due to what the user might be doing at the time of the backup.
If you are just doing a quick backup so that you have a copy for a test environment - then that is not such a problem. But if you are making a historical / longer term backup - then we almost always recommend that all users are out of the system. It is more a matter of a clean database vs operational problems.
Just a slightly different angle, but all the same, both options work.
Please remember that you will not be able to restore the company database until everyone is logged out of that company. It would be best not to have anyone in GP as you need to be careful about the DYNAMICS database because of the note index field. If you have any services running that attach to the database you will need to stop them as well.
Richard, great point, I had forgotten about the index issues getting wacked.
Thanks for the reminder - I will be much more cautious moving forward now.
Hi Bill,
I need to take a daily backup. But, GP users are working in deferent time zone. So, I could see at least one user have been logged in GP at anytime. So, can you suggest me how should I plan for backup process?
Hi Manikandan,
Working with users in different TimeZones is always a little challenging.. especially when it comes to system maintenance to do backups and upgrades. As the other replies suggest, there is not necessarily a need to get everyone out of GP to perform a backup, but you can never know what it actually going on in terms of processing, posting, creation of documents when you do your backup and there are users logged in.
I'd fix some company wide policies that would state all GP users that from time X to Y, the system is unavailable for backup reasons.. I don't know how big are your company DB's, but we own a dozen companies and the largest DB is about 15GB. The whole backup process for all DB's take every night less than 10 min... so it's not that bad. Our users can understand that the system shouldn't be used at night.
Of course, you could make things very complex by running pre-backup scripts to check if the ACTIVITY table in DYNAMICS has no record before sending out notification to all the GP users (group e-mail ?) to not login into GP until time XX:XX (estimation of when your backup will be completed.).
Which version of GP do you use ? with GP 2015 there is a table that you could probably set the company locked out for any user login to prevent accidental logins while doing the full backup.
Mani,
All of them given valuable suggestions to you, and I agree with the same. When you restore a backup you can run the following script of microsoft kb in order to make sure no transaction stuck in any batches.
View the contents of the following tables to verify that all users are logged off: DYNAMICS..ACTIVITY, DYNAMICS..SY00800, DYNAMICS..SY00801, TEMPDB..DEX_LOCK, and TEMPDB..DEX_SESSION. To do this, run the following script.
SELECT * FROM DYNAMICS..ACTIVITY
SELECT * FROM DYNAMICS..SY00800
SELECT * FROM DYNAMICS..SY00801
SELECT * FROM TEMPDB..DEX_LOCK
SELECT * FROM TEMPDB..DEX_SESSION
Note When all users are logged off from Microsoft Dynamics GP, these tables will not have any records in them.
If no results are returned, go to 'Step 4'. Otherwise, clear the stuck records by using any of the following appropriate scripts.
DELETE DYNAMICS..ACTIVITY
DELETE DYNAMICS..SY00800
DELETE DYNAMICS..SY00801
DELETE TEMPDB..DEX_LOCK
DELETE TEMPDB..DEX_SESSION
Hi Beat Bucher,
Thanks for your clear explanations. We are using 2015 R2 and the full back will take around 45 - 50 minutes in our organization. We have already implemented the delete activity script before taking the backup. Also, informed users should not log into the GP at that time. But, some users not understanding the impact. Specifically many users doing the posting process at that time. Also, some users logging into GP during backup process. So, I am getting some posting related issues.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
