R
reader_guy
Objective:
to do a mid-day file backup of a group of files belonging to one
application. The application is an old-style platform, 16-bit Windows,
that has ISAM (maybe BISAM) files/databases. We could use a number of
"open file manager" products but when they make a snapshot of the
files it would be best to have no activity in progress on them.
Environment:
Windows 2000 Server Active Directory Domain. 70 workstations of which
80% are XP Pro SP2 and the rest are W2K Pro SP4.
Question:
is there a way to force this application to close at a pre-determined
time, network-wise, without just "killing" it (which might pose
concerns about data corruption)??? If so, how would we then allow the
application to run again (how would the users know when) after the
snapshot is taken?? Ideally, the workstation could do other work which
is unrelated to the application in question (which implies we do not
force a logout)
Thanks for any ideas that might help.....
to do a mid-day file backup of a group of files belonging to one
application. The application is an old-style platform, 16-bit Windows,
that has ISAM (maybe BISAM) files/databases. We could use a number of
"open file manager" products but when they make a snapshot of the
files it would be best to have no activity in progress on them.
Environment:
Windows 2000 Server Active Directory Domain. 70 workstations of which
80% are XP Pro SP2 and the rest are W2K Pro SP4.
Question:
is there a way to force this application to close at a pre-determined
time, network-wise, without just "killing" it (which might pose
concerns about data corruption)??? If so, how would we then allow the
application to run again (how would the users know when) after the
snapshot is taken?? Ideally, the workstation could do other work which
is unrelated to the application in question (which implies we do not
force a logout)
Thanks for any ideas that might help.....