goldylamont
asked on
NTbackup--what to backup? restoration process? and best practices
hi, i need to know exactly what i should be backing up to ensure my client's safety. I still don't fully understand how a restore from NTbackup would go so i'd like to go over the list of things to back up and also the restoration process.
here's my thoughts so far, please correct me and add to this:
Stuff to Back up:
1) back up all business data (obviously)
2) back up system state (contains Active Directory & DNS?)
3) Ensure Exchange data and IIS web data are backed up (if they are installed)
4) should I back up anything else on C: (system) drive?? C:\program files??
When Restoring with backups made using NTbackup:
1) reinstall Server 2003 or SBS 2003
2) restore System State from NTbackup
3) restore Exchange & IIS
4) reinstall programs? (i.e. corporate anti-virus, etc.)
5) what about Group Policy? DHCP? NTbackup scripts/config?
Thanks! would love to hear from guys who have had to restore using NTbackup in real world scenarios but all comments welcome.
-k
here's my thoughts so far, please correct me and add to this:
Stuff to Back up:
1) back up all business data (obviously)
2) back up system state (contains Active Directory & DNS?)
3) Ensure Exchange data and IIS web data are backed up (if they are installed)
4) should I back up anything else on C: (system) drive?? C:\program files??
When Restoring with backups made using NTbackup:
1) reinstall Server 2003 or SBS 2003
2) restore System State from NTbackup
3) restore Exchange & IIS
4) reinstall programs? (i.e. corporate anti-virus, etc.)
5) what about Group Policy? DHCP? NTbackup scripts/config?
Thanks! would love to hear from guys who have had to restore using NTbackup in real world scenarios but all comments welcome.
-k
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
the links are great! thanks guys.
so, one last thing before closing out--can you please re-confirm/comment on my following thought:
"If I back up the System State and everything in the C:\Program Files directory, then in the event of a system restore, I won't need to reinstall any of the programs (i.e. Symantec Antivirus, etc.). After a 'successful' restore these programs will run as they did before without needing to be reinstalled/reconfigured."
Thanks guys
so, one last thing before closing out--can you please re-confirm/comment on my following thought:
"If I back up the System State and everything in the C:\Program Files directory, then in the event of a system restore, I won't need to reinstall any of the programs (i.e. Symantec Antivirus, etc.). After a 'successful' restore these programs will run as they did before without needing to be reinstalled/reconfigured."
Thanks guys
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
a great suggestion Steve. what i'm trying to determine is specifically--is it worth me backing up C:\Program Files directory so that i can restore programs in this directory INSTEAD of having to reinstall and reconfigure them after the restore. I totally understand that you can't give a concrete answer on this but I'm just wondering if this is even worth trying or should i expect to have to reinstall 3rd party apps from scratch even if I do have full backups of the Programs Files directory and the registry.
what i'm trying to avoid is backing up files that will be useless to me after the restore. And the Programs Files and C:\Windows directories are usually the bulk of data on my system drives. If it's useless for me to back these up b/c all that really matters is System State for this drive then i'd like to exclude them from my backup scripts. Do you back up these directories?
thanks
what i'm trying to avoid is backing up files that will be useless to me after the restore. And the Programs Files and C:\Windows directories are usually the bulk of data on my system drives. If it's useless for me to back these up b/c all that really matters is System State for this drive then i'd like to exclude them from my backup scripts. Do you back up these directories?
thanks
ASKER
can someone confirm whether they do or do not back up "C:\program files" so that when restoring they won't need to reinstall programs? i will then close out question. thanks to all who answered!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I know I'm late to the party but looks likes a popular thread. By the end of the thread I got the impression that doing a complete backup (files and system settings) would allow me to avoid reinstalling apps upon recovery. Prior to reading this thread I thought the opposite, that I would need to reinstall my OS, then my apps and then system state and data.
Does anyone want to discuss?
Does anyone want to discuss?
Backup Types
Aside from creating a full disk image or just copying a few files, several standard backup types can be run, as discussed in the following sections.
Full Backup
Full backups are the most comprehensive and are self-contained backups. However, the size of the data to be backed up and the time it takes to run a full backup to slow media may make it inappropriate as a regularly scheduled backup. Full backups may be restricted to a weekly or monthly schedule.
Most small businesses that fall within the SBS client base should have no problem doing a full nightly backup as created by the SBS Backup Wizard. If data size does become an issue (for example, multimedia or CAD files), archiving older files or excluding the files from the full backup and running a second data-only incremental or differential backup become options.
The trade-offs of a full backup are that although it provides the fastest restore, the storage space requirement is the highest, and backup and verify time is the longest.
With a full backup, only the previous full backup needs to be stored offsite.
It is also worth noting that each full backup contains an entire copy of the data. If the backup media were to be illegally accessed or stolen, the hacker or thief would then have access to an entire copy of your data.
The SBS 2003 Backup Wizard only creates a full, System State backup, but it does allow for the exclusion of some files and folders. SBS works around the problem of backing up open files by taking a snapshot copy of the drive contents using VSS. A copy of the open file is made by VSS, and the backup process accesses the VSS copy of the file instead of trying to access the open file directly.
Differential Backup
There is a significant distinction between differential backups and incremental backups although they are often confused. Differential backups back up all the files that have changed since the last full backup, whereas incremental backups back up all the files modified since the last full backup or incremental backup.
The trade-off is that although smaller and subsequently faster than a full backup, a differential backup is slower to restore.
Two backup files are required: the latest full backup and the latest differential backup. The last full backup and the last differential backup are the two backups that you need to store offsite.
Incremental Backup
Incremental backups provide a much faster method of backing up data than either full or incremental backups. An incremental backup backs up only those files that have changed since the most recent full, incremental, or differential backup.
The advantage of lower backup times comes at the price of an increased restore time and the need to safely store more media offsite. When restoring from incremental backup, you need the most recent full backup as well as every incremental backup you've made since the last full backup.
For example, if you did a full backup on Friday and incrementals on Monday, Tuesday, Wednesday, and Thursday, and the server crashes on the next Friday, you would need all five backup files: The Friday full backup and the Monday, Tuesday, Wednesday, and Thursday incrementals.
By comparison, if you had done differential backups on Monday, Tuesday, Wednesday, and Thursday, to restore on the Friday only the previous Friday's full backup plus Thursday's differential backup are required.
Note
Windows NTBackup uses the following backup type definitions:
Normal backup (full)A normal backup copies all the files you select and marks each file as having been backed up (in other words, the archive attribute is cleared). With normal backups, you only need the most recent copy of the backup file or tape to restore all the files. You usually perform a normal backup the first time you create a backup set.
Copy backupA copy backup copies all the files you select but does not mark each file as having been backed up (in other words, the archive attribute is not cleared). Copying is useful if you want to back up files between normal and incremental backups because copying does not affect these other backup operations.
Daily backupDaily backup copies all the files you select that have been modified on the day the daily backup is performed. The backed-up files are not marked as having been backed up (in other words, the archive attribute is not cleared). This backup type is generally not used as part of a recovery program because to do a full system restore, you would have to have a normal backup and then a daily backup from each and every day since the normal backup.
Kind Regards
Steve