Microsoft Word Hardware Reconfiguration Methodology V final2

Backup schedules

It is important to determine when backups can be scheduled before proceeding with any backup- related action. Consider the following:

1. 
   When are the systems to be backed up? Are they to be done at night, during the day, or on weekends? Backups should be done when all necessary resources are available.
   

2. 
   Are network resources available 24x7 for remote backups? Is there more bandwidth available on weekends and at night? If so, then backups should be scheduled for these times.
   

3. 
   Are backups planned to coincide with increased network bandwidth availability? If backups are to be performed over the network and there are large data transfers to occur between one or more systems to a backup server, then backups should be carried out when network activity is low.
   
4. 
   Do actively used user files and applications affect backups? If so, then backups of user files and applications should occur when the users have logged off. However, if in use files and applications do not affect backups then they can be scheduled for any time.
   

5. 
   Do certain operating system services and/or applications interfere with the backup process? If so, then a schedule should be made for when they can be disabled so that the operating system can be backed up. If they do not interfere, then they can be backed up at any time.
   

6. 
   Are certain key files or data locked or unavailable? If the backup can continue without those files then the backup should be made when ever possible. However, if the files are required for a successful backup and the tools Dump or DD are not able to acquire them then a time should be scheduled to offline the system for backup using a rescue or Live CD.
   

7. 
   How will backups be scheduled and executed? If they are using the system’s scheduler then backups can be automated. If they are executed from the command line then a backup operator will be required. In either instance, scripts can be used for automation.
   

3.