Username: Save?
Password:
Home Forum Links Search Login Register*
    News: Keep The TechnoWorldInc.com Community Clean: Read Guidelines Here.
Recent Updates
[May 13, 2025, 02:04:25 PM]

[May 13, 2025, 02:04:25 PM]

[May 13, 2025, 02:04:25 PM]

[May 13, 2025, 02:04:25 PM]

[April 12, 2025, 01:54:20 PM]

[April 12, 2025, 01:54:20 PM]

[April 12, 2025, 01:54:20 PM]

[April 12, 2025, 01:54:20 PM]

[March 12, 2025, 03:05:30 PM]

[March 12, 2025, 03:05:30 PM]

[March 12, 2025, 03:05:30 PM]

[March 12, 2025, 03:05:30 PM]

[January 03, 2025, 03:29:12 PM]
Subscriptions
Get Latest Tech Updates For Free!
Resources
   Travelikers
   Funistan
   PrettyGalz
   Techlap
   FreeThemes
   Videsta
   Glamistan
   BachatMela
   GlamGalz
   Techzug
   Vidsage
   Funzug
   WorldHostInc
   Funfani
   FilmyMama
   Uploaded.Tech
   Netens
   Funotic
   FreeJobsInc
   FilesPark
Participate in the fastest growing Technical Encyclopedia! This website is 100% Free. Please register or login using the login box above if you have already registered. You will need to be logged in to reply, make new topics and to access all the areas. Registration is free! Click Here To Register.
+ Techno World Inc - The Best Technical Encyclopedia Online! » Forum » THE TECHNO CLUB [ TECHNOWORLDINC.COM ] » Techno Articles » Internet
 Creating a Backup Plan
Pages: [1]   Go Down
  Print  
Author Topic: Creating a Backup Plan  (Read 647 times)
Shawn Tracer
TWI Hero
**********


Karma: 2
Offline Offline

Posts: 16072


View Profile
Creating a Backup Plan
« Posted: February 25, 2008, 11:57:19 AM »


Creating a Backup Plan
 by: Stephen Bucaro

Your company's data may be its most important asset. Imagine a large corporation with millions of dollars of account receivable and account payable data stored on their network. A fire causes massive data loss. How much work would be required to re-create the lost data? Without backups, the company may not survive the disaster.

Choosing a backup media is important, but in this article I'll focus on creating a plan for the type and frequency of backups. Let's assume you will use some type of tape backup media.

If your company has only a small amount of data, you may be able to perform a full backup every night. You would need two tapes which you would alternate in case the most recent full backup turns out defective. At least you have a previous one to go back to. You would store the tapes in a secure off-site location to avoid being destroyed in the same disaster that might destroy the original data.

When you perform a full backup, each file that gets baked up has the "archive" attribute in its file properties set to zero.

The archive attribute is a flag stored for each file that has been created or modified. It indicates that the file needs to be archived. Backup programs can reduce the size of backups by saving only files which have been modified since the previous backup. When the file is saved in a full or incremental backup, the archive bit is set to one.

In Windows, you can view the archive attribute for any file by right-clicking the file in Windows Explorer and selecting "Properties" in the popup menu. In the "Properties" dialog box, click on the "Advanced..." button.

If your company has a large amount of data, it would be too time consuming to perform a full backup every night. Instead, you would perform a full backup only on Friday nights, and perform a "differential" backup on other weekday night. This backup plan would require six tapes.

- A differential backup saves all files that have been created or modified since the last FULL backup.

- Restoring with differential backups is easy. You need just use two tapes. First restore the last full backup. Then restore the last differential backup.

A differential backup doesn't reset the archive attribute. The next time you perform a differential backup, it will again save all the files that have changed since the last full backup. So each night, the differential backup will get progressively larger until the next you perfrom a full backup.

If your company has a great amount of data that changes every day, it would be too time consuming to perform a differential backup every night. Instead, you might perform a full backup on Friday nights, and an "incremental" backup on other weekday night.

- An incremental backup saves only the files that have changed since the last full or incremental backup.

An incremental backup checks the archive attribute to determine if the file has changed and needs to be backed up. Then it resets the archive attribute. An incremental backup stays small because it includes only files that have changed since the last full or incremental backup.

- Restoring with incremental backups is more time consuming. First, restore the last full backup. Then restore all the incremental backups made since the full backup, in the order they were made. The only reason to use an incremental backup scheme is if differential backups become too large, requiring more than one tape.

Many company networks continue to opperate on Saturday and even Sunday. In this case, you would need to add the required additional tapes to the plan.

If during the day your company creates a large volume of data, or a small amount of data that is too critical to wait for the standard night time backup, you can perform a copy backup. To do this, you just copy the selected files to a backup media.

Copyright(C) 2004 Bucaro TecHelp.

Permission is granted for the below article to forward, reprint, distribute, use for ezine, newsletter, website, offer as free bonus or part of a product for sale as long as no changes are made and the byline, copyright, and the resource box below is included.

About The Author

Stephen Bucaro
To learn how to maintain your computer and use it more effectively to design a Web site and make money on the Web visit bucarotechelp.com. To subscribe to Bucaro TecHelp Newsletter visit http://bucarotechelp.com/search/000800.asp.

Logged

Pages: [1]   Go Up
  Print  
 
Jump to:  

Copyright © 2006-2023 TechnoWorldInc.com. All Rights Reserved. Privacy Policy | Disclaimer
Page created in 0.304 seconds with 25 queries.