Thursday, January 5, 2017

How much swap space should the Linux/Redhat system have?

Swap space in Linux is used when the amount of physical memory (RAM) is full. If the system needs more memory resources and the RAM is full, inactive pages in memory are moved to the swap space. While swap space can help machines with a small amount of RAM, it should not be considered a replacement for more RAM. Swap space is located on hard drives, which have a slower access time than physical memory. Swap space can be a dedicated swap partition (recommended), a swap file, or a combination of swap partitions and swap files.

However, modern systems often include hundreds of gigabytes of RAM. As a consequence, recommended swap space is considered a function of system memory workload, not system memory.

Amount of RAM in the system
Recommended swap space
Recommended swap space if allowing for hibernation
 2 GB
2 times the amount of RAM
3 times the amount of RAM
> 2 GB – 8 GB
Equal to the amount of RAM
2 times the amount of RAM
> 8 GB – 64 GB
At least 4 GB
1.5 times the amount of RAM
> 64 GB
At least 4 GB
Hibernation not recommended



Thursday, March 26, 2015

Setting Access Permissions on Shared Folders for View Persona Management

View Persona Management and Windows roaming profiles require a specific minimum level of permissions on the user profile repository. View Persona Management also requires that the security group of the users who put data on the shared folder must have read attributes on the share.
Set the required access permissions on your user profile repository and redirected folder share.
Minimum NTFS Permissions Required for the User Profile Repository and Redirected Folder Share
User Account
Minimum Permissions Required
Creator Owner
Full Control, Subfolders and Files Only
Administrator
None. Instead, enable the Windows group policy setting, Add the Administrators security group to the roaming user profiles. In the Group Policy Object Editor, this policy setting is located in Computer Configuration\Administrative Templates\System\User Profiles\.
Security group of users needing to put data on share
List Folder/Read Data, Create Folders/Append Data, Read Attributes - This Folder Only
Everyone
No permissions
Local System
Full Control, This Folder, Subfolders and Files
Share Level (SMB) Permissions Required for User Profile Repository and Redirected Folder Share
User Account
Default Permissions
Minimum Permissions Required
Everyone
Read only
No permissions
Security group of users needing to put data on share
N/A
Full Control 

Wednesday, December 24, 2014

VNX Pool Capacity, Tier information, FAST VP Operation status

> To see Pool Capacity
naviseccli -h IP storagepool -list -tiers

> FAST VP AutoTier operation status/details
naviseccli -h ip autotiering -info -opstatus


Wednesday, September 10, 2014

Requirements ESRS IP Client:

Requirements ESRS IP Client:
 1. Dedicated VM with Windows 2003/08 server
 2. A Static IP network with Internet connectivity
3. Network connectivity between the servers and EMC devices to be managed by ESRS IP
 4. Internet connectivity to EMC’s ESRS infrastructure by using outbound port 80, 443 and 8443
 5. VC++, .Net Framework (min 2.0)
 6. Port number 25 needs to be open from ESRS IP Client machine to SMTP Server

Thursday, April 17, 2014

EMC Powerpath

• powermt check ( – select option –a ) ( This is needed when you reboot the server Mostly for patching do – Disk Management Rescan and run the command to clear dead paths ) • powermt update lun_names ( This is needed when LUN names is to be updated and you have to update in the system to refresh same)

Friday, March 28, 2014

Reconfiguring Storage Processor (SP) IP address using Navisphere Manager



Reference

Reconfiguring Storage Processor (SP) IP address using Navisphere Manager


CLARiiON CX Series,CLARiiON iSCSI Array.

Description:

Procedure to reconfigure SP IP address using Navisphere Manager.

Resolution:

The storage processor (SP) IP address can only be set through the /setup page. Please follow the steps give below.

If this procedure is done with active hosts attached to the array, ensure that there are no single HBA-attached hosts and that failover software is configured on each multi HBA attached host. SPs will reboot each time the IP address change is submitted.   Wait to change the other SP's IP address until the first SP has rebooted.
1.        If the storage system to be reconfigured is the domain master, select a new domain master before proceeding.
2.        Make sure both SPs for which you want to change IP addresses are connected to the network
3.        If the array on which you want to set or cannot set the IP address ("problem array") is in a domain with other arrays, open Navisphere Manager on one of the other arrays and remove it from the domain using the Configure Domain dialog.
4.        Open the setup page for SP A <SP A IP address/setup> on the array.
5.        Reset security and domain information for SP-A by pressing the "Reset Security" button.  Select "Yes" and "Submit" to confirm.
6.        Re-open the setup page for SP A on the array and restart the Management Server by pressing the "Restart Management Server" button.  Select "Yes" and "Submit" to confirm.
7.        Open the setup page for SP B <SP B IP address/setup> on the array.
8.        Reset security and domain information for SP B by pressing the "Reset Security" button.  Select "Yes" and "Submit" to confirm.
9.        Re-open the setup page for SP B on the array and restart the Management Server by pressing the "Restart Management Server" button.  Select "Yes" and "Submit" to confirm.
10.     Once the Management Server on SP A and SP B has been restarted, security and domain information will be in an uninitialized state.  You should now be able to set the IP addresses using the following steps
11.     Open a browser and go to <Current SP A IP address/setup
12.     In the IP address field change the current SP A IP address to the new SP A IP address and click "Apply Settings". SP A will reboot which may take up to five minutes to complete
13.     Go back to SP A's setup page using the new SP A IP address <New SP A IP Address/setup>
14.     Open a browser and go to <Current SP B IP address/setup>
15.     In the IP address field enter SP B's new IP address and in the Peer IP Address field enter SP A's new IP address and click "Apply Settings". SP B will reboot which may take up to five minutes to complete.
16.     Go back to the SP B setup page <new SP B IP Address/setup>  and click "Restart Management Server". Select "Yes" and "Submit" on the pop up screen.
17.     Go to SP A setup page <New SP A IP Address/setup> (You may already be there due to step number 12)  and click "Restart Management Server".  Select "Yes" and "Submit" on the pop up screen.   This will update the peer IP address on SP A.
18.     If the array will be back in a domain with other arrays, re-add  it to the existing domain.  Security will automatically be initialized by obtaining the necessary information from the domain master. If it was originally in the domain and it was the domain master you can now select it as the domain master again.  If the array is not to be in a domain, open Navisphere Manager on SP A of the array. You should now be prompted to initialize security.  Select "Yes" and add a global username and password. 

Friday, March 14, 2014

How to migrate Clariion to VNX using SANCopy (naviseccli)

SANCopy syntax:

naviseccli -h -create -name name <-incremental>
[-srcwwn srcwwn|
-srclun srcspname srcNumOrSnapshotName <-device devicename="">|
-srcportwwn srcportwwn srclunnumber]
[-destwwn destwwns|
-destlunnumber destspname destlunnumber <-device devicename="">|
-destportwwn destportwwn destlunnumber]
<-changesonly> <-verify> <-start> <-throttle 1-10="">
<-linkbw linkbw=""> <-latency latency=""> <-o>

Example:
navicli -h sancopy -create -name -srcwwn xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx destlunnumber -verify

Start SANCopy:

naviseccli -h sancopy -start -name