Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

Maintaining Dynamics GP : Safeguarding data by Backing Up everything

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
5/23/2013 5:44:55 PM

Data backup may be the single most important maintenance item related to Dynamics GP. Backing up data is crucial to ensuring the long term integrity of the system. Dynamics GP provides a basic backup process designed to protect data and schedule full backups.

The built-in Dynamics GP backup routine is not intended to be a one-size-fits-all backup process. For example, it doesn't provide a mechanism for transaction log backups via the interface. Most companies prefer to use SQL tools to manage their backup process. Ultimately, each company should determine a recovery plan and then work with IT professionals to create an appropriate backup process.

However, the Dynamics GP backup process is an acceptable option, especially as a preference to no backup at all. The focus of this recipe is on setting up a backup process using the Dynamics GP backup routine.

How to do it...

To set up a Dynamics GP backup routine:

  1. 1. Select Microsoft Dynamics GP at the top. Select Maintenance | Backup from the Microsoft Dynamics GP menu. Enter the system password if prompted.

  2. 2. Select the company to back up. For our example, select Fabrikam, Inc. and set a backup file location. The backup location needs to exist or be created using the file lookup button to the right of the field:

  1. 3. Click on Schedule to set up recurring backups.

  2. 4. Name the schedule FABRIKAM.

  3. 5. Select the checkbox for each day to provide daily backups.

  4. 6. Set the backups to delete after 4 Weeks:

  1. 7. Click on Save to save the backup routine.

  2. 8. Repeat this process for other company databases and the System Database.

How it works...

Backing up data is the single most important maintenance function. Companies may need to go beyond the built-in backup routine to intra-day transaction log backups for true point-in-time recovery. The built-in routine does provide at least a daily backup option for protection.

There's more...

In addition to the databases, other files need to be backed up as well.

Additional Backups

Backing up the company and system databases provides the ability to restore a firm's information. However, it's important to back up the infrastructure around that information as well. Dictionary files hold customized forms and reports that can be extremely time consuming to restore. This also applies to financial statement layouts in the FRx Sysdata folder and integration definitions in the IMD file that stores integrations. Key items to back up include:

  • Any file with a DIC extension.

  • Any file with a VBA extension.

  • Any file with an IMD extension from Integration Manager.

  • The entire Sysdata folder from FRx.

  • Exports of VBA code, Custom Forms, and Custom Reports as an additional backup. These are created with the Export button found in the Microsoft Dynamics GP menu under Tools | Customization Maintenance.

Other -----------------
- Maintaining Dynamics GP : Improving stability by Managing Dictionaries
- Client Access to Exchange Server 2007 : Using Cached Exchange Mode for Offline Functionality
- Client Access to Exchange Server 2007 : Using Outlook 2007 Collaboratively (part 3) - Using Group Schedules
- Client Access to Exchange Server 2007 : Using Outlook 2007 Collaboratively (part 2) - Sharing Information with Users Outside the Company
- Client Access to Exchange Server 2007 : Using Outlook 2007 Collaboratively (part 1)
- Windows Server 2003 on HP ProLiant Servers : The Physical Design and Developing the Pilot - Time Services (part 2) - Domain Time Hierarchy
- Windows Server 2003 on HP ProLiant Servers : The Physical Design and Developing the Pilot - Time Services (part 1) - Time Services Role in Authentication
- Windows Server 2003 on HP ProLiant Servers : The Physical Design and Developing the Pilot - Network Services
- Workflow in Dynamics AX 2009 : Workflow Life Cycle (part 3) - Activating the Workflow
- Workflow in Dynamics AX 2009 : Workflow Life Cycle (part 2) - Creating the Workflow Document Class
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server