For PowerProtect Data Manager, what is a major consideration when setting up protection policies for SAP HANA?

Question

Options

• ADatabase indexing strategy
• BLog-based data replication
• CIn-memory data storage
• DMulti-tenant database container structure

• A
  7% (2)
• B
  3% (1)
• C
  73% (22)
• D
  17% (5)

Explanation

SAP HANA's defining architectural characteristic is in-memory data storage - data resides primarily in RAM rather than on traditional disk. This fundamentally changes how PowerProtect Data Manager must approach protection policies, requiring coordination with HANA's savepoint mechanism and log backups to capture a consistent, crash-recoverable state of in-memory data before it is flushed to persistent storage.

Why the distractors are wrong:

• A (Database indexing strategy) is a performance tuning concern for DBAs, not a factor that shapes how a backup tool structures protection policies.
• B (Log-based data replication) describes SAP HANA System Replication (HSR), which is a high-availability feature - separate from what PowerProtect Data Manager handles in backup policy configuration.
• D (Multi-tenant database container structure) does add backup complexity, but it is a secondary structural concern; the primary challenge that distinguishes HANA from conventional databases is its in-memory engine.

Memory tip: Anchor on HANA's tagline - it's an in-memory platform. Whenever a question pairs HANA with a backup or protection tool, your first instinct should be "how does protecting RAM-resident data differ from disk-resident data?" That reasoning leads you straight to C.

No community discussion yet for this question.