| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.

View
 

CITRT Backup Practices

Page history last edited by OneSeventeen 11 years, 3 months ago

Introduction

Current backup solutions and goals.  Feel free to throw your CITRT username, real name, or church name in here along with non-sensitive backup details.

The goal of this page is to learn from each other's experiences, and possibly help point out where things could improve (especially when free or inexpensive solutions are available)!

 

Check out the Backup page for details on the various types of backups, ballpark pricing, and how to implement successful backup policies.

 

Fellow CITRT practices

 

OneSeventeen

Current:

SQL Server's built-in backup features with scripts to 7-zip them and robocopy them to a server in another room nightly.

Fileserver is prayed over while we are pursuing an offsite backup solution.

Exchange server and domain controller are backed up using Backup Exec.

VM's are not backed up.

Goals:

Expand SAN and virtualize all servers except the Domain Controller.

Use Veeam Backup or similar utility to backupall VM's with file-level restores.

Send all Veeam Backups to a SAN downtown over a T1 point-to-point during the evening and early morning hours.

Use Backup Exec (or something that works for us) to backup the physical servers to the same SAN downtown.

Continue SQL server backups, but backup to the SAN downtown instead.

Comments (0)

You don't have permission to comment on this page.