Example Backup Strategies : Here is a backup strategy for full daily backups. Ensure NO other backup product is installed. Create a backup set for each day of the week (TOOLS->BACKUP SETS- >NEW from the context menu): (Monday,Tuesday etc.). I assume these will be called (Monday, Tuesday etc.). The Monday backup method will direct data to the Monday backup set, the Tuesday backup method will direct data to the Tuesday backup set and so forth. The "changed files only" flag should be switched off and the source will be "Allow backup of all files". Make sure that all local drives you want backed up are in the "Source drives scanned for backup" container (TOOLS->SOURCE DRIVES). You can use the refresh option from the context menu if all drives are not present. You can drag and drop drive icons between the top and bottom sections. Decide the degree of logging you want. The control panel allows you to select "log failures only" if you don't want the log to become too large. Run the Monday backup. Label and insert tapes when requested. The first tape will be called Monday-1. The one you insert half way (if needed) through the backup will be called Monday-2. NOTE: With a P200 and 64 MB of RAM we see data rates of less than 1GB per hour. If you have a significantly more powerful machine you may achieve a better rate. The backup, I have proposed includes the NET.ACC file. If "backup of ACLs" is switched ON in the control panel, "BACKACC" will run for each logical drive. This may add 30 minutes to the backup time. Check that the backup has completed successfully. Open the "backup set container", select the "Monday backup set" and choose "view log" from the context menu. Files that have "NOT" been backed up for any reason will be marked with an 'X' in the left hand column. The most common reason for a failure is if another process on the system has locked the file and prevented PSnS from reading it. SystemView, for example, locks some files in this way. You may want to shut down certain programs, before you run the backup so that ALL files can be backed up. NOTE: The OS/2 system includes some log files that are locked open "Deny Read"; therefore, not backed up. Such files are recreated by the system so you do not have to worry about a failure backing them up. NOTE: To automate the process of shutting down certain programs before a backup runs, write a "User exit" procedure. Example procedures are provided in the system directory and instructions in the on-line help. When the Monday backup completes "EMPTY" the backup set. This ensures that you can reuse tapes Monday-1 and Monday-2 next week. To "empty" the backup set open the backup set container, select the Monday backup set and choose the "empty" option from the context menu (This doesn't actually delete the data, the "index" is removed and stored). Create "Disaster Recovery" diskettes (Full instructions are given in on-line help). If you have installed the new version of PSnS, it is important to create NEW "Disaster Recovery" diskettes, the PSnS program files on the third diskette will only be at the prior level if new DR diskettes are not created. NOTE: If you intend to restore the production system image to an alternative machine the systems must be identical in all respects. In particular you need to ensure that the new system can be driven by the same set of device drivers. Test the disaster recovery process fully on the reserve server. Run the backup methods for the rest of the week just as you ran Monday's. ===================================================================== Albert Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/What_Error_Messages_Really_Mean_IBMOS2/ <*> To unsubscribe from this group, send an email to: What_Error_Messages_Really_Mean_IBMOS2-unsubscribe@xxxxxxxxxxxxxxx <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/