Backup Farm

I have just finally completed the remainder of my backup tasks.

We are backing up:

IIS Metabase - (running on windows scheduler daily)
Backup IIS once before production and every time there is an IIS change or new WEB App created on ALL WFE’s

Syntax
iisback[.vbs] /backup [/b BackupName] [/v {Integer NEXT_VERSION HIGHEST_VERSION}] [/overwrite] [/e EncryptingPassword] [/s Computer [/u [Domain\]User [/p Password]]]
batch file to run is located at C:\WINDOWS\system32\inetsrv\MetaBack\BACKUP_IIS_METABASE.bat
Creates 2 files in:
C:\WINDOWS\system32\inetsrv\MetaBack\WeeklyBackup.MD0 (0 increments for each save)
C:\WINDOWS\system32\inetsrv\MetaBack\WeeklyBackup.SC0 (0 increments for each save)


IIS Configuration – (running on windows scheduler weekly)
Go to IIS, Right Click Local Computer – Choose All tasks – Backup/Restore Configuration – Create Backup
C:\WINDOWS\system32\inetsrv\MetaBack\IIS Configuration Backup 083107.MD0
NOTE: This backup method provides a way to restore only your IIS settings, not your content files. This backup method does not work if you reinstall your operating system. Backup files cannot be used to restore an IIS configuration on other computers that are running Windows 2000

MOSS – Index Server (full farm)
Full Farm Backup – GUI - Central Admin – Operations – Perform a backup. Backup location S:\FullFarmBackup (needs to have farm service account and sql service account sharing rights)

Batch file created to run on Window Scheduler every Saturday at 9:00PM. - S:\FullFarmBackup (FullFarmDiff) This is a full farm backup using the differential flag. This will only backup changes. You must first have a full farm backup before using the differential flag

Site Collection – Each Site Collection has been backed up to d:\moss_backup. The batch file is located in d:\moss_backup and has been added to the job scheduler to run every Saturday evening at 8:35pm. This works great but once your site collections get really big they will take a long time. Also if you are running this on a server that users are accessing it can hurt performance. We have this running on our Index server which users are not accessing.

I will add also that currently the SSP is very important. This is being backed up by the Central Administration site. I am working on creating a script to have this backed up by the windows scheduler also.

Database backups are done nightly