SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

3 Planning Database Security and Recovery
Database security and recovery are essential topics to consider before creating an SQL/MX
database. Planning for security is the primary protection against unauthorized user intervention.
Security, however, cannot eliminate errors by authorized users. Planning for recovery is essential
for protecting your database. Your recovery plan should include protection against disk failures,
software failures, application errors, other equipment failures, catastrophic disasters, and human
errors of all types.
This section addresses these topics:
• “Planning Database Security” (page 42)
• “Planning Database Recovery” (page 45)
• “Using TMF for Transaction Recovery, Database Consistency, and Database Recovery”
(page 48)
• “Using RDF to Set Up a Backup System” (page 56)
• “Using Backup and Restore 2 for SQL/MX Database Recovery” (page 61)
This section applies specifically to SQL/MX databases. For more information about planning
security and recovery for an SQL/MP database, see the SQL/MP Installation and Management
Guide.
For more information about performing recovery operations on an SQL/MX database, see
“Performing Recovery Operations” (page 235).
Planning Database Security
Planning for database security is the primary protection against unauthorized user intervention.
When planning your SQL/MX database security, consider:
• What are the requirements for security on the system or network?
• How many different users access the same database?
• How should schemas be defined so that the correct people have the authorization to change
and remove objects from the metadata?
• What are the needs or restrictions of all users of your system, or a network of systems?
For related information, see:
• “Authorization Requirements for Adding Database Objects” (page 151)
• “Authorization Requirements for Altering Database Objects” (page 163)
• “Authorization Requirements for Dropping Database Objects” (page 169)
• “Managing Permissions for Files in OSS Space” (page 221)
• “Managing Permissions for Files in Guardian Space” (page 221)
• “Securing User Modules” (page 223)
• “Managing Network Security” (page 274)
Planning Guidelines
When you plan your SQL/MX database security you should consider:
• “Database Access and Security” (page 43)
• “OSS File and Directory Security” (page 43)
• “Safeguard Security” (page 44)
42 Planning Database Security and Recovery