Paging problem in Windows 2008

[Former Member]

Hello Gurus,

We have a project of system migration in OS and database, we made the kernel update and JVM with the corresponding notes, after the process of migration every works fine but in the operative system upgrade from 2003 to 2008 R2 SP1, the system made paging  in C: drive only. We try to put the paging configuration in other drive, but only used the space left in C:, this give us a problem in the performance of the system.

do you have any clue of why is this happen?

Regards,

[former_member188883]

Hi Jose,

Post adding the paging space in other drive, did you reboot the server ?

Regards,

Deepak Kori

[Former Member]

Hi Deepak,

We restar several times the server, but still have the issue.

Regards,

[former_member188883]

Hi Jose,

Please check on your server settings how much page size it is showing.

Ensure total page = paging in C:\drive + other drive.

If note, then there looks to be some problem with registry entries

Open registry and search for pagefiles.

Ensure paths are correctly specified along with size.

Take a restart and check the results.

Hope this helps.

Regards,

Deepak Kori

[Sriram2009]

Hi Jose

Kindly check the follows

1. Have you applied latest windows 2008 service pack? kindly refer the SAP Note

30478 - Windows Service Packs

2. Have you updated the Windows update from Microsoft site?

3. After migration of SAP system have you define the memory parameters? as mention in the SAP Notes

1280759 - SAP recommends only 64-Bit Windows for SAP Appl. Servers

88416 - Zero administration memory management for the ABAP server

1612283 - Hardware Configuration Standards and Guidance

Regards

Sriram

[Former Member]

can you please open a powershell in elevate mode and run following two commands in them (and post the output of the commands here):

It will give us an output of the computers current pagefile configuration.

In the example below we can see, that on C: a pagefile with a custom size is defined (20GB Minimum growing up to 40 GB) on E: InitialSize and MaximumSize is 0 which indicates that the size is automatically maintained by the operating system.

This setting (E:) is not recommended, because it will increase the size of the pagefile much slower than the application may request memory - hence, even if you have sufficient free space on disk E: it may result in allocation failures.

As far as I know, the operating system will prefer to use a sufficient sized pagefile on C: because it needs it to create system crash dumps. If you are using automatic sized pagefiles (system managed), I expect the operating system to increase the pagefile on C: up to the size of RAM available, before it is starting to increase and use additional pagefiles on other disks.

You only can eliminate this effect by not using any automatism.

regards

Peter

---------------

Powershell commands for detecting current pagefile configuration:

get-wmiobject WIN32_PAGEFILE | Format-List *
get-wmiobject WIN32_PAGEFILESETTING | Format-List *

---------------

output looks like:

PS C:\Users\d020904\Documents> get-wmiobject win32_pagefilesetting  | format-list *

PSComputerName  : WSIV0022
__GENUS          : 2
__CLASS          : Win32_PageFileSetting
__SUPERCLASS    : CIM_Setting
__DYNASTY        : CIM_Setting
__RELPATH        : Win32_PageFileSetting.Name="c:\\pagefile.sys"
__PROPERTY_COUNT : 6
__DERIVATION    : {CIM_Setting}
__SERVER        : WSIV0022
__NAMESPACE      : root\cimv2
__PATH          : \\WSIV0022\root\cimv2:Win32_PageFileSetting.Name="c:\\pagefile.sys"
Caption          : c:\ 'pagefile.sys'
Description      : 'pagefile.sys' @ c:\
InitialSize      : 20480
MaximumSize      : 40960
Name            : c:\pagefile.sys
SettingID        : pagefile.sys @ c:
Scope            : System.Management.ManagementScope
Path            : \\WSIV0022\root\cimv2:Win32_PageFileSetting.Name="c:\\pagefile.sys"
Options          : System.Management.ObjectGetOptions
ClassPath        : \\WSIV0022\root\cimv2:Win32_PageFileSetting
Properties      : {Caption, Description, InitialSize, MaximumSize...}
SystemProperties : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers      : {dynamic, Locale, provider, UUID}
Site            :
Container        :


PSComputerName  : WSIV0022
__GENUS          : 2
__CLASS          : Win32_PageFileSetting
__SUPERCLASS    : CIM_Setting
__DYNASTY        : CIM_Setting
__RELPATH        : Win32_PageFileSetting.Name="e:\\pagefile.sys"
__PROPERTY_COUNT : 6
__DERIVATION    : {CIM_Setting}
__SERVER        : WSIV0022
__NAMESPACE      : root\cimv2
__PATH          : \\WSIV0022\root\cimv2:Win32_PageFileSetting.Name="e:\\pagefile.sys"
Caption          : e:\ 'pagefile.sys'
Description      : 'pagefile.sys' @ e:\
InitialSize      : 0
MaximumSize      : 0
Name            : e:\pagefile.sys
SettingID        : pagefile.sys @ e:
Scope            : System.Management.ManagementScope
Path            : \\WSIV0022\root\cimv2:Win32_PageFileSetting.Name="e:\\pagefile.sys"
Options          : System.Management.ObjectGetOptions
ClassPath        : \\WSIV0022\root\cimv2:Win32_PageFileSetting
Properties      : {Caption, Description, InitialSize, MaximumSize...}
SystemProperties : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers      : {dynamic, Locale, provider, UUID}
Site            :

Container        :

[Former Member]

Hello  Peter ,

thank you for the help, this is the output of the both commands

PS C:\Users\xi1adm> get-wmiobject WIN32_PAGEFILESETTING | Format-List *




__GENUS          : 2
__CLASS          : Win32_PageFileSetting
__SUPERCLASS     : CIM_Setting
__DYNASTY        : CIM_Setting
__RELPATH        : Win32_PageFileSetting.Name="c:\\pagefile.sys"
__PROPERTY_COUNT : 6
__DERIVATION     : {CIM_Setting}
__SERVER         : SRV-CRXIPP01
__NAMESPACE      : root\cimv2
__PATH           : \\SRV-CRXIPP01\root\cimv2:Win32_PageFileSetting.Name="c:\\pagefile.sys"
Caption          : c:\ 'pagefile.sys'
Description      : 'pagefile.sys' @ c:\
InitialSize      : 800
MaximumSize      : 800
Name             : c:\pagefile.sys
SettingID        : pagefile.sys @ c:
Scope            : System.Management.ManagementScope
Path             : \\SRV-CRXIPP01\root\cimv2:Win32_PageFileSetting.Name="c:\\pagefile.sys"
Options          : System.Management.ObjectGetOptions
ClassPath        : \\SRV-CRXIPP01\root\cimv2:Win32_PageFileSetting
Properties       : {Caption, Description, InitialSize, MaximumSize...}
SystemProperties : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers       : {dynamic, Locale, provider, UUID}
Site             :
Container        :


__GENUS          : 2
__CLASS          : Win32_PageFileSetting
__SUPERCLASS     : CIM_Setting
__DYNASTY        : CIM_Setting
__RELPATH        : Win32_PageFileSetting.Name="f:\\pagefile.sys"
__PROPERTY_COUNT : 6
__DERIVATION     : {CIM_Setting}
__SERVER         : SRV-CRXIPP01
__NAMESPACE      : root\cimv2
__PATH           : \\SRV-CRXIPP01\root\cimv2:Win32_PageFileSetting.Name="f:\\pagefile.sys"
Caption          : f:\ 'pagefile.sys'
Description      : 'pagefile.sys' @ f:\
InitialSize      : 23000
MaximumSize      : 23000
Name             : f:\pagefile.sys
SettingID        : pagefile.sys @ f:
Scope            : System.Management.ManagementScope
Path             : \\SRV-CRXIPP01\root\cimv2:Win32_PageFileSetting.Name="f:\\pagefile.sys"
Options          : System.Management.ObjectGetOptions
ClassPath        : \\SRV-CRXIPP01\root\cimv2:Win32_PageFileSetting
Properties       : {Caption, Description, InitialSize, MaximumSize...}
SystemProperties : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers       : {dynamic, Locale, provider, UUID}
Site             :
Container        :






PS C:\Users\xi1adm> get-wmiobject WIN32_PAGEFILE | Format-List *




__GENUS               : 2
__CLASS               : Win32_PageFile
__SUPERCLASS          : CIM_DataFile
__DYNASTY             : CIM_ManagedSystemElement
__RELPATH             : Win32_PageFile.Name="c:\\pagefile.sys"
__PROPERTY_COUNT      : 36
__DERIVATION          : {CIM_DataFile, CIM_LogicalFile, CIM_LogicalElement, CIM_ManagedSystemElement}
__SERVER              : SRV-CRXIPP01
__NAMESPACE           : root\cimv2
__PATH                : \\SRV-CRXIPP01\root\cimv2:Win32_PageFile.Name="c:\\pagefile.sys"
AccessMask            :
Archive               : True
Caption               : c:\pagefile.sys
Compressed            : False
CompressionMethod     :
CreationClassName     : CIM_LogicalFile
CreationDate          : 20140502100342.029989-360
CSCreationClassName   : Win32_ComputerSystem
CSName                : SRV-CRXIPP01
Description           : c:\pagefile.sys
Drive                 : c:
EightDotThreeFileName : c:\pagefile.sys
Encrypted             : False
EncryptionMethod      :
Extension             : sys
FileName              : pagefile
FileSize              : 838860800
FileType              : System file
FreeSpace             :
FSCreationClassName   : Win32_FileSystem
FSName                : NTFS
Hidden                : True
InitialSize           : 800
InstallDate           : 20140502100342.029989-360
InUseCount            :
LastAccessed          : 20140502100342.029989-360
LastModified          : 20140514085727.406250-360
Manufacturer          :
MaximumSize           : 800
Name                  : c:\pagefile.sys
Path                  : \
Readable              : True
Status                : OK
System                : True
Version               :
Writeable             : True
Scope                 : System.Management.ManagementScope
Options               : System.Management.ObjectGetOptions
ClassPath             : \\SRV-CRXIPP01\root\cimv2:Win32_PageFile
Properties            : {AccessMask, Archive, Caption, Compressed...}
SystemProperties      : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers            : {dynamic, Locale, provider, UUID}
Site                  :
Container             :

[Former Member]

can you please also add the output of:

Get-WmiObject WIN32_PAGEFILEUSAGE | Format-List -property *

Thanks

Peter

[Former Member]

Hello Peter,

Thank you  for all the help, we put the result of the command.

Best Regards,

PS C:\Users\xi1adm> Get-WmiObject WIN32_PAGEFILEUSAGE | Format-List -property *




Status            :
Name              : C:\pagefile.sys
CurrentUsage      : 7
__GENUS           : 2
__CLASS           : Win32_PageFileUsage
__SUPERCLASS      : CIM_LogicalElement
__DYNASTY         : CIM_ManagedSystemElement
__RELPATH         : Win32_PageFileUsage.Name="C:\\pagefile.sys"
__PROPERTY_COUNT  : 9
__DERIVATION      : {CIM_LogicalElement, CIM_ManagedSystemElement}
__SERVER          : SRV-CRXIPP01
__NAMESPACE       : root\cimv2
__PATH            : \\SRV-CRXIPP01\root\cimv2:Win32_PageFileUsage.Name="C:\\page
AllocatedBaseSize : 800
Caption           : C:\pagefile.sys
Description       : C:\pagefile.sys
InstallDate       : 20140502100342.029989-360
PeakUsage         : 65
TempPageFile      : False
Scope             : System.Management.ManagementScope
Path              : \\SRV-CRXIPP01\root\cimv2:Win32_PageFileUsage.Name="C:\\page
Options           : System.Management.ObjectGetOptions
ClassPath         : \\SRV-CRXIPP01\root\cimv2:Win32_PageFileUsage
Properties        : {AllocatedBaseSize, Caption, CurrentUsage, Description...}
SystemProperties  : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers        : {dynamic, Locale, provider, UUID}
Site              :
Container         :

[Former Member]

well this pretty looks like a system with sufficient RAM.

You have only used 64 MB of the pagefile on C.

What happens if more memory is used?

You can try to allocate more memory by using SAP's memlimits.exe:

• Logon as <sid>adm
• Open a powershell Windows
• enter perfmon in the powershell
• in the perfmon Windows you navigate - Performance - Monitoring Tools - Performance Monitor
• here you click the + button
• in the counters listbox select Paging File
• in the Instances of selected object list select both pagefiles and add them to the added counters --> OK
• now start following command in the powershell window:
  memlimits.exe -a yes -l 20000

This command will allocate 20 GB (20000 MB) of heap.

Track the monitor information in regards to pagefile usage.

You may start with smaller values than 20000 and increase this number in later iterations to higher values.

I expect the pagefile on E: growing if the system starts using it.

Please be aware that a general memory shortage (RAM and Pagefile are completely used) may destabilize your operating system, with a need to reboot it.

kind regards

Peter

[Former Member]

Hello Peter,

We apply the memlimits but just allocate maximun 7712 Mb, even we restart the server and have the same result, what other thing we can do ?

Best regards,

PS C:\Users\xi1adm> memlimits.exe -a yes -l 10000
SAP R/3 address space configuration test tool V3.2 (98/01/14)
=============================================================




Check the maximum data size per process (malloc)
Access allocated pages to force swap space allocation
in systems with lazy (late) swap allocation strategy.
The checking will time out after 600 seconds
allocating / accessing   7712 MB
Maximum process heap size =  7712MB




+-------------------------------------------------------+
|                        Result                         |
+-------------------------------------------------------+
Maximum heap size per process........:  7712 MB
    this value is probably limited by swap space
Total available swap space...........:  7712 MB
    main memory size x 3 recommended , minimum 1 GB
    swap space probably even bigger, but cannot be
    totally allocated by only one process

[Former Member]

What does get-wmiobject win32_pagefileusage report after running memlimits?

What kind of disk is E:\

[Former Member]

Hello peter,

With the command just appear C pagefile, the  F: is a virtual drive  with primary partition, but before the SO upgrade the paging configuration works fine.

Best Regards,

[Former Member]

to get a complete picture I need to understand what kind of virtual drive F: is.

Did you migrate your system to a VM?

If so, I assume C: is also a virtual drive?

If so, is it located on the same host volume as F:?