System Administration Guide, Volume I

Example--Backup Schedule for a Server

Table 33-13 shows an example backup strategy for a heavily-used file server on a small network where users are doing file-intensive work, such as program development or document production. It assumes that the backup period begins on a Sunday and consists of four seven-day weeks.

Table 33-13 Schedule of Backups for a Server Example

Directory 

Date 

Level 

Tape Name 

root (/)

1st Sunday 

n tapes

/usr

1st Sunday 

"  

/export

1st Sunday 

"  

/export/home

1st Sunday 

"  

 

1st Monday 

 

1st Tuesday 

 

1st Wednesday 

 

1st Thursday 

 

1st Friday 

 

1st Saturday 

root (/)

2nd Sunday 

n tapes

/usr

2nd Sunday 

"  

/export

2nd Sunday 

"  

/export/home

2nd Sunday 

"  

 

2nd Monday 

G  

 

2nd Tuesday 

H  

 

2nd Wednesday 

I  

 

2nd Thursday 

J  

 

2nd Friday 

 

2nd Saturday 

L  

root (/)

3rd Sunday 

n tapes  

/usr

3rd Sunday 

"  

/export

3rd Sunday 

"  

/export/home

3rd Sunday 

"  

 

3rd Monday 

 

3rd Tuesday 

N  

 

3rd Wednesday 

O  

 

3rd Thursday 

 

3rd Friday 

 

3rd Saturday 

root (/)

4th Sunday 

n tapes  

/usr

4th Sunday 

"  

/export

4th Sunday 

"  

/export/home

4th Sunday 

"  

 

4th Monday 

 

4th Tuesday 

 

4th Wednesday 

 

4th Thursday 

 

4th Friday 

 

4th Saturday 

With this plan, you use 4n tapes (the number of tapes needed for four full backups of root (/), /usr, /export, and /export/home), plus 24 additional tapes for the incremental backups of /export/home. This plan assumes that each incremental backup uses one tape and you save the tapes for a month.

Here's how this plan works:

  1. On each Sunday, do a full backup (level 0) of root (/), /usr, /export, and /export/home. Save the level 0 tapes for at least 3 months.

  2. On the first Monday of the month, use tape A to do a level 9 backup of /export/home. ufsdump copies all files changed since the previous lower-level backup (in this case, the level 0 backup that you did on Sunday).

  3. On the first Tuesday of the month, use tape B to do a level 9 backup of /export/home. Again, ufsdump copies all files changed since the last lower-level backup--Sunday's level 0 backup.

  4. On the first Wednesday, use tape C to do a level 5 backup. ufsdump copies all files changed since Sunday.

  5. Do the Thursday and Friday level 9 backups on tapes D and E. ufsdump copies all files changed since the last lower-level backup--Wednesday's level 5 backup.

  6. On the first Saturday of the month, do a level 5 backup of /export/home, which copies all files changed since the previous lower-level backup--in this case, the level 0 backup you did on Sunday. Store tapes A-F until the first Monday of the next 4-week period, when you use them again.

  7. Repeat steps 1-6 for the next three weeks, using tapes G-L and 4n tapes for the level 0 on Sunday, and so on.

  8. For each 4-week period, repeat steps 1-7, using a new set of tapes for the level 0s and reusing tapes A-X for the incremental backups. The level 0 tapes could be reused after 3 months.

    This plan lets you save files in their various states for a month. It requires many tapes, but ensures that you have a library of tapes to draw upon. To reduce the number of tapes, you could reuse Tapes A-F each week.