You first need a sound Backup Policy. Just throwing hw and sw at a
problem isn't a good solution unless it meets those policy
objectives.
I've seen this mentioned many times on the list. As a small K-8
school (150 total students), we do not have an official policy, as I
pretty much decide how things are going to be.
That's part of the problem this addresses.
And even if you are the sole person involved, you still need to
define the polcy you plan to implement.
I'm interested in any other EDU institutions sharing their policies
with the list.
We suggest the following survey / template for clients as a starting
point for drafting a backup policy. For more see "Unix Backup and
recovery" by O'Reilly.
Backup Policy
- Business Continuity Concerns
Address concerns for continuing business operations and
protection needs.
- High Availablity Data
Requirements and and implementations for keeping data available
to users through technologies like RAID, redundancy, replication
and failover.
- Archival Requirements
What archival states does source data follow? What compliance
requriements exist? Is some data maintainable as "volumes". What
data can be made less available (pushed further offline)?
- What Needs Backed Up
Identify the important data in each of the following categories.
- system files
- applications
- data
- logs
- user files
- assets
- Source File Locations
- hosts
- filesystems
- accessibility
- sizes
- atomicy of data
sometimes large files have small changes, for instance
databases
- Backup Operators
Identify roles of users, maangement, and operations
- who will back up what files?
- files from what locations get backed up by whom?
- what parties are involved in backup operations
- on-site
- off-site
- near-line
- online
- role of users
- Backup Conditions
- where
- hosts
- devices
- locations
- when
- backup window
- standalone times
- system state changes
- why
- files modified
- checkpoint snapshots
- versioning
- system state images
- before/after system state changes
- base os
- compliance
- Source Volatility
- frequency of changes
- importance of changes
- need for rollback
- identifying and targeting ephemeral files
- Recovery Requirements
- recovery expectations
- recovery time periods
- media retrieval
- Retention
- archival requirements
- compliance requirements
- rotation periods
- Media Storage
- media formats
- capacities required
- end-of-life
- compression
- locations
- online
- near-line
- off-line
- off-site
- retrieval times
- security
- physical media security
- data security
- environmental security
- cataloging
--
-dhan
------------------------------------------------------------------------
Dan Shoop AIM: iWiring
Systems & Networks Architect http://www.iwiring.net/
email@hidden http://www.ustsvs.com/
iWiring provides systems and networks support for Mac OS X, unix, and
Open Source application technologies at affordable rates.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
