In the first quarter of 2013, we came across a couple of situations where database backups were not taken prior to the year-end close procedures being run.  Running the year-end close processes is usually not a big deal if everything goes well, but what if something goes awry?

The year-end close documentation beats you over the head with reminders for database backups, but it is done in your best interest.  The database backups serve as a safety net in the event that some unforeseen event occurs.  In both support cases, I strongly suspect that there were hard drive space issues that did not allow the database to grow while closing the year, which killed the year-end close process midstream.  The end results were no year-end posting journal being printed and the year-end balances not closing out properly in the fiscal year being closed.  In addition, there were no beginning balances posted in the new fiscal year.

Back up your Dynamics GP Databases

Take the extra 10 minutes to have your Dynamics GP databases backed up.  And while the backup is being taken, check the hard drive(s) on which your data and log files are stored to ensure you have a good amount of space to work with (this will vary with the size of your Dynamics GP database).  If you have any doubts, or questions, you can always contact us. Believe me, the 10 minutes spent on the database backup will save you hours in support calls.

George Rios is a Microsoft Dynamics® GP Certified Professional and senior consultant at Bond Consulting Services. He has over 13 years of work experience with accounting and accounting systems.

The BCS Team also recommends: Move Forward with Year-End Closing in Dynamics GP