Home » HP Manuals » Storage Devices » HP StoreOnce D2D4324 » Manual Viewer

HP StoreOnce D2D4324 HP StoreOnce VSA Deployment and Configuration Guide (TC45 - Page 54

Miscellaneous issues, Operations such as power-off, power-on

View all HP StoreOnce D2D4324 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 54 highlights

Miscellaneous issues Operations such as power-off, power-on, and storage addition on the StoreOnce VSA may fail when using vSphere with the message: Cause This behavior may happen when the vmdk descriptor file for the StoreOnce VSA is corrupt or missing or locked. This vmdk file corruption may also be caused by frequently changing the name of the StoreOnce VSA through vSphere GUI. . Solution Please refer to VMware troubleshooting documents on this issue. Search the VMware knowledge base on Verifying ESX/ESXi virtual machine file integrity (1003743) to find suggestions for resolving the issue. All VSAs/VMs on the ESXi server become unresponsive and all operations on StoreOnce VSAs fail Cause The ESXi server's VMFS file system heap size is not set to the maximum value. When total storage provisioned to the VMs/VSAs on the ESXi server exceeds the limit that a certain heap size setting on the server can manage, the VMs on the ESXi server become unresponsive. Solution The heap size variable for the ESXi server should be set to a maximum (640 MB) allowing smooth handling of VMDKs up to 60 TB. Make sure the ESXi servers are updated to the latest patches released by VMware. Please refer to VMware Knowledge base - article ID : 1004424. See also VMFS3.MaxHeapSizeMB setting (page 6). Emails are not sent to configured accounts The StoreOnce GUI is used to configure SMTP and email recipients for alerts, warnings and errors. Cause This may be a domain name resolution issue, when the SMTP server is represented by a domain name. Solution Set up the Email configuration using the SMTP server IP address instead of the fully qualified domain name. Adding/deleting replication targets fail with error "Maximum no. of sessions reached" Cause This behavior is seen when the fan-out limit on the StoreOnce VSA is reached. The StoreOnce VSA requires additional time to delete configuration information on the deleted target appliance and enable the addition of a new target device. This behavior is intermittent and is not seen always. 54 Troubleshooting

Section	Page
Contents	3
1 Introduction	5
Product description	5
StoreOnce VSA system requirements	5
Supported datastores	6
VMFS3.MaxHeapSizeMB setting	6
AMD support	6
Before you start deployment	8
StoreOnceVSA files required for deployment	9
Deployment overview	10
Logging on to the StoreOnce VSA after deployment	11
HPresetpassword account	11
For more information	11
HP StoreOnce documentation	11
HP StoreOnce Enterprise Manager documentation	11
vSphere documentation	12
Licensing	12
StoreOnce serial numbers	12
To redeem a purchased license	13
2 Deployment using HP StoreOnce Enterprise Manager (SEM)	14
Introduction	14
Before you start	14
Deployment process	15
To increase storage capacity using StoreOnce Enterprise Manager	21
To apply the license using SEM	24
3 Deployment using vSphere client	26
Introduction	26
Before you start	26
Deployment process	26
To create virtual disks for the StoreOnce VSA	32
To create a 1 TB virtual disk	33
To prepare and add storage using the StoreOnce CLI	37
To apply the license using StoreOnce CLI commands	38
To amend the network configuration after deployment	38
To check the current configuration	38
To run the net set wizard	38
4 Increasing virtual memory for optimal performance	40
5 Troubleshooting	43
Deployment Problems	44
StoreOnce VSA power-on fails after deployment	44
GUI displays blank and ‘system show status’ shows Service Set is unavailable / in a Failed to Start state	44
Deployment of StoreOnce VSA fails	45
StoreOnce VSA deployment through SEM fails after 98% progress	45
StoreOnce VSA deployment through SEM is 100% complete, however subsequent configuration stages fail	46
StoreOnce VSA power-on fails	46
Applying network settings fails	46
Storage addition problems	47
hardware discover storage / hardware prepare storage StoreOnce CLI command fails	47
Error running system show status	48
Data vdisks not recognized when executing the StoreOnce CLI storage addition commands	48
License alerts and issues	49
StoreOnce Instant-on license not installed alert	49
StoreOnce Instant-on license expired alert	49
Backup jobs fail with backup target size full error with Storage Report on GUI showing Free Space and Used Space as 0 GB	49
License addition fails with error “Invalid Device ID”	49
Instant-on license validity or number of days remaining is reduced	50
The VSA powers off after every power-on	50
License transfer is required	50
Network problems	51
Unable to access VSA over the network when default port —eth0 goes down	51
Performance problems	52
VSA writes and reads are slower in ESXi SAN environments	52
Power issues	53
The VSA service set goes down and file system becomes read-only	53
Backup jobs on VTLs fail after power shutdown	53
Miscellaneous issues	54
Operations such as power-off, power-on, and storage addition on the StoreOnce VSA may fail when using vSphere with the message: <File [unspecified file name] not found>	54
All VSAs/VMs on the ESXi server become unresponsive and all operations on StoreOnce VSAs fail	54
Emails are not sent to configured accounts	54
Adding/deleting replication targets fail with error “Maximum no. of sessions reached”	54
Time settings are reset when the StoreOnce VSA is rebooted	55
A fifth VT library gets created in the StoreOnceVSA automatically when the iSCSI initiator attached to the StoreOnce VSA is reset or refreshed	55
Logs for SEM and the StoreOnce VSA	55
Managing and resetting the password for the HPresetpassword account	55
To change the password for the HPresetpassword account	56
To reset the password for the local Admin user	56
6 Support and other resources	57
Contacting HP	57
Subscription Service	57
Related information	57
Websites	57
Typographic conventions	58

Match case Limit results 1 per page

Miscellaneous issues

Operations such as power-off, power-on, and storage addition on the StoreOnce

VSA may fail when using vSphere with the message: <File [unspecified file name]

not found>

Cause

This behavior may happen when the vmdk descriptor file for the StoreOnce VSA is corrupt or

missing or locked. This vmdk file corruption may also be caused by frequently changing the name

of the StoreOnce VSA through vSphere GUI. .

Solution

Please refer to VMware troubleshooting documents on this issue. Search the VMware knowledge

base on

Verifying ESX/ESXi virtual machine file integrity (1003743)

to find suggestions for resolving

the issue.

All VSAs/VMs on the ESXi server become unresponsive and all operations on

StoreOnce VSAs fail

Cause

The ESXi server’s VMFS file system heap size is not set to the maximum value. When total storage

provisioned to the VMs/VSAs on the ESXi server exceeds the limit that a certain heap size setting

on the server can manage, the VMs on the ESXi server become unresponsive.

Solution

The heap size variable for the ESXi server should be set to a maximum (640 MB) allowing smooth

handling of VMDKs up to 60 TB. Make sure the ESXi servers are updated to the latest patches

released by VMware. Please refer to

VMware Knowledge base - article ID : 1004424

. See also

VMFS3.MaxHeapSizeMB setting (page 6)

Emails are not sent to configured accounts

The StoreOnce GUI is used to configure SMTP and email recipients for alerts, warnings and errors.

Cause

This may be a domain name resolution issue, when the SMTP server is represented by a domain

name.

Solution

Set up the Email configuration using the SMTP server IP address instead of the fully qualified domain

name.

Adding/deleting replication targets fail with error “Maximum no. of sessions reached”

Cause

This behavior is seen when the fan-out limit on the StoreOnce VSA is reached.

The StoreOnce VSA requires additional time to delete configuration information on the deleted

target appliance and enable the addition of a new target device.

This behavior is intermittent and is not seen always.

Troubleshooting