Problems Connecting To The Storeonce System From The Backup Application; Timeout Problems With Nas Cifs Shares - HPE StoreOnce 6500 User Manual

Table of Contents

•

No more than 8 active operator sessions for the GUI

•

No more than 16 active operator sessions for the CLI

•

No more than 1 active administrator session to ensure there is no confusion when configuration

changes are made

Currently, you cannot see which users are logged in. The accounts show command will list all the user

accounts defined for the StoreOnce System. For each account the authority level is provided.

Problems connecting to the StoreOnce System from the

backup application

Perform the following checks:

•

Make sure you have the latest version or software patches for the backup application. See

www.hpe.com/info/ebs

for supported applications.

•

Stop and restart the backup application services after the backup device has been discovered. If you

still cannot access the device, check the Device Manager to make sure it is accessible from the host.

•

For Fibre Channel devices: Models with an 8Gb Fibre Channel card have a theoretical limit of 255

devices per Fibre Channel port on a host or switch; models with 4Gb Fibre Channel card have a

theoretical limit of 127 devices per Fibre Channel port on a host or switch.

NOTE:

There are practical limitations on the number of devices that each host, Fibre Channel switch, or HBA can

access. It is possible to configure more drive and library devices than a host can access. Although the

Fibre Channel connection supports a greater theoretical number of devices per Fibre Channel port on a

host or switch, HPE recommends that no more than 64 devices are configured for use by a single host.

Timeout problems with NAS CIFS shares

By default, Windows CIFS timeout is set low for NAS backup implementations. This can lead to various

error message related to lost connection to the share, unrecoverable write errors or timeout problems

resulting backup job failures. It is recommended to add or to increase the "SessTimeout" value from the

default of 45 (seconds) to 300 (five minutes).

Increasing the timeout ensures that the Windows CIFS timeout does not cause your backup application to

prematurely timeout the running job.

NOTE:

This can resolve issues resulting from timeouts, but is not exclusively the only reason for such failures. A

large number of 'out of sequence' writes causing slow response times within the product often can be the

root cause. Further analysis may be required if increasing the timeout is not successful.

In order to increase the timeout: