Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
redcoon Absent Member.
Absent Member.
661 views

DP6.2: SMISA starting drive scan

Jump to solution

Hello,

since upgrading to DP 6.2 I experience a strange behavior regarding SMIS Agent.

When starting a backup using Snapshots he creates the snapshots and presents them to the backup host. But then he starts a drive scan ("Starting drive scan") which takes nearly an hour or even longer. Sometimes he gets stuck here, sometime at the next step when he says "Drive scan has completed". But he is not starting to write data to tape or disk.

Where could be the problem?

0 Likes
1 Solution

Accepted Solutions
redcoon Absent Member.
Absent Member.

Re: DP6.2: SMISA starting drive scan

Jump to solution

I think I found a problem, but outside of Data Protector. It seems to be a problem with disk management of Windows 2k8 R2. It runs instable at this moment, will try to have a look at it.

 

Thanks everyone for your suggestions.

0 Likes
5 Replies
Knowledge Partner
Knowledge Partner

Re: DP6.2: SMISA starting drive scan

Jump to solution

Hi,

 

Do you install latest parches for DP6,2?

Do you check teh configuration in you librery?

 

Post output for devbra -dev , and compare with your library properties in the GUI.

 

Regards

Please assign a kudo to this post, if you find it useful.
0 Likes
redcoon Absent Member.
Absent Member.

Re: DP6.2: SMISA starting drive scan

Jump to solution

output of devbra -dev is: (matches exacly the entries in the DP GUI)

 

C:\Windows\system32>devbra -dev

Tape HP:Ultrium 5-SCSI Path: "Tape5:0:1:0C" SN: "HU1046DKH4"
Description: CLAIMED:HP LTO drive
Revision: I3BW Device type: lto [13] Flags: 0x0111

Tape HP:Ultrium 3-SCSI Path: "Tape4:0:0:3C" SN: "HU105265JF"
Description: CLAIMED:HP LTO3 Drive
Revision: G65W Device type: lto [13] Flags: 0x0011

Tape HP:Ultrium 3-SCSI Path: "Tape3:0:0:2C" SN: "HU10839LDM"
Description: CLAIMED:HP LTO3 Drive
Revision: G65W Device type: lto [13] Flags: 0x0011

Exch HP:MSL6000 Series Path: "Changer1:0:0:1" SN: "USX529006A"
Description: CLAIMED:HP StorageWorks MSL 6000 Series
Revision: 0520 Flags: 0x0016 Slots: 58 Drives: 4
Drive(s) SN:
"HU10839LDM"
"HU105265JF"
"HU10623GYU"
"HU109064M4"

Exch HP:MSL G3 Series Path: "Changer0:0:1:1" SN: "DEC04905YW"
Description: CLAIMED:HP StorageWorks MSL 2024 G3 Series
Revision: 1000 Flags: 0x0016 Slots: 92 Drives: 2
Drive(s) SN:
"HU1046DKHE"
"HU1046DKH4"

Tape HP:Ultrium 5-SCSI Path: "Tape2:0:1:0C" SN: "HU1046DKHE"
Description: CLAIMED:HP LTO drive
Revision: I3BW Device type: lto [13] Flags: 0x0111

Tape HP:Ultrium 3-SCSI Path: "Tape1:0:0:2C" SN: "HU109064M4"
Description: CLAIMED:HP LTO3 Drive
Revision: G65W Device type: lto [13] Flags: 0x0011

Tape HP:Ultrium 3-SCSI Path: "Tape0:0:0:1C" SN: "HU10623GYU"
Description: CLAIMED:HP LTO3 Drive
Revision: G65W Device type: lto [13] Flags: 0x0011

0 Likes
ranjithpk Honored Contributor.
Honored Contributor.

Re: DP6.2: SMISA starting drive scan

Jump to solution

Could you please try manually scanning the device and find the time.

Hpux: date;ioscan;date

 

If its taking more time,you need to check the SAN to reduce the time (maybe removing from many ZONE).

Regards,
Ranjith
0 Likes
Trusted Contributor.. Joerg Richter Trusted Contributor..
Trusted Contributor..

Re: DP6.2: SMISA starting drive scan

Jump to solution

Hi,

 

this drive scan is a designed "feature"  in 6.11/6.2 to prevent problems with parallel operations.

 

It is possible to run several EVA/P6000 ZDB session at the same time, which might share the same backup server for replica presentation and in order to prevent problems the system is scanned for already presented replicas.  

 

I'm not aware of any omnirc or similar parameter to switch off the check, but even if it would exist you might loose support of your setup.

 

Regards,

 

0 Likes
redcoon Absent Member.
Absent Member.

Re: DP6.2: SMISA starting drive scan

Jump to solution

I think I found a problem, but outside of Data Protector. It seems to be a problem with disk management of Windows 2k8 R2. It runs instable at this moment, will try to have a look at it.

 

Thanks everyone for your suggestions.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.