Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Problem with built-in backup

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem with built-in backup

    For the last several months, we have been having problems with the nightly backups, using Alpha's built-in backup. Almost every time, there are several .ddd files that do not get backed up, because Alpha thinks that they are in use (see attached file). I ran a database compact, which worked fine, with no errors, but when I immediately attempted the backup again, there were several .ddd files that could not be backed up because they were "in use." I attempted to edit field rules for the tables whose .ddd file was in use. Sometimes it claimed that the table was in use, and sometimes it didn't. Any ideas what could be wrong, or how I could troubleshoot this?
    You do not have permission to view this gallery.
    This gallery has 1 photos.

  • #2
    When no one else is using Alpha on any workstation, go to the control panel in Alpha. Choose File menu; Choose Database Information. Open tables or sets will be marked.

    Is it possible these files were left "in use" on the machine acting as server for your application? If so, have you shut down and restarted the machine that's acting as server for your Alpha application?

    -- tom

    Comment


    • #3
      Thanks for the suggestion, Tom. I'll have them restart the server before the next backup, and report back.

      Comment


      • #4
        Nathan,

        You do not say what Alpha build you are using.

        I would do what Tom suggested.

        If after that you are still experiencing problems, I would submit a bug report. I think that there might be a bug. There are other posts on this board where people can not restructure a table. They are getting the table in use message also.

        To confirm that it may be a bug, go back to the alpha build you were using before you had any issues. You may want to do this by coping the entire workspace into a sandbox where you do not have to worry about damaging your live data.

        Note: You can have multiple installations of Alpha Anywhere on you computer. This way you can have different builds of AA where you can test before making any changes to the live application. I personally have five different installations of AA, each a different build.

        Ron
        Alpha Anywhere v3.5
        Version 12.3, Build 2999
        MySql56 & DBF's

        Alpha 4, 5, Anywhere

        Ron Anusiewicz

        Comment


        • #5
          Thanks for the input, Ron. We are using the current version, but just recently upgraded, and the problem predated the upgrade. Before upgrading, we were using a version that was at least a year or two old.

          Nathan

          Comment


          • #6
            I’m using both build 2999 and build 4269 to run different applications. The backup works fine in both along with table restructuring. Just after build 4269, Alpha went with a new version of .net primarily for WEB side development. This required rewriting much code supporting the desktop side of things. In my experience it, it also broke many features on the desktop. I submitted many bug reports and they were fixed.

            So if there was a time when your backup did work and then it stopped working correctly, coupled with the fact that others are experiencing a similar error even though they are doing a different task, this still may be a bug.

            Ron
            Alpha Anywhere v3.5
            Version 12.3, Build 2999
            MySql56 & DBF's

            Alpha 4, 5, Anywhere

            Ron Anusiewicz

            Comment


            • #7
              This issue was set aside for awhile because of other priorities, but now I'm back to working on it again. I made a copy of the entire database and put it on another computer, opened it up using the same build of Alpha, and the backup worked fine. This leads me to believe that it's not necessarily related to a build issue. The working database is used by several people on a network, but the backup is run at night after all of the users have shut down Alpha. Some of the files that are not being backed up are from temporary tables that are not normally being used, so it seems unlikely that they were even in use the day of the backup. Any other ideas?

              Comment


              • #8
                Also, I just noticed that of the 18 files that were not backed up last night, all of them were .ddd files, except for one .dbf file.

                Comment


                • #9
                  Suggest you use a 3rd party one.
                  Datareplicator is a Synology freebie
                  You can schedule as you wish and include what you want.
                  Ted Giles
                  Example Consulting - UK
                  .

                  sigpichttp://ec12.example-software.com//
                  See our site for Alpha Support, Conversion and Upgrade.

                  Comment


                  • #10
                    Nathan, I suggest you configure the "copy" you made to do its backup overnight. That's a truer test in my opinion. If the same omissions occur in the "copy" look for other processes that are running overnight. Is it possible malware scans are running? Might they open and close your alpha files, preventing alpha from including them in your backups? Another thought: are some of your users logging in remotely during the night?

                    Comment


                    • #11
                      I thought backup was supposed to close all files, Tom.
                      Ted Giles
                      Example Consulting - UK
                      .

                      sigpichttp://ec12.example-software.com//
                      See our site for Alpha Support, Conversion and Upgrade.

                      Comment


                      • #12
                        Ted, I'm used to running much older versions, so perhaps the backup sequence in Alpha was changed. In earlier versions tables can't be backed up if they're in use. Just like Database Compact restriction.

                        What Nathan describes is very odd. I'm wondering now if his workspace is entirely located within a single folder (without subfolders ?

                        Wondering also if he's using a conventional PC or Server to host his application. NAS devices aren't recommended as I recall.

                        -- tom

                        Comment


                        • #13
                          Tom, yes, the workspace is entirely located within a single folder.

                          To test this further, I copied the entire database into a subfolder on the same network drive where the live database is. When I ran a backup on that copy, again a couple of files were not backed up because they were "in use." In this case, there certainly were no other users logging in remotely. (I'm confident that is not happening with the live database either.) There still is a possibility that there is a malware scan interfering. I will check into that.

                          Nathan

                          Comment


                          • #14
                            Only other thing I can think of is where the backup is being put.
                            Windows doesnt like software messing with Prog Files folders,that's why most peole put the apps in a folder outside the Prog Files one.
                            Ted Giles
                            Example Consulting - UK
                            .

                            sigpichttp://ec12.example-software.com//
                            See our site for Alpha Support, Conversion and Upgrade.

                            Comment


                            • #15
                              I have confirmed that the antivirus software does not scan the Alpha folder. The database is on an HP server running Windows Server 2016 Standard. The backup is done to a USB external hard-drive connected to the Alpha computer.

                              Since it is almost always only a few .ddd files that are not getting backed up, and they are usually for non-essential tables, and it varies from night to night which files are skipped, we will probably just live it, as it's very unlikely that important changes will be permanently lost. Thanks to everyone for your input!

                              Comment

                              Working...
                              X