Backing Up Within A Multi-Mode Environment

Ok so my multi-user environment ended up being really simple to push out however there have been a few glitches. One being within Payroll, where our page setting had switched from Pre Printed, which with 2 sets of eyes we figured out. Today one of the users told me they were unable to perform a backup while in multi-mode, although the other user was not logged in.

The user had to put the software back into single user mode to do a backup, does this make any sense????  We have not changed to the server installation yet as we had the capability of multi-user all the time, accounts were just not setup so nothing has changed other than setting up multi-mode.

  • multi user mode is not how many users are connected
    it is the selection you choose when you login
    one user can connect in multi user mode, allowing other to connect in multi user mode
    but only one user can connect in single mode when no one else is connected
    if only one user is connected in multiuser mode, they need to switch to single user mode for backup
  • in reply to Roger L

    I fully understand multi-mode and if what you are saying is correct then either the software has a bug or it's poorly designed. If what you are saying is true this would mean all users would have to close the application. Then one has to reopen once again in single mode just to back up, doesn't make any logical sense at all. Multi-mode should simply detect and warn that other users are still using the database and to close all instances but one, then perform a backup, not completely have to shut down the program only to reopen in a different mode. I will setup s scheduled backup and see what happens when both users close off the application at the end of the day and see if it automatically performs the backup. Thanks Roger.

  • in reply to DMIMAGE

    DMIMAGE said:
    If what you are saying is true this would mean all users would have to close the application. Then one has to reopen once again in single mode just to back up

    This is the only certain way to get a full and consistent backup of *any* database.

    DMIMAGE said:
    not completely have to shut down the program only to reopen in a different mode

    There is an option under the File menu to switch between 'Single-user mode' and 'Multi-user mode'.   It will completely close the database, then reopen the data file using a different type of connection, which prevents any new connections.  

    Switching from one mode to another does not completely unload the application from memory and reload it from disk.  It takes 10 seconds on our gigantic file, it's more of a screen flicker on smaller files.

    DMIMAGE said:
    I will setup s scheduled backup and see what happens when both users close off the application at the end of the day and see if it automatically performs the backup.

    If you mean a backup that doesn't use the Sage 50 backup module, then it will usually work fine.   It is best to check whether a file called 'process.pid' exists, in the company data '.SAJ' folder.   If it's not there, there are no open connections, and any backup software can make a copy of the data.

    The Sage 50 Automated backup should do what you want.  

    I hope that helps, please post back.

  • in reply to RandyW
    Thank you Randy for confirming what Roger had said, appreciate that. The backup I was referring to was one that I noticed in the Sage 50 User guide under Settings, that allows you to set an automatic backup when the software is closed. So now you have got me thinking about looking for pids, and how it all works. Hmm.
  • in reply to DMIMAGE

    DMIMAGE said:
    The backup I was referring to was one that I noticed in the Sage 50 User guide under Settings, that allows you to set an automatic backup when the software is closed.

    I just did a quick test with a multi-user data file, the backup did not start, unless the last person to close the company file was in Single-User Mode.

    DMIMAGE said:
    now you have got me thinking about looking for pids, and how it all works. Hmm.

    It's not all that mysterious, really - the workstation (client) makes contact with the Connection Manager (server), which checks the license, etc. before starting the MySQL Database. 

    The PID file contains the Windows 'Process ID' of the database until the database is shut down.  If the file with the PID isn't there, the database is not running, and it's safe to cut / copy / paste / backup the Company data files.  

    If it is there, the database is running, or the database wasn't shut down properly (someone tripped over the power cord, etc.)

    Somewhat like a 1940's telephone operator, the Connection Manager then gives a new port number to the workstation and the MySQL Database daemon.  Picture Ruth Buzzy...