Meta tags:
Headings (most frequently used words):
best, practices, for, sap, and, workload, manager, stay, organized, with, collections, save, categorize, content, based, on, your, preferences, severity, levels, workloads, products, pricing, support, resources, engage,
Text of the page (most frequently used words):
the (536), sap (418), for (389), hana (250), this (199), high (169), see (151), 2025 (143), and (136), that (132), from (128), rule (111), more (108), october (107), information (98), cloud (85), google (83), availability (82), parameter (74), cluster (74), medium (67), security (67), has (63), value (62), guide (62), resource (61), evaluation (60), change (60), also (60), severity (59), been (58), evaluations (58), configuration (58), updated (57), applies (55), 27th (54), existing (54), include (54), use (54), set (54), pacemaker (54), critical (52), system (47), recommended (43), best (42), you (41), practices (36), your (36), with (35), april (34), check (32), data (32), general (31), sles (30), password (30), can (29), linux (29), resources (28), are (28), rhel (27), compute (26), recommends (25), one (24), timeout (24), must (23), enable (22), insights (21), performance (21), log (20), backup (20), netweaver (20), overview (20), engine (19), all (18), appropriate (18), default (18), agent (18), instances (18), instance (17), replication (17), planning (17), have (16), not (16), corosync (16), projects (16), locations (16), workload (15), base (15), number (15), maintenance (15), access (15), policy (15), values (15), certified (15), recommendations (14), knowledge (14), parameters (14), workloads (14), based (14), user (14), type (14), backups (14), monitor (14), list (14), manager (13), ensure (13), users (13), options (13), creating (13), disk (13), failure (13), support (12), configuring (12), application (12), persistent (12), specifies (12), primary (12), create (12), saphana (12), get (12), their (11), how (11), setting (11), operating (11), encryption (11), recovery (11), settings (11), services (10), host (10), which (10), before (10), used (10), node (10), interval (10), fencing (10), 2026 (9), when (9), run (9), minimum (9), due (9), systems (9), server (9), database (9), least (9), cpu (9), operations (9), full (9), enqueue (9), operation (9), delete (9), following (8), red (8), hat (8), mode (8), running (8), memory (8), configured (8), volumes (8), reference (8), machine (8), custom (8), caution (8), platform (8), within (8), ers (8), version (8), migration (8), site (7), thumb (7), license (7), each (7), environment (7), time (7), suse (7), selinux (7), against (7), types (7), days (7), guides (7), automatic (7), same (7), secondary (7), properties (7), nodes (7), disaster (7), event (7), saphanatopology (7), should (7), saphanasr (7), failover (7), level (6), out (6), stability (6), start (6), recommend (6), vms (6), tools (6), checklists (6), privilege (6), will (6), file (6), such (6), different (6), migrate (6), delta (6), managed (6), central (6), ensa1 (6), topology (6), seconds (6), angi (6), threshold (6), receive (6), events (5), code (5), other (5), last (5), current (5), practice (5), table (5), these (5), might (5), scale (5), consistency (5), after (5), verify (5), help (5), while (5), large (5), swap (5), managing (5), unauthorized (5), maximum (5), failed (5), than (5), allow (5), risk (5), any (5), development (5), using (5), specific (5), storage (5), hosting (5), restart (5), ensa2 (5), contains (5), merges (5), defines (5), primitive (5), between (5), true (5), stonith (5), health (5), monitoring (5), ascs (5), alias (5), auto (5), token (5), down (4), impact (4), hosts (4), control (4), required (4), amount (4), created (4), size (4), note (4), service (4), june (4), but (4), space (4), recommendation (4), role (4), safeguard (4), privileges (4), production (4), encrypt (4), supports (4), provide (4), volume (4), higher (4), they (4), passwords (4), improve (4), minimal_password_length (4), lower (4), initial (4), only (4), section (4), location (4), key (4), uefi (4), enabled (4), across (4), march (4), optimal (4), separate (4), disks (4), able (4), option (4), prevent (4), reduce (4), recover (4), automatically (4), because (4), profile (4), deletion (4), scope (4), clusters (4), 700 (4), stickiness (4), address (4), ilb (4), gcpstonith (4), deprecated (4), limit (4), during (4), ssd (4), compression (4), management (4), deployments (4), join (3), manage (3), samples (3), status (3), need (3), content (3), its (3), policies (3), console (3), non (3), scaleout (3), tables (3), tables_preloaded_in_parallel (3), regular (3), possible (3), stack (3), tuning (3), changing (3), permissive (3), compatibility (3), available (3), layer (3), network (3), configurations (3), global (3), cve (3), 2019 (3), 0357 (3), password_lock_time (3), character (3), times (3), helps (3), expires (3), maximum_unused_productive_password_lifetime (3), maximum_unused_initial_password_lifetime (3), maximum_password_lifetime (3), soon (3), maximum_invalid_connect_attempts (3), logs (3), last_used_passwords (3), sap_internal_hana_support (3), both (3), optimized (3), servers (3), provider (3), hook (3), provided (3), hyperdisk (3), load_table_numa_aware (3), region (3), zonal (3), stopping (3), fast (3), includes (3), functionality (3), would (3), virtual (3), unplanned (3), outage (3), infrastructure (3), distributed (3), scs (3), replicator (3), behavior (3), documentation (3), protection (3), apis (3), triggered (3), specified (3), stop (3), 600 (3), attributes (3), defaults (3), results (3), upgrade (3), long (3), promotable (3), manages (3), trigger (3), another (3), preference (3), constraints (3), definition (3), fence_gce (3), fence (3), supported (3), low (3), case (3), then (3), conform (3), numa (3), garbage (3), collection (3), databases (3), datashipping_parallel_channels (3), shipping (3), catalog (3), needed (3), usage (3), logger (3), reclaim (3), map (3), correctly (3), evaluating (3), resolve (3), product (3), rest (3), executions (3), 한국어 (2), 日本語 (2), português (2), brasil (2), français (2), español (2), américa (2), latina (2), deutsch (2), english (2), sign (2), third (2), terms (2), about (2), youtube (2), architecture (2), started (2), release (2), notes (2), pricing (2), products (2), understand (2), incorrect (2), utc (2), otherwise (2), licensed (2), under (2), details (2), java (2), send (2), feedback (2), state (2), doesn (2), selected (2), marks (2), icon (2), levels (2), maintaining (2), crucial (2), maintain (2), consistent (2), parallel (2), checks (2), corruptions (2), indexserver (2), crash (2), thread (2), determines (2), saptune (2), tuned (2), enabling (2), enterprise (2), components (2), implementations (2), requires (2), without (2), ensures (2), disabled (2), well (2), part (2), follows (2), debug (2), vulnerability (2), administrator (2), versions (2), protect (2), way (2), persistence (2), additional (2), locked (2), logon (2), attempts (2), contain (2), password_layout (2), expire (2), important (2), expiration (2), password_expire_warning_time (2), enforce (2), preventing (2), minimum_password_lifetime (2), characters (2), could (2), reducing (2), temporary (2), valid (2), protects (2), reuse (2), allowed (2), account (2), force_first_password_change (2), means (2), even (2), guest (2), image (2), newer (2), generation (2), mandatory (2), remove (2), specify (2), migrations (2), series (2), reasons (2), hooks (2), individual (2), vendor (2), filesystem (2), serving (2), installation (2), path (2), save (2), zones (2), does (2), metal (2), errors (2), cause (2), outages (2), sites (2), deployed (2), regions (2), single (2), potential (2), loss (2), what (2), zone (2), regularly (2), strategy (2), situations (2), snapshot (2), daily (2), may (2), necessary (2), meet (2), requirements (2), titled (2), deployment (2), issues (2), guard (2), certain (2), scenarios (2), processes (2), new (2), where (2), still (2), pfl (2), accidental (2), iam (2), failures (2), row (2), store (2), reorganization (2), often (2), automatic_reorg_threshold (2), parallel_merge_threads (2), starting (2), complete (2), considered (2), 300 (2), meta (2), clone (2), determine (2), configure (2), integrity (2), essential (2), strongly (2), later (2), remain (2), enough (2), 1000 (2), correct (2), moved (2), vip (2), internal (2), traffic (2), 3600 (2), occurs (2), 5000 (2), reliability (2), included (2), view (2), name (2), sapinstance (2), sets (2), allowing (2), meta_attributes (2), move (2), kernel (2), multiple (2), executed (2), utilization (2), merge (2), worst (2), although (2), modes (2), logshipping_max_retention_size (2), logshipping_async_buffer_size (2), administration (2), log_mode (2), avoid (2), pcmk_delay_max (2), transport (2), token_retransmits_before_loss_const (2), max_messages (2), make (2), consensus (2), permanent (2), second (2), throughput (2), channels (2), especially (2), over (2), log_disk_usage_reclaim_threshold (2), free (2), segments (2), diskfull (2), logfull (2), charge (2), sdk (2), languages (2), frameworks (2), costs (2), observability (2), networking (2), industry (2), solutions (2), hybrid (2), multicloud (2), analytics (2), pipelines (2), cancel (2), actuations (2), discoveredprofiles (2), cross (2), technology (2), areas (2), close (2), subscribe, newsletter, our, decade, climate, action, cookies, privacy, tech, twitter, blog, engage, training, certification, center, getting, github, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, noted, page, registered, trademark, oracle, affiliates, developers, apache, creative, commons, attribution, evaluates, comparing, comply, assigns, indicates, far, compliance, compliant, explains, icons, corresponding, modifying, adhere, dst, switch, timezones, timezone, loads, unloads, lets, loaded, providing, flexibility, optimization, detect, hidden, early, overflow, evaluator, expressionparser, newly, worker_stack_size_kb, default_stack_size_kb, worker, profiles, optimize, sapconf, solution, startup, fails, enhanced, interfere, disabling, reboot, rebooting, aware, enhances, efficiently, physical, listen, interface, allowed_sender, restrict, senders, attach, debugger, allows, commands, root, particular, affected, minutes, 1440, receives, notification, notify, warning, elapse, aging, frequently, enhancing, shorter, likely, guessed, cracked, increase, logged, compromised, accounts, prolonged, inactivity, 365, meant, serve, purpose, measures, periodically, 182, reached, common, prevents, reusing, most, recent, past, whether, require, statement, encrypting, transferred, gains, cannot, read, decryption, applicable, party, features, family, boot, feature, selecting, pre, compatible, prerequisite, uefi_compatible, images, platforms, migrating, advised, want, target, advanced, instruction, promptly, reporting, becomes, sync, notably, function, filesystems, snapshots, num_submit_queues, num_completion_queues, resiliency, exist, multi, setup, restarting, apply, onhostmaintenance, intel, ras, significantly, crashes, combined, capability, since, sp04, families, wide, business, continuity, geographical, approach, mitigates, catastrophic, affecting, downtime, beyond, redundancy, offer, bare, implementing, proper, corruption, weekly, substitute, frequent, rpo, restarts, mitigate, don, migrated, portal, mismatch, protected, deletionprotection, api, uses, permissions, alert, fragmentation, won, parallelism, consumed, tokens, token_per_table, finish, cloned, interleave, clone_node_max, preserve, activate, timely, completion, isolating, them, disrupting, property, articles, term, package, sp6, replaces, packages, replicated, pair, takeover, upon, prefer_site_takeover, duplicate_primary_timeout, 7200, automated_register, classified, msl, prefers, minimize, unnecessary, disable, performing, those, deactivate, manual, constraint, occur, manually, update, local, load, balancer, work, together, monitors, listening, port, routing, ineligible, module, bundled, distributions, extension, add, legacy, clients, installed, ensa, align, continued, experiences, replicatorhost, serverhost, guaranteeing, enhance, attribute, additionally, automatic_recover, false, indicating, three, rsc_defaults, knowledgebase, abap, identify, active, optional, is_ers, influence, behaves, bootstrap, take, being, override, op_defaults, troubleshooting, stopped, unforeseen, healthy, addresses, discouraged, mechanism, consequently, making, impossible, implementation, partitions, exceeded, result, increased, backlog, sufficient, handling, consider, increasing, usual, introduce, bottlenecks, num_merge_threads, max_cpuload_for_parallel_merge, context, logreplay, redo, kept, synchronization, underlying, isn, hold, retention, happen, runs, comes, standstill, disconnected, shipment, scratch, order, buffer, adjusted, normal, creates, point, restoring, moment, overwrite, demote, promote, special, race, conditions, greater, device, protocol, expected, udpu, knet, detection, 20000, message, flooding, processing, modify, sure, keys, operate, generated, uniform, optimizes, placement, loading, block, 400, per, balanced, extreme, provision, 000, iops, allowable, sizes, 235, allocation, hiccups, memoryreclaim, waits, happens, reactively, gc_unused_memory_threshold_abs, gc_unused_memory_threshold_rel, datashipping, four, ship, subsequential, continuous, distances, example, async, issue, caused, grow, quite, cleaned, lead, problems, difficult, find, housekeeping, partition, useddiskspace, percent, totaldiskspace, above, keep, cached, removed, explicitly, via, alter, hit, internally, situation, machines, february, mapped, incomplete, inaccurate, post, tasks, command, line, utility, matches, replaced, install, description, category, select, categories, filter, shows, there, resolution, reviewing, useful, informational, earliest, convenience, suboptimal, supportability, next, planned, window, degraded, unsupported, impacts, document, lists, learn, categorize, preferences, stay, organized, collections, home, audit, logging, quotas, limits, listoperationsresponse, listoperationsrequest, listlocationsresponse, listlocationsrequest, getoperationrequest, getlocationrequest, deleteoperationrequest, canceloperationrequest, shared, v1alpha, cloudresource, rules, writeinsight, scannedresources, patch, openshift, sql, redis, mysql, authenticate, skip, main,
Text of the page (random words):
ies to existing evaluations that include this rule for more information see the guide for your os for rhel see creating cloned saphanatopology resource for sles see creating saphanatopology high october 27 2025 sap high availability pacemaker use the recommended values for the sap hana topology monitor setting a linux pacemaker ha cluster contains a saphanatopology resource that includes a monitor operation which has an interval value and a timeout value for linux pacemaker ha clusters for sap on google cloud we recommend a value between 10 and 60 seconds for the interval and a value of 600 seconds for the timeout for more information see the guide for your os for rhel see create the saphanatopology resource for sles see create the saphanatopology primitive resource critical april 16 2025 sap high availability pacemaker use the recommended timeout values for the sap hana topology start stop operation the timeout parameter defines the maximum amount of time allowed for an operation such as starting or stopping a resource to complete if the operation does not finish within this specified time it is considered to have failed the recommended settings for a sap hana topology resource is a start timeout value of 600 and a stop timeout value of 300 from october 27th 2025 the severity of this evaluation rule has been updated from medium to high this change also applies to existing evaluations that include this rule for more information see the guide for your os for rhel see create the saphanatopology resource for sles see saphanatopology high october 27 2025 sap hana insights sap hana performance check for appropriate configuration of the parallel_merge_threads parameter if parallel_merge_threads is set to a specific value this value is used for parallelism while token_per_table defines the number of consumed tokens from october 27th 2025 the severity of this evaluation rule has been updated from medium to high this change also applies to existing evaluations that include this rule for more information see sap hana delta merges in the sap knowledge base high october 27 2025 sap hana insights sap hana maintenance check for appropriate configuration of the automatic_reorg_threshold parameter the automatic_reorg_threshold parameter specifies when automatic reorganization of row store tables is triggered if the value is set to 30 default automatic reorganization won t be triggered as often as it could be for more information see incorrect sap hana alert 71 row store fragmentation in the sap knowledge base medium april 21 2025 sap general sap general ensure that sap application servers and sap central services are in different zones to guard against zonal failures google cloud recommends that at least one instance hosting an sap application server is running in a different zone than the sap central services from october 27th 2025 the severity of this evaluation rule has been updated from medium to high this change also applies to existing evaluations that include this rule for more information see the sap hana disaster recovery planning guide high october 27 2025 sap general sap general allow full access to all cloud apis google cloud recommends that for compute engine instances the cloud api access scope is set to allow full access to all cloud apis and uses the iam permissions of the instance service account to control access to google cloud resources from october 27th 2025 the severity of this evaluation rule has been updated from caution to medium this change also applies to existing evaluations that include this rule for more information see the section titled enable access to google cloud apis in the agent for sap installation guide medium october 27 2025 sap general sap general enable deletion protection on all vms that run sap workloads compute instances that have the deletionprotection option enabled are protected against accidental deletion google cloud recommends enabling deletion protection for all instances that are critical to running sap workloads from october 27th 2025 the severity of this evaluation rule has been updated from medium to high this change also applies to existing evaluations that include this rule for more information see prevent accidental vm deletion in the compute engine documentation high october 27 2025 sap high availability high availability use ensa2 parameters for enqueue replicator in systems where the sap netweaver version supports ensa2 but the default pfl file still contains ensa1 parameters this mismatch might cause issues with enqueue server functionality and cluster behavior from october 27th 2025 the severity of this evaluation rule has been updated from medium to high this change also applies to existing evaluations that include this rule for more information see profile parameters of enqueue replicator 2 in the sap help portal high october 27 2025 sap general sap general sap application server processes must not be running on compute engine instances serving as the a scs or ers to mitigate potential performance issues and guard against certain failure scenarios in a pacemaker managed high availability cluster google cloud recommends that you don t run the sap application server processes on the same compute instances that host the sap central services or enqueue replication server ers this is because application servers are not managed by the pacemaker cluster and are not migrated to a new vm in the event of an outage from october 27th 2025 the severity of this evaluation rule has been updated from caution to high this change also applies to existing evaluations that include this rule for more information see the section titled distributed deployment with high availability in the reference architecture for sap on google cloud high october 27 2025 sap general sap general enable automatic restart for sap workloads to ensure that the vm restarts automatically in the event of a failure enable the compute engine automatic restart policy for any vm that is running an sap workload for more information see set vm host maintenance policy critical april 18 2025 sap hana sap hana check for backups of the sap hana database creating backups regularly and implementing a proper backup strategy helps you recover your sap hana database in situations such as data corruption or data loss due to an unplanned outage or failure in your infrastructure google cloud recommends following a backup strategy that includes creating at least one full system backup of your sap hana database weekly and creating at least one delta backup or snapshot based backup of the sap hana data volume daily daily full system backups can also be used as a substitute for delta or snapshot based backups more frequent backups may be necessary to meet specific rpo requirements for more information see backup and recovery in the sap hana operations guide or backup and recovery for sap hana on bare metal instances critical april 18 2025 sap hana sap hana ensure that the sap primary and dr sites are in different regions to protect against region wide outages and maintain business continuity the sap hana primary node and disaster recovery dr sites must be deployed in different geographical regions this approach mitigates the risk of catastrophic events affecting the components deployed within a single region reducing potential data loss and downtime beyond what zone level redundancy can offer from october 27th 2025 the severity of this evaluation rule has been updated from critical to high this change also applies to existing evaluations that include this rule for more information see the sap hana disaster recovery planning guide high sap hana sap hana enable sap hana fast restart compute engine includes functionality based on intel s memory ras that can significantly reduce the impact of all memory errors that would otherwise cause vm crashes when combined with sap hana s fast restart capability available since hana 2 0 sp04 sap hana systems are able to recover from such failure events this configuration is recommended on all memory optimized virtual machine families from october 27th 2025 the severity of this evaluation rule has been updated from critical to high this change also applies to existing evaluations that include this rule for more information see sap hana fast restart option high october 27 2025 sap general sap general set vm maintenance policy to migrate for sap workloads to prevent any platform maintenance events from stopping or restarting a vm that is running sap workloads the onhostmaintenance parameter for the vm must be set to the recommended option migrate this recommendation does not apply to x4 or c3 metal instances for more information see set vm host maintenance policy critical april 18 2025 sap high availability high availability ensure multi zonal setup for sap hana to ensure resiliency of an sap hana high availability configuration the primary and secondary nodes must exist in different zones in the same region from october 27th 2025 the severity of this evaluation rule has been updated from medium to high this change also applies to existing evaluations that include this rule for more information see the sap hana planning guide high october 27 2025 sap hana sap hana use the recommended configuration settings for hyperdisk to enable the best performance of the hyperdisk volumes used with sap hana you must set values recommended by google cloud for the following sap hana properties num_completion_queues num_submit_queues tables_preloaded_in_parallel and load_table_numa_aware for more information see hyperdisk performance in the sap hana planning guide critical april 18 2025 sap hana sap hana use a separate disk for each sap hana filesystem for optimal performance of your sap hana system google cloud recommends that you use a separate disk for each sap hana filesystem notably the disks hosting the sap hana data and log volumes must not be used for any other function such as serving as the installation path or system instance path this recommendation also applies to the sap hana backup volume if you save your backups to a disk hosting filesystems on separate disks is also recommended to be able to use data snapshots as a backup and recovery option from october 27th 2025 the severity of this evaluation rule has been updated from medium to high this change also applies to existing evaluations that include this rule for more information see the persistent disk storage section in the sap hana planning guide high october 27 2025 sap high availability high availability set the system replication hook for sap hana in an sap hana high availability configuration the ha dr hooks monitor replication and individual services such as the indexserver provided by the operating system vendor these configurations impact sap hana from promptly reporting to the cluster if the secondary instance becomes out of sync or sap hana services crash for more information see the guide for your os for rhel see enable the sap hana ha dr provider hook for sles see enable the sap hana ha dr provider hook critical march 17 2026 sap general sap general for compute engine instance migrations across machine series set the cpu platform to automatic for compute engine instance migrations across machine series google cloud recommends setting the cpu platform to automatic before migrating setting a specific cpu platform is only advised if you want to use the same type for the target machine due to performance or advanced instruction set compatibility reasons from october 27th 2025 the severity of this evaluation rule has been updated from caution to medium this change also applies to existing evaluations that include this rule for more information see the compute engine guides for cpu platforms how to specify a minimum cpu platform for vm instances and how to remove a minimum cpu platform setting medium october 27 2025 sap general sap general uefi enabled os images are mandatory for newer generation servers enable uefi boot for the vm by creating a custom image with the uefi_compatible guest os feature or selecting a pre configured uefi compatible image uefi compatibility is a prerequisite for newer generation machine types in google cloud from october 27th 2025 the severity of this evaluation rule has been updated from caution to high this change also applies to existing evaluations that include this rule for more information see the compute engine guides for operating system details memory optimized machine family for compute engine and enable guest operating system features high october 27 2025 sap hana security best practices sap hana security enable encryption for data and log backups encryption protects backups from unauthorized access by encrypting the backup data before it is transferred to the backup location this means that even if an unauthorized user gains access to the backup data they cannot read it without the decryption key this is applicable for both file based backups and backups created using third party backup tools google cloud recommends that you enable backup encryption in the sap hana system from october 27th 2025 the severity of this evaluation rule has been updated from medium to high this change also applies to existing evaluations that include this rule for more information see system backup encryption statement in the sap hana reference guide high october 27 2025 sap hana security best practices sap hana security safeguard against users with development privileges in a production environment at least one user or role has the development privilege in the production database google cloud recommends that you have no users with this privilege from october 27th 2025 the severity of this evaluation rule has been updated from medium to high this change also applies to existing evaluations that include this rule for more information see development privilege section in sap hana security checklists and recommendations high october 27 2025 sap hana security best practices sap hana security require users to change their initial password the force_first_password_change parameter in sap hana specifies whether users are required to change their password after they are created google cloud recommends that you enable the force_first_password_change parameter for more information see password policy configuration options in the sap hana one security guide medium april 23 2025 sap hana security best practices sap hana security safeguard against users with sap_internal_hana_support privileges in production environment at least one account has the sap_internal_hana_support role google cloud recommends that you have no users with this privilege from october 27th 2025 the severity of this evaluation rule has been updated from medium to high this change also applies to existing evaluations that include this rule for more information see sap_internal_hana_support role in sap hana security checklists and recommendations high october 27 2025 ...
|
