Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Is backup risky across a network

Discussion in 'Information Technology' started by GL, Jul 28, 2006.

  1. GL

    GL
    Expand Collapse
    Guest

    Hi,

    I’ve read many times in this forum and elsewhere that is risky to compact a
    database from one computer to another across a network.
    Is it risky too to make a backup, copy rename, across a network and in case
    of a problem to have a bad copy as well?

    Thanks
    GL
     
  2. Loading...

    Similar Threads Forum Date
    Legal Sharing Passwords with Spouse is Risky Breaking News Oct 14, 2011
    Illness: A Risky and Costly Affair for Punjabi Migrants (Part 2) Health & Nutrition Dec 21, 2010
    Adolescent Brains Biologically Wired to Engage in Risky Behavior - A Study Parenting Jun 5, 2010

  3. Alex Dybenko

    Alex Dybenko
    Expand Collapse
    Guest

    Hi,
    better idea - is to compact on local drive, and then copy result over
    network

    --
    Best regards,
    ___________
    Alex Dybenko (MVP)
    http://alexdyb.blogspot.com
    http://www.PointLtd.com

    "GL" <GL@discussions.microsoft.com> wrote in message
    news:6D13A383-FBFC-43B7-A668-C55F6CB98434@microsoft.com...
    > Hi,
    >
    > I've read many times in this forum and elsewhere that is risky to compact

    a
    > database from one computer to another across a network.
    > Is it risky too to make a backup, copy rename, across a network and in

    case
    > of a problem to have a bad copy as well?
    >
    > Thanks
    > GL
     
  4. Arvin Meyer [MVP]

    Arvin Meyer [MVP]
    Expand Collapse
    Guest

    In addition, make a copy of the file, before doing a compact. Do the compact
    on the copy. Then the chance of messing anything up is low to nil.
    --
    Arvin Meyer, MCP, MVP
    Microsoft Access
    Free Access downloads
    http://www.datastrat.com
    http://www.mvps.org/access

    "GL" <GL@discussions.microsoft.com> wrote in message
    news:6D13A383-FBFC-43B7-A668-C55F6CB98434@microsoft.com...
    > Hi,
    >
    > I've read many times in this forum and elsewhere that is risky to compact

    a
    > database from one computer to another across a network.
    > Is it risky too to make a backup, copy rename, across a network and in

    case
    > of a problem to have a bad copy as well?
    >
    > Thanks
    > GL
     
  5. '69 Camaro

    '69 Camaro
    Expand Collapse
    Guest

    Hi, GL.

    > Is it risky too to make a backup, copy rename, across a network and in case
    > of a problem to have a bad copy as well?


    The risk lies in an interrupted database write-to-disk operation, which is
    more likely when conducted from across the network than when conducted from
    the same workstation. Backups can be made using different methods, but when
    conducting a backup via Microsoft Access, you are accessing the current
    database file. You might notice that the file has increased in size after
    you've created the backup file, which means that Jet was writing to the
    original file during the backup. So it's a bit risky if you're trying to do
    this across the network, and I wouldn't recommend it.

    Copying and renaming a file from across the network is fine, as long as the
    database is closed when you do so. The reason it should be closed is that if
    someone is actively using it, then it could be in the middle of a write
    operation when the file is copied, or it could be in the middle of a
    transaction that has not yet been completed. The former would cause the file
    to be marked as "suspect," as in possible file corruption. The latter would
    cause loss of data integrity. (After all, you don't want a transaction that
    debits your savings account to be halted before your checking account is
    credited with the same amount, do you?) The reason that it's fine from
    across the network is because while your workstation is passing the commands
    to copy the file and paste it, the networked computer's operating system is
    actually executing these two operations from its own queue, so there's a far
    less likely chance of failure that these operations will be interrupted.

    To safeguard the original file, make a copy of the database file before any
    backup or compact of the database via Access, and then do the operation on
    the copy, not the original.

    HTH.
    Gunny

    See http://www.QBuilt.com for all your database needs.
    See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
    http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.


    "GL" wrote:

    > Hi,
    >
    > I’ve read many times in this forum and elsewhere that is risky to compact a
    > database from one computer to another across a network.
    > Is it risky too to make a backup, copy rename, across a network and in case
    > of a problem to have a bad copy as well?
    >
    > Thanks
    > GL
     
  6. Tony Toews

    Tony Toews
    Expand Collapse
    Guest

    GL <GL@discussions.microsoft.com> wrote:

    >I’ve read many times in this forum and elsewhere that is risky to compact a
    >database from one computer to another across a network.


    Then those folks are wrong. I have many times compacted a 300 mb
    database over the network.

    >Is it risky too to make a backup, copy rename, across a network and in case
    >of a problem to have a bad copy as well?


    Yup, that's a possibility too isn't it.

    Tony
    --
    Tony Toews, Microsoft Access MVP
    Please respond only in the newsgroups so that others can
    read the entire thread of messages.
    Microsoft Access Links, Hints, Tips & Accounting Systems at
    http://www.granite.ab.ca/accsmstr.htm
     

Share This Page