Activity
|
Objective
|
Method
|
Expected Result
|
Actual Result
|
Pass or Not
|
SAP Clustering Test Scenarios
| |||||
Stopping HA heartbeat
|
To simulate heartbeat failure on each node
|
· Disable heartbeat on node 1 or node 2
|
· Nothing happen. No cluster resource failover. SAP users can work as normal
|
· No cluster resource failover. SAP users can work as normal
| |
Starting HA heartbeat
|
To simulate heartbeat failback on each node
|
· Enable heartbeat on node 1 or node 2
|
· Nothing happen. No cluster resource failback. SAP users can work as normal
|
· No cluster resource failback. SAP users can work as normal
| |
Stopping public network on node 1
|
To test HA failover on node 2 if node 1's public network is disabled
|
· Disable all public network on node 1
|
· Node 2 should sense that node1's public is down and should takeover all resources of node 1
|
· Cluster resource failover to node 2
| |
Starting public network on node 1
|
To test HA failback process when node1's public network is enabled
|
· Enable all public network on node 1
|
· All resource are still activated on node 2 (check node owner)
· The status of node 1 should be online
· Failback have to be manually performed
|
· Cluster resource still on node 2 ( no failback)
· node 1’s status is online
· Failback done by manual move cluster resource group with MCSG Cluster Admin.
· Stop SAP CI on Node2 by halt resource
· Start SAP CI on Node1 by start resource
· Start SAP DI on Node2
| |
Stopping all public network on node 2
|
To test HA redundancy interface card on node 2 if node 2's one public network is disabled
|
· Disable all public network on node 2
|
· Nothing happen. No cluster resource failback. SAP users can work as normal
|
· Cluster resource still on node 1
· Node 2’s status is online
· Node 2's public interface offline
| |
Starting public network on node 2
|
To test HA normally process when node2's public network is enabled
|
· Enable all public network on node 2
|
· All resource are still activated on node 1 (check node owner)
· The status of node 2 should be online
|
· Cluster resource still on node 1
· Node 2’s status is online
| |
Power failure on node 1
|
To test HA failover on node 2 if node 1 suddenly shutdown
|
· Turn-off server by pressing the power button located on the server's front panel
|
· Node 2 should sense that node 1 is down and should takeover all resources of node 1
|
· Cluster resource failover to node 2
| |
Power restore on node 1
|
To test HA failback process when power is restored and node 1 is properly booted
|
· Turn-on server by pressing the power button located on the server's front panel
|
· All resource are still activated on node 2 (check node owner)
· The status of node 1 should be online
· Failback have to be manually performed
|
· No cluster failback to node 1
· Node 1’s status is online
| |
Power restore on node 2
|
To test HA failback process when power is restored and node 2 is properly booted
|
· Turn-on server by pressing the power button located on the server's front panel
|
· All resource are still activated on node 1 (check node owner)
· The status of node 2 should be online
· Failback have to be manually performed
|
· No Cluster failback to node 2
· Node 2’s status is online
| |
Showing posts with label Project/Plan Management. Show all posts
Showing posts with label Project/Plan Management. Show all posts
Scenarios Test SAP Clustering Failover
** Team
Scenarios Test case Backup and Restore
** Team
Activity
|
Objective
|
Method
|
Expected Result
|
Actual Result
|
Pass or Not
|
Backup Test Scenarios
| |||||
DEV System
| |||||
Backup Testing
|
To test the backup and procedures from software backup for accuracy and completeness
|
· Backup SAP Data
|
· Successful - no errors
|
· Successful with no error
| |
QAS System
| |||||
Backup Testing
|
To test the backup and procedures from software backup for accuracy and completeness
|
· Backup SAP Data
|
· Successful - no errors
|
· Successful with no error
| |
PRDSystem
| |||||
Backup Testing
|
To test the backup and procedures from software backup for accuracy and completeness
|
· Backup SAP Data From Snap Clone
|
· Successful - no errors
|
· Successful with no error
| |
Restore Test Scenarios
| |||||
DEV System
| |||||
Restore and recovery Testing and startup for usage testing
|
To test the startup and shutdown procedures for accuracy and completeness
|
· Startup and shutdown system, hardware and software services
|
· Successful - no errors
|
· Successful with no error
| |
QAS System
| |||||
Restore and recovery Testing and startup for usage testing
|
To test the startup and shutdown procedures for accuracy and completeness
|
· Startup and shutdown system, hardware and software services
|
· Successful - no errors
|
· Successful with no error
| |
PRD System
| |||||
Restore and recovery Testing and startup for usage testing
|
To test the startup and shutdown procedures for accuracy and completeness
|
· Startup and shutdown system, hardware and software services
|
· Successful - no errors
|
· Successful with no error
| |
SAP BASIS Project Activity(Task) Plan for Migrate Physical server to VM
** Myself
No.
|
Activities
|
Server /System
|
Responsible (Name/Team)
|
Start Date/Time
|
End Date/Time
|
Duration
(hh:mm) |
Preparation Step
| ||||||
1
|
Check Backup to tape complete
|
PRD
|
Unix
|
29-Apr-10 16:45
|
29-Apr-10 17:00
|
0:15
|
Deployment Step
| ||||||
1
|
Install MS Patch
|
PRD/PRD
|
SAP_BASIS
|
29-Apr-10 17:00
|
29-Apr-10 17:45
|
0:45
|
2
|
Hold Queue and job - SAP Production SAP PRD
|
PRD/PRD
|
SAP_BASIS
|
29-Apr-10 17:45
|
29-Apr-10 17:50
|
0:05
|
3
|
Stop SAP Production SAP PRD
|
PRD/PRD
|
SAP_BASIS
|
29-Apr-10 17:50
|
29-Apr-10 18:05
|
0:15
|
4
|
Perform P2V Conversion
|
PRD/PRD
|
Unix
|
29-Apr-10 18:05
|
29-Apr-10 22:05
|
4:00
|
5
|
Configure VM PRD
|
PRD/PRD
|
Unix
|
29-Apr-10 22:05
|
29-Apr-10 23:05
|
1:00
|
6
|
Shutdown physical servers & Startup SAP Production SAP PRD on VM
|
PRD/PRD
|
SAP_BASIS
|
29-Apr-10 23:05
|
29-Apr-10 23:25
|
0:20
|
7
|
Check system log (Check Point#1)
|
PRD/PRD
|
SAP_BASIS
|
29-Apr-10 23:25
|
29-Apr-10 23:40
|
0:15
|
8
|
Release Queue and job - SAP Production SAP PRD on VM
|
PRD/PRD
|
SAP_BASIS
|
29-Apr-10 23:40
|
30-Apr-10 00:00
|
0:20
|
Backout Plan
| ||||||
Check Point#1
| ||||||
1
|
Start SAP Production SAP PRD
|
PRD/PRD
|
SAP_BASIS
|
29-Apr-10 23:40
|
29-Apr-10 23:55
|
0:15
|
2
|
Release Queue and job - SAP Production SAP PRD
|
PRD/PRD
|
SAP_BASIS
|
29-Apr-10 23:55
|
30-Apr-10 00:00
|
0:05
|
Fallback Plan
| ||||||
1
|
Start SAP Production SAP PRD
|
PRD/PRD
|
SAP_BASIS
|
0:15
| ||
2
|
Release Queue and job - SAP Production SAP PRD
|
PRD/PRD
|
SAP_BASIS
|
0:05
| ||
Subscribe to:
Posts (Atom)