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):
rectly on all instances in the evaluation scope instances in the evaluation scope must have the agent for sap configured for workload manager evaluation if the agent has not been set up correctly then evaluation results might be incomplete or inaccurate this check is included by default at no charge for more information see google cloud s agent for sap planning guide and then verify the agent version critical march 18 2026 sap hana sap hana use a certified os to receive support from sap and google cloud for sap hana on a compute engine vm you must use an operating system version that is certified by sap and google cloud for use with sap hana for more information see os support for sap hana on google cloud critical june 1 2026 sap hana sap hana use a certified custom vm type to receive support from sap and google cloud for sap hana on a compute engine custom vm you must use a custom vm type that is certified by sap and google cloud for use with sap hana for more information see certified custom machine types for sap hana critical april 9 2025 sap hana sap hana map the sap hana data and log volumes to the same type of ssd based persistent disk for performance reasons the sap hana hana data and hana log volumes must be mapped to the same type of ssd based persistent disk you can map both volumes to the same single persistent disk or if the same persistent disk type is used for each you can map each volume to a separate persistent disk for more information see the sap hana planning guide critical april 9 2025 sap hana sap hana use a certified vm type to receive support from sap and google cloud for sap hana on a compute engine vm you must use a vm type that is certified by sap and google cloud for use with sap hana for more information see certified compute engine vms for sap hana critical february 18 2026 sap netweaver sap netweaver use a certified custom vm type to receive support from sap and google cloud for sap netweaver on a compute engine custom vm you must use a custom vm type that is certified by sap and google cloud for use with sap netweaver for more information see certified machines in the sap netweaver planning guide critical april 9 2025 sap netweaver sap netweaver use a certified os to receive support from sap and google cloud for sap netweaver on a compute engine vm you must use an operating system version that is certified by sap and google cloud for use with sap netweaver for more information see os support for sap netweaver on google cloud critical june 1 2026 sap netweaver sap netweaver use a certified vm type to receive support from sap and google cloud for sap netweaver on a compute engine vm you must use a vm type and cpu platform that is certified by sap and google cloud for use with sap netweaver for more information see machine types in the sap netweaver planning guide critical march 3 2026 sap hana insights sap hana maintenance check for appropriate configuration of the log_disk_usage_reclaim_threshold parameter if the log partition file system disk usage useddiskspace in percent of totaldiskspace is above the specified threshold the logger will automatically trigger an internal log release 0 disabled as default the logger will keep all free log segments cached for reuse segments will only be removed if a reclaim is triggered explicitly via alter system reclaim log or if a diskfull logfull event is hit on logger level this threshold parameter can be used to trigger the reclaim internally before a diskfull logfull situation occurs 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 log_disk_usage_reclaim_threshold in the sap hana configuration parameter reference high october 27 2025 sap hana insights sap hana maintenance regular backup catalog housekeeping is needed to improve backup performance the backup catalog can grow quite large over time especially if it is not regularly cleaned up this can lead to performance problems and can make it difficult to find the backups that are needed 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 multiple issue caused by large log backups due to large backup catalog size in the sap knowledge base high october 27 2025 sap hana insights sap hana high availability and disaster recovery enable data and log compression data and log compression can be used for the initial full data shipping the subsequential delta data shipping as well as for the continuous log shipping data and log compression can be configured to reduce the amount of traffic between systems especially over long distances for example when using the async replication mode 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 data and log compression in the sap hana system replication guide high october 27 2025 sap hana insights sap hana high availability and disaster recovery use the recommended value for the datashipping_parallel_channels parameter the sap hana parameter datashipping_parallel_channels defines the number of network channels used by full or delta datashipping the default value is 4 which means that four network channels are used to ship data 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 datashipping_parallel_channels in the sap hana administration guide high october 27 2025 sap hana insights sap hana performance check for appropriate configuration of garbage collection parameters in databases with more than 235 gb allocation limit the gc_unused_memory_threshold_rel and gc_unused_memory_threshold_abs parameters have to be configured these parameters help to reduce the risk of hiccups e g due to memoryreclaim waits when garbage collection happens reactively 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 garbage collection in the sap knowledge base high october 27 2025 sap hana sap hana sap minimum allowable sizes for ssd based persistent disk options for block storage sap hana requires a minimum throughput of 400 mb per second if you are using ssd or balanced persistent disks use the minimum size for that persistent disk type to provide the necessary throughput if you are using extreme persistent disks provision a minimum of 20 000 iops for more information see persistent disk storage in the sap hana planning guide critical april 18 2025 sap hana insights sap hana performance enable the load_table_numa_aware parameter to improve the performance of numa based sap hana systems enable the load_table_numa_aware parameter when this parameter is enabled sap hana optimizes data placement across numa nodes during table loading 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 non uniform memory access numa in the sap knowledge base high october 27 2025 sap hana insights sap hana maintenance check the status of the hana license a permanent license key is required to operate on a hana system if a permanent license key expires a second temporary license key is automatically generated and will be valid for 28 days 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 license keys for sap hana database in the sap knowledge base high october 27 2025 sap high availability corosync use the recommended value for the consensus parameter in a linux pacemaker high availability cluster for sap on google cloud the default value of the consensus parameter is set to 1 2 times the value of the token parameter it is recommended not to modify this value if you change the default value make sure that it is at least 1 2 times the token value 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 corosync configuration parameter values in the sap hana high availability planning guide high october 27 2025 sap high availability corosync use the recommended value for the join parameter in a linux pacemaker high availability cluster for sap on google cloud set the corosync join parameter to a value of 60 to conform to google cloud best practices 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 corosync configuration parameter values in the sap hana high availability planning guide high october 27 2025 sap high availability corosync use the recommended value for the max_messages parameter in a linux pacemaker high availability cluster for sap on google cloud to avoid message flooding between cluster nodes during token processing set the corosync max_messages parameter to a value of 20 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 corosync configuration parameter values in the sap hana high availability planning guide medium october 27 2025 sap high availability corosync use the recommended value for the token_retransmits_before_loss_const parameter in a linux pacemaker high availability cluster for sap on google cloud set the corosync token_retransmits_before_loss_const parameter to a value of 10 or more to conform to google cloud best practices for more information see corosync configuration parameter values in the sap hana high availability planning guide critical april 14 2025 sap high availability corosync use the recommended value for the token parameter in a linux pacemaker high availability cluster for sap on google cloud set the value of the corosync token parameter to the recommended timeout value of 20000 to conform to the google cloud best practice for failure detection for more information see corosync configuration parameter values in the sap hana high availability planning guide critical april 14 2025 sap high availability corosync use the recommended value for the transport parameter in a linux pacemaker high availability cluster for sap on google cloud set the value of the corosync transport protocol as appropriate for your operating system for red hat systems of version 8 and later the parameter should be set to knet for other supported operating systems a value of udpu is expected for more information see the guide for your os for rhel see ha cluster configuration guide for sap hana on rhel for sles see ha cluster configuration guide for sap hana on sles critical april 14 2025 sap high availability pacemaker set pcmk_delay_max on the fencing device cluster resource to avoid fence race conditions in linux pacemaker high availability clusters for sap the pcmk_delay_max parameter must be specified with a value of 30 or greater in the definition of the fencing resource for more information see special options for fencing resources critical april 14 2025 sap high availability pacemaker use the recommended timeout value for saphana operations the definition of the saphana resource in a linux pacemaker ha cluster contains a timeout value for the stop start promote and demote operations for linux pacemaker ha clusters for sap on google cloud we recommend a value of at least 3600 for each operation for more information see the guide for your os for rhel see ha cluster configuration guide for sap hana on rhel for sles see ha cluster configuration guide for sap hana on sles critical april 14 2025 sap hana insights sap hana maintenance check the log mode if log_mode is set to normal hana creates regular log backups allowing for point in time recovery restoring up to the moment before a failure if log_mode is set to overwrite no log backups are created you can only recover the database to the last data backup from october 27th 2025 the severity of this evaluation rule has been updated from medium to critical this change also applies to existing evaluations that include this rule for more information see log modes in the sap hana administration guide critical october 27 2025 sap hana insights sap hana high availability and disaster recovery set logshipping_async_buffer_size on the primary site if system replication is disconnected during a full data shipment then replication has to start from scratch in order to reduce the risk of buffer full situations the logshipping_async_buffer_size parameter can be adjusted to a value of 1 gb on the primary site 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 system replication in the sap knowledge base high october 27 2025 sap hana insights sap hana high availability and disaster recovery use the recommended value for the logshipping_max_retention_size parameter in context of logreplay operations modes the logshipping_max_retention_size sap hana parameter defines the maximum amount of redo logs that are kept on primary site for synchronization with the secondary site default 1 tb if the underlying file system isn t large enough to hold the complete configured retention size it can happen in the worst case that the file system runs full and the primary site comes to a standstill for more information see sap hana system replication in the sap knowledge base medium april 17 2025 sap hana insights sap hana performance check for appropriate configuration of the max_cpuload_for_parallel_merge parameter by default multiple auto merges up to num_merge_threads of different tables or partitions can be executed up to a cpu utilization limit of 45 but as soon as this limit is exceeded a maximum of one auto merge is executed at any time this can in the worst case result in an increased auto merge backlog although sufficient system resources for handling parallel auto merges would still be available in this case you can consider increasing this parameter to a value that is both higher than the usual cpu utilization and lower than a critical limit that would allow auto merges to introduce resource bottlenecks from october 27th 2025 the severity of this evaluation rule has been updated fr...
|
