Microsoft Word Hardware Reconfiguration Methodology V final2

Users and applications

User-based data can generally be restored at any time; the only time this may be problematic is when a currently opened file is undergoing modification by the user and/or application or service. In such a case, the file cannot be replaced without causing data loss to the file. In such cases, it is normal for the system administrator to request that affected users be logged off the system by a

given time so that the restoration can continue. In cases where the user cannot logoff from the system the data can always be restored to an alternate directory and then copied over to the appropriate location at a more appropriate time. If necessary, however, the system administrator can forcibly logoff a user and shut down his applications and open files; however, this should be left as a last resort to users in a state of non-compliance.

10. Databases

Database applications should always be shut down before restoring any database file. Unlike many other applications, database applications are data-specific and cannot generally be left operational even if the databases are currently unmounted; even unmounted database on quiescent systems can result in data loss, corruption, or database application crash if a database file is restored while the application is running. Database files do not necessarily require mounting in order to be considered as actively used by the application. In part, this can be attributed to the fact that database applications, generally initialized by scripts, may maintain journaling and buffered information about its files, even if they are unmounted. However, this will vary from application to application and as such, it is important to be somewhat familiar with the database application and how it works with respect to its database files. Reading the application’s user and administrator manuals may provide further clarification.

11.