用于创建后端文件的夜间备份的正确方法 [英] Proper method for creating nightly backups of the back-end file
问题描述
这是我计划创建生产后端文件的夜间备份
（IT员工无限智慧阻止使用Windows
Scheduler并且用户没有Windows的管理权限。
Candace Tripp有一个自动备份程序，我为
使用而修改。您可以安排时间进行备份。由于我们无法使用Windows任务
调度程序，这意味着自动备份程序
必须保持打开状态。
现在，此自动备份程序将驻留在本地PC上。
上的后端文件服务器将被指定备份到服务器上名为'备份''的文件夹。
。我想我在某个地方读到，从一个位置到另一个位置（即服务器到PC或一个
服务器到另一个位置）后备文件是不是一个好主意。 。
我的计划对我来说似乎很简单合理但是我错过了我应该知道的任何东西。
谢谢。
-
通过AccessMonster.com发布消息
http://www.accessmonster.com/Uwe/For...ccess/200608/1
Here''s my plan for creating nightly backups of the production back-end file
(the IT staff in their infinite wisdom have prevented use of Windows
Scheduler and users do not have administrative rights to Windows).
Candace Tripp has an automatic backing up program that I modified for our
use. You can schedule a time for the backup to occur. Since Windows task
scheduler is not available to us, this means that the auto backup program
will have to remain open.
Now this auto backup program will reside on the local PC. A back-end file on
the server will be specified to be backed up to a folder called ''Backups''
also on the server. I think I read somewhere that it is not a good idea to
backup back-end files from one location to another (i.e. server to PC or one
server to another).
My plan seems simple and reasonable to me but am I missing anything that I
should be aware of.
Thanks.
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200608/1
推荐答案
" rdemyan via AccessMonster.com" < u6836 @ uwewrote
"rdemyan via AccessMonster.com" <u6836@uwewrote
我想我在某处读到了从
一个位置到另一个位置（即服务器到PC或一个
服务器到另一个）。
I think I read somewhere that it is not a
good idea to backup back-end files from
one location to another (i.e. server to PC or one
server to another).
你还记得读过为什么这不是一个好主意吗？
这只是我的意见，但受到业务中多个平均程序员生命周期的影响。应该那个
" backup folder"碰巧是在同一个物理驱动器上，那个物理上的b
驱动器会瘫痪，这本来就是一个非常好的想法，确实已经支持了b $ b一个不同的区域设置。
Access数据库的备份是一个简单的事情，让每个人都记录下来，这是一个非常困难的事情，这不是一件非常困难的事情。并做一个文件复制
（或压缩和修复）。
Do you remember reading "why" it would not be a good idea?
It''s only my opinion, but influenced by
multiple-average-programmer-lifetimes in the business, that should that
"backup folder" happen to be on the same physical drive, and that physical
drive were to go belly-up, it would have been A Very Good Idea Indeed to
have backed up to a different locale.
A backup of an Access database is a simple matter of getting everyone logged
off, which is not a terribly difficult thing to do, and doing a file copy
(or a Compact and Repair).
我的计划对我来说似乎很简单合理但是
我错过了我应该注意的任何事情。
My plan seems simple and reasonable to me but
am I missing anything that I should be aware of.
见上文。
我不能评论Candace Tripp'的自动备份计划 ，"因为我不是b $ b不熟悉它。
你真的很认真，IT部门不会与用户合作
部门，以确保重要的业务信息备份？在我的时间里，我已经用了很多钱来处理一些非常困难的@@@ IT部门，但没有一个人想要通过用户的升级来升级命令链到顶部
级别，然后通过他们的命令链下降他们
将关键业务数据置于风险之中。并且，通常，我们每天早上在X AM拍摄一张磁盘
图像。除了你确保没有人登录你的数据库时，你不会一直在使用/ b $ b $数据库。磁盘映像。
Larry Linson
Microsoft Access MVP
See the above.
I can''t comment on Candace Tripp''s "automatic backing up program," as I am
not familiar with it.
Are you really serious that the IT department will not work with a user
department to assure that vital business information is backed up? I''ve had
to deal with some pretty hard-@@@ IT departments in my time, but none who
wanted an escalation up through the user''s chain of command to the top
level, and then have that descend through their chain of command that they
were "putting vital business data at risk." And, the usual, "we take a disk
image every morning at X AM" doesn''t work all the time for Access/Jet
databases, unless you assure that no one is logged in to your database when
the disk image is made.
Larry Linson
Microsoft Access MVP
Candace'的程序非常好用且方便。即使对于这个新手，代码也相对容易理解，所以我能够根据我们的需求进行定制。
是的，我想知道备份到同一台服务器。但我确定我已经看到了关于在网络连接中使用FileCopy的陷阱的讨论
[不可否认这至少是6个月前我最近才知道添加了
另一年我的日历:)]。
Larry Linson写道：
Candace''s program is very nice and convenient. Code was relatively easy to
understand even for this novice, so I was able to customize to our needs.
Yeah, I was wondering about backing up to the same server. But I''m sure I
saw discussions on the pitfalls of using FileCopy across a network connection
[admittedly this was at least 6 months ago and I''ve recently added yet
another year on to my calendar :) ].
Larry Linson wrote:
我想我在某个地方看到，从一个位置到另一个位置备份后端文件并不是一个好主意。即服务器到PC或一个
服务器到另一个）。
I think I read somewhere that it is not a
good idea to backup back-end files from
one location to another (i.e. server to PC or one
server to another).
你还记得读过为什么这不是一个好主意吗？
这只是我的意见，但受到业务中多个平均程序员生命周期的影响，那应该是
" ;备份文件夹碰巧是在同一个物理驱动器上，那个物理驱动器会变得瘫痪，这本来是一个非常好的想法确实可以支持不同的地方。
一个Access数据库的备份是一个简单的事情，让所有人都记录下来，这不是一件非常困难的事情，并且正在进行文件复制
（或紧凑和修复） 。
Do you remember reading "why" it would not be a good idea?
It''s only my opinion, but influenced by
multiple-average-programmer-lifetimes in the business, that should that
"backup folder" happen to be on the same physical drive, and that physical
drive were to go belly-up, it would have been A Very Good Idea Indeed to
have backed up to a different locale.
A backup of an Access database is a simple matter of getting everyone logged
off, which is not a terribly difficult thing to do, and doing a file copy
(or a Compact and Repair).
我的计划对我来说似乎很简单合理但是
我错过了任何我应该注意的事情。
My plan seems simple and reasonable to me but
am I missing anything that I should be aware of.
见上文。
我不能对Candace Tripp的自动备份计划发表评论。因为我不熟悉它。
您是否真的认真对待IT部门不会与用户部门合作以确保备份重要的业务信息？在我的时间里，我已经有了处理一些相当难的@@@ IT部门，但是没有人希望通过用户的指挥链升级到最高层。等级，然后让他们通过他们的命令链下降，他们将重要的业务数据置于风险之中。通常，我们每天早上在X AM拍摄一张磁盘图像。除非您确保在制作磁盘映像时没有人登录到您的数据库，否则不会一直使用Access / Jet
数据库。
Larry Linson
Microsoft Access MVP
See the above.
I can''t comment on Candace Tripp''s "automatic backing up program," as I am
not familiar with it.
Are you really serious that the IT department will not work with a user
department to assure that vital business information is backed up? I''ve had
to deal with some pretty hard-@@@ IT departments in my time, but none who
wanted an escalation up through the user''s chain of command to the top
level, and then have that descend through their chain of command that they
were "putting vital business data at risk." And, the usual, "we take a disk
image every morning at X AM" doesn''t work all the time for Access/Jet
databases, unless you assure that no one is logged in to your database when
the disk image is made.
Larry Linson
Microsoft Access MVP
-
通过AccessMonster.com发布的消息
http：// www。 accessmonster.com/Uwe/For...ccess/200608/1
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200608/1
" Larry Linson" < bo ***** @ localhost.notwrote in message
news：intCg.8797
"Larry Linson" <bo*****@localhost.notwrote in message
news:intCg.8797
这篇关于用于创建后端文件的夜间备份的正确方法的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
