SNAPI commands not working after SN upgraded 4.3.2 to 5.2

This is related to SR: StorNext M-Series Escalation To SES From SPS: SR3512412, Customer:Cinesys/Primerica:

SNAPI commands not working after SN upgraded 4.3.2 to 5.2

 

From Sue Bechly:

 

 

From: Sue Bechly
Sent: Monday, March 16, 2015 10:12 AM
To: German Krackow; Oliver Lemke; DL-SN-SES
Cc: DL-Service EMEA - SW; DL-KL ASPS Tech Support; Isabel Vigil; Kevin Poole; StorNext Sustaining Engineers
Subject: RE: StorNext M-Series Escalation To SES From SPS: SR3512412, Customer:Cinesys/Primerica -- CatDV SN Retrieve, SNAPI commands not working after SN upgraded 4.3.2 to 5.2, , Serial Number: CX1310CKD00027
 
See CRs – 54978 and 54986
 
The following text was added to the StorNext 5 Release Notes (with 5.2.0.1) -
 
Description:
The StorNext Web Service interface GetFileAttribute propagates an incorrect value for the location field. Prior to StorNext 5 release 5.2, locations could include TAPE and DISK AND TAPE, in StorNext 5 release 5.2 and StorNext 5 release 5.2.0.1, the locations are returned as ARCHIVE and DISK AND ARCHIVE.
 
Workaround:
In order to work around this issue, add the following line to the
/usr/adic/.profile file.
 
export SNAPI_COMPAT_MODE=TRUE
 
Then restart the GUI by executing the following command:
 
/usr/adic/tomcat/bin/service stornext_web restart
 
This will return the output of the GetFileAttribute to respond with TAPE as a location rather than ARCHIVE.
This Known Issue will be addressed in a future release of StorNext 5.

 

 

Notes

 Might be better to create a KB Article instead QWiki.

Note by Michael Richter on 03/17/2015 03:34 AM


This page was generated by the BrainKeeper Enterprise Wiki, © 2018