Re: [Veritas-bu] ACSLS 8.0.2 and NBU 7.1(.0.2)

[Scott Jacobson]

You might try adding to your vm.conf:
 
ACS_TCP_RPCSERVICE
ACS_SSI_HOSTNAME =  What ever your fully qualified 
name is for the media or master server
ACS_SSI_SOCKET =   13741
 
-sj


>>> Rusty Major  10/3/2011 12:03 PM >>>

Hi All,
 
Fresh install of NBU 7.1 with ACSLS 8.0.2, both on Solaris 10. I am unable to 
get NBU to communicate with ACSLS without forcing the port to communicate over 
in vm.conf (ACS_CSI_HOSTPORT). This works fine until the ACSLS application is 
restarted and the port changes.

I noticed with NBU version 7.1.0.0, MM and ACS daemons would not even start up, 
but when I patched to 7.1.0.2, all the appropriate daemons started, but there 
was still no communication with ACSLS without the above mentioned vm.conf 
entry. ACSLS is configured with default settings.
 
I have an ACSLS 8.0.2 server working with NBU version 6.5.x without any issues 
(same default ACSLS settings and no entries in VM.CONF).
 
Has anyone run across this and have any pointers?
Thanks,
-Rusty
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS 8.0.2 and NBU 7.1(.0.2)

[Rusty Major]

It turned out rpcbind was not setup correctly. This is a note that the Sun
Engineer sent me:

Symptoms
Although RPC is enabled on the ACSLS server, RPC clients cannot
communicate to it.
rpcinfo, when called from the client server, fails with an "Authentication
error".
   #  rpcinfo -p acsls_hostname
rpcinfo: can't contact portmapper: RPC: Authentication error; why
= Failed (unspecified error)

Changes
New clustered servers with Solaris OS, Solaris Cluster,  ACSLS and ACSLS
HA  installed successfully.

Cause
rpcbind service was configured to have SMF property config/local_only set
to TRUE. (By, default, it should be set to FALSE.)  This SMF property is
used to allow or disallow access to rpcbind by remote clients.

Thus, a value of TRUE will disallow remote access.
Solution
1. Verify the RPC bind service's local_only  property setting:
 #  svccfg -s bind listprop | grep local
 config/local_only boolean true

2.  If set to TRUE, change the setting to FALSE; then, list the property
again to verify change:
 #  svccfg -s bind setprop config/local_only=false
 # svccfg -s bind listprop | grep local
 config/local_only boolean false

3.   Refresh the service to activate the new value:
 # svcadm refresh bind


-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of John
Meyers
Sent: Monday, October 03, 2011 3:48 PM
To: Rusty Major
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] ACSLS 8.0.2 and NBU 7.1(.0.2)

Just a data point for you.  We're still on ACSLS 7.3 under Solaris 10 and
have had zero issues going from 6.5.4 -> 7.0 -> 7.0.1 -> 7.1 -> 7.1.0.1.
The robot definitions were defined soley through the gui after the initial
7.0 upgrade and don't have anything specific to the robot in the vm.conf.

John

On 10/03/2011 02:03 PM, Rusty Major wrote:
> Hi All,
>
>
>
> Fresh install of NBU 7.1 with ACSLS 8.0.2, both on Solaris 10. I am
> unable to get NBU to communicate with ACSLS without forcing the port
> to communicate over in vm.conf (ACS_CSI_HOSTPORT). This works fine until
the ACSLS application is restarted and the port changes.
>
>
> I noticed with NBU version 7.1.0.0, MM and ACS daemons would not even
> start up, but when I patched to 7.1.0.2, all the appropriate daemons
> started, but there was still no communication with ACSLS without the
above mentioned vm.conf entry. ACSLS is configured with default settings.
>
>
>
> I have an ACSLS 8.0.2 server working with NBU version 6.5.x without
> any issues (same default ACSLS settings and no entries in VM.CONF).
>
>
>
> Has anyone run across this and have any pointers?
>
> Thanks,
>
> -Rusty
>
>
>
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS 8.0.2 and NBU 7.1(.0.2)

[John Meyers]

Just a data point for you.  We're still on ACSLS 7.3 under Solaris 10 and
have had zero issues going from 6.5.4 -> 7.0 -> 7.0.1 -> 7.1 -> 7.1.0.1.
The robot definitions were defined soley through the gui after the initial
7.0 upgrade and don't have anything specific to the robot in the vm.conf.

John

On 10/03/2011 02:03 PM, Rusty Major wrote:
> Hi All,
> 
>  
> 
> Fresh install of NBU 7.1 with ACSLS 8.0.2, both on Solaris 10. I am unable to 
> get NBU to communicate with ACSLS without forcing
> the port to communicate over in vm.conf (ACS_CSI_HOSTPORT). This works fine 
> until the ACSLS application is restarted and the port
> changes.
> 
> 
> I noticed with NBU version 7.1.0.0, MM and ACS daemons would not even start 
> up, but when I patched to 7.1.0.2, all the appropriate
> daemons started, but there was still no communication with ACSLS without the 
> above mentioned vm.conf entry. ACSLS is configured
> with default settings.
> 
>  
> 
> I have an ACSLS 8.0.2 server working with NBU version 6.5.x without any 
> issues (same default ACSLS settings and no entries in
> VM.CONF).
> 
>  
> 
> Has anyone run across this and have any pointers?
> 
> Thanks,
> 
> -Rusty
> 
> 
> 
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS script for removing scratch tapes from 8500 tape library

[Justin Piszcz]

On Tue, 8 Dec 2009, bolobaboo kabootar wrote:

> Hi
> I am planning to remove around 100s of scratch tapes from ACSLS. Does
> any body has command or script I can use to remove at ACSLS LEVEL ?
> THX
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>

Why don't you want to remove via netbackup?

Justin.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS ISSUE

[Kenneth Hansen]

Hi,

Please post, what where done to resolve the problem.

Thanks

Kenneth

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of harikrse
Sent: 14. oktober 2009 10:03
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: [Veritas-bu] ACSLS ISSUE


Hi All,

Thanks for your feedback, as mentioned:

I did a vary LSM  online but resulted in an error, hence i logged a 
call with SUN and the issue was resolved, the Engineer had collected the logs 
and will study to find out the reason for LSM offline.

+--
|This was sent by senthil.h...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS ISSUE

[Kenneth Hansen]

Hi, I've seen this problem before.
I have a customer that newly installed a new SL3000 and Acsls 7.3
Not sure if it's a bug, but problem did resolve itself by restarting acsls 
server.

I did check the
Q acs 0 online
Q lsm 0,0 offline
Q cap 0,0 online

Doing the var lsm 0,0 online did give me the exact same error.
Pr today I do not know if it's a SW or HW problem, but same problem in 
customers 2 SL3000.

Kenneth


-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of harikrse
Sent: 12. oktober 2009 10:05
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: [Veritas-bu] ACSLS ISSUE


Hi All,

Kindly provide me a solution for the below issue,

When i log in to my acsls server and check the logs it shows as 

Request: Transport Serial Number
Error: 0401 - General procedure error:  LSM is not ready
 
2009-10-11 21:07:24 DISMOUNT[0]:
546 N cl_log_lh_er.c 1  99
dm_lh_lsm_off: LH error type = LH_ERR_LSM_OFFLINE
 
Backups are not progressing and it is in queue for a long time. Hence how can 
we bring up the LSM

+--
|This was sent by senthil.h...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS ISSUE

[Marianne Van Den Berg]

Hopefully you've logged a call by now with your SUN/STK vendor...

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of harikrse
Sent: 12 October 2009 10:05
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: [Veritas-bu] ACSLS ISSUE


Hi All,

Kindly provide me a solution for the below issue,

When i log in to my acsls server and check the logs it shows as 

Request: Transport Serial Number
Error: 0401 - General procedure error:  LSM is not ready
 
2009-10-11 21:07:24 DISMOUNT[0]:
546 N cl_log_lh_er.c 1  99
dm_lh_lsm_off: LH error type = LH_ERR_LSM_OFFLINE
 
Backups are not progressing and it is in queue for a long time. Hence
how can we bring up the LSM

+--
|This was sent by senthil.h...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS ISSUE

[Michael Graff Andersen]

Hi

It has been some since I have worked with ACSLS, but have you tried to do a
vary LSM  online ?

If it gives an error you hopefully will have a better idea of what problem
is

Regards
Michael

2009/10/12 harikrse 

>
> Hi All,
>
> Kindly provide me a solution for the below issue,
>
> When i log in to my acsls server and check the logs it shows as
>
> Request: Transport Serial Number
> Error: 0401 - General procedure error:  LSM is not ready
>
> 2009-10-11 21:07:24 DISMOUNT[0]:
> 546 N cl_log_lh_er.c 1  99
> dm_lh_lsm_off: LH error type = LH_ERR_LSM_OFFLINE
>
> Backups are not progressing and it is in queue for a long time. Hence how
> can we bring up the LSM
>
> +--
> |This was sent by senthil.h...@gmail.com via Backup Central.
> |Forward SPAM to ab...@backupcentral.com.
> +--
>
>
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS ISSUE

[scott . george]

It appears that your solution may not be a software solution.  It would 
probably help if you gave us more information, like what kind of hardware 
is being driven by the ACSLS server?  Your hardware will differ on how it 
indicates hardware problems, but my first guess is that you have a robot 
down.





harikrse  
Sent by: veritas-bu-boun...@mailman.eng.auburn.edu
10/12/2009 04:04 AM
Please respond to
VERITAS-BU@MAILMAN.ENG.AUBURN.EDU


To
VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
cc

Subject
[Veritas-bu]  ACSLS ISSUE







Hi All,

Kindly provide me a solution for the below issue,

When i log in to my acsls server and check the logs it shows as 

Request: Transport Serial Number
Error: 0401 - General procedure error:  LSM is not ready
 
2009-10-11 21:07:24 DISMOUNT[0]:
546 N cl_log_lh_er.c 1  99
dm_lh_lsm_off: LH error type = LH_ERR_LSM_OFFLINE
 
Backups are not progressing and it is in queue for a long time. Hence how 
can we bring up the LSM

+--
|This was sent by senthil.h...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


PLEASE NOTE: The preceding information may be confidential or
privileged. It only should be used or disseminated for the purpose
of conducting business with Parker. If you are not an intended
recipient, please notify the sender by replying to this message and
then delete the information from your system. Thank you for your
cooperation.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS issue

[Marianne Van Den Berg]

Have a look at this:

http://www.mass.dk/index.php?option=com_content&view=article&id=48:netba
ckup-and-the-acsls-firewall-feature&catid=38:guides&Itemid=57


and this:

http://seer.entsupport.symantec.com/docs/306739.htm

Regards

M.

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of pfwhufc
Sent: 18 August 2009 18:47
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: [Veritas-bu] ACSLS issue


I have 2 servers that connect to an ACSLS server.
1 connects fine, but the other does not.
The 3 servers are all behind a firewall.

1 is solaris 8 with nbu 5.1, and 1 is solaris 10 with nbu 6.5.2. It is
the latter that has the issues.

New to acsls so not sure what to check etc 

Looking at the vm.conf, they do slightly differ.

What should I be checking for, and where - logs etc 

Many Thanks.

+--
|This was sent by peter.f...@produban.co.uk via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS issue

[Omar A Villa]

Here is a little not that I have about how to troubleshoot ACSLS, hope it can 
help.

Grab logs: # .//export/home/ACSSS/diag/bin/get_data.sh

1) Check the /var/adm/syslog/syslog.log for ACSD orAVRD errors.
2) View the acsssi event.log for failures (windows)
3) Look to see if /usr/openv/volmgr/vm.conf file has been changed (addition or 
deletion of ACS directives.)
4) Initiate a ping between the Media Server and ACS - Typically the problem is 
not that easy...
5) Run these commands and see if they return errors
rpcinfo {acsls_hostname} > /tmp/rpcinfo.acsls
rpcinfo -t {acsls_hostname} 30031 2 > /tmp/rpcinfo-t.2
rpcinfo -t {acsls_hostname} 30031 1 > /tmp/rpcinfo-t.1
See if this command returns information.
# rpcinfo
If no information is returned, this may mean that rpcbind is not running on 
that server.
Relevant NetBackup logs:
/usr/openv/volmgr/debug/daemon
/usr/openv/volmgr/debug/reqlib
/usr/openv/volmgr/debug/acsssi
Turn on 'csi' tracing on the ACSLS server.
Review these ACS logs.
/export/home/ACSSS/log/acsss_event.log
/export/home/ACSSS/log/acsss_trace.log


regards

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of pfwhufc
Sent: Tuesday, August 18, 2009 9:47 AM
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: [Veritas-bu] ACSLS issue


I have 2 servers that connect to an ACSLS server.
1 connects fine, but the other does not.
The 3 servers are all behind a firewall.

1 is solaris 8 with nbu 5.1, and 1 is solaris 10 with nbu 6.5.2. It is the 
latter that has the issues.

New to acsls so not sure what to check etc 

Looking at the vm.conf, they do slightly differ.

What should I be checking for, and where - logs etc 

Many Thanks.

+--
|This was sent by peter.f...@produban.co.uk via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS & Vault

[Howard Sherman]

CAP mode manual means that in order to enter tapes, you have to issue the ACSLS 
"enter  " command to put the CAP in unlocked mode so that you can enter 
tapes.
CAP mode automatic means you don't have to issue the ACSLS command, that the 
CAP at rest is unlocked. This setting is more convenient, but it means that any 
passer-by of the library can enter tapes, and may not sit well with an 
IT security audit.

To see what CAPs, i.e. CAP ids, are defined to your library, you can enter the 
ACSLS command, "q cap all".
The CAP id is a three digit, comma separated value: ACS,LSM,CAP
Some sample output:
ACSSA> q cap all
2009-07-22 10:31:07    CAP Status
 Identifier   Priority  Size  State    Mode   Status
   0, 1,0 0 39    online   automatic  available
   0, 1,1 0 39    offline  manual available
   1, 1,0 0 39    online   automatic  available
   1, 1,1 0 39    offline  manual available


For NetBackup Vault, one of a vault's attributes is "Media access port". This 
value is the CAP id. When a vault profile needs to eject tapes, it calls the 
ACSLS server via the acsssi interface, with the vault's configured capid, to 
perform the ejects.

With the CAP in enter mode, when you enter tapes into the CAP, the library's 
robot(s) automatically grab the tapes and put them in the library slots. It is 
after this that you are to run robotic inventory from NetBackup. So, this is 
why for ACS libraries, the "Empty access port" option is grey'ed out. 

Hope this helps.

Howard Sherman
City of New York, DoITT
Office phone 718-403-1957
hsher...@doitt.nyc.gov




From: Nathan Kippen 
To: veritas-bu@mailman.eng.auburn.edu
Sent: Monday, July 20, 2009 5:03:50 PM
Subject: [Veritas-bu] ACSLS & Vault


A couple of question for you ACSLS users:

1- Do I want the cap door mode automatic or manual?  (What is the difference)

2- I use the Vault option with Netbackup Enterprise.  How does the eject 
process work with ACSLS?

3- When I put tapes in the access port, I cannot click on 'Empty access 
port..." when trying to perform an inventory on the library.  Is the option 
suppose to be greyed out?

4- Any other useful informaiton you can think of that I should be aware of when 
using ACSLS with netbackup?  (perhaps something you found out that was helpful 
in the past).


TIA
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS & Vault

[ckstehman]

Hi

First you must be at Netbackup 6.5 or greater
2. We use automatic mode
3.  We use ACSLS and don't do anything special,, Netbackup sends commands 
to ACSLS via remote command to eject the tapes.
4. Once the eject command is executed, someone must open the door and 
physically remove the tape(s)
5. There is too much to tell in the response.  See if you can find a 
manual on it, via google, I did.

--
Carl Stehman
Distributed Services
Pepcoholdings, Inc.
701 Ninth St NW
Washington DC 20068
202-331-6619







Nathan Kippen  
Sent by: veritas-bu-boun...@mailman.eng.auburn.edu
07/20/2009 05:04 PM

To
veritas-bu@mailman.eng.auburn.edu
cc

Subject
[Veritas-bu] ACSLS & Vault






A couple of question for you ACSLS users:
 
1- Do I want the cap door mode automatic or manual?  (What is the 
difference)
 
2- I use the Vault option with Netbackup Enterprise.  How does the eject 
process work with ACSLS?
 
3- When I put tapes in the access port, I cannot click on 'Empty access 
port..." when trying to perform an inventory on the library.  Is the 
option suppose to be greyed out?
 
4- Any other useful informaiton you can think of that I should be aware of 
when using ACSLS with netbackup?  (perhaps something you found out that 
was helpful in the past).
 
 
TIA
 ___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


This Email message and any attachment may contain information that is
proprietary, legally privileged, confidential and/or subject to copyright
belonging to Pepco Holdings, Inc. or its affiliates ("PHI").  This Email is
intended solely for the use of the person(s) to which it is addressed.  If
you are not an intended recipient, or the employee or agent responsible for
delivery of this Email to the intended recipient(s), you are hereby notified
that any dissemination, distribution or copying of this Email is strictly
prohibited.  If you have received this message in error, please immediately
notify the sender and permanently delete this Email and any copies.  PHI
policies expressly prohibit employees from making defamatory or offensive
statements and infringing any copyright or any other legal right by Email
communication.  PHI will not accept any liability in respect of such
communications.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS & Vault

[Clooney, David]

Nathan

 

1.)You want the cap mode automatic as as I understand it once all
your volumes are in the cap or the cap is full it places in  cap in an
eject state, otherwise the cap has to manually be placed in an eject
state.

2.)Once the eject is initiated in the Vault, the job will wait for
all designated volumes to be pulled from the cap, if you have a cap of
capacity 20, and you have 30 tapes to vault eject, you will need to
remove the first 20 batch, close the cap and then  eject the remaining
10. Only once this is done will the vault job continue and complete.

3.)What library are you using and does NBU know you library has an
access port. One way to check would be to select any volume and eject it
and see whether it places it in the cap.

4.)There is quite a lot to ACSLS, depends how you plan on using it
i.e. are you going to share the library between mainframe and NBU for
instance, this would require setting up pools, volume attribute etc etc.

Regards

 

 

David Clooney

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nathan
Kippen
Sent: 20 July 2009 22:04
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] ACSLS & Vault

 

A couple of question for you ACSLS users:

 

1- Do I want the cap door mode automatic or manual?  (What is the
difference)

 

2- I use the Vault option with Netbackup Enterprise.  How does the eject
process work with ACSLS?

 

3- When I put tapes in the access port, I cannot click on 'Empty access
port..." when trying to perform an inventory on the library.  Is the
option suppose to be greyed out?

 

4- Any other useful informaiton you can think of that I should be aware
of when using ACSLS with netbackup?  (perhaps something you found out
that was helpful in the past).

 

 

TIA

 




Notice to recipient:
The information in this internet e-mail and any attachments is confidential and 
may be privileged. It is intended solely for the addressee. If you are not the 
intended addressee please notify the sender immediately by telephone. If you 
are not the intended recipient, any disclosure, copying, distribution or any 
action taken or omitted to be taken in reliance on it, is prohibited and may be 
unlawful.

When addressed to external clients any opinions or advice contained in this 
internet e-mail are subject to the terms and conditions expressed in any 
applicable governing terms of business or client engagement letter issued by 
the pertinent Bank of America group entity.

If this email originates from the U.K. please note that Bank of America, N.A., 
London Branch, Banc of America Securities Limited and MBNA Europe Bank Limited 
are authorised and regulated by the Financial Services Authority.  For all U.K. 
corporate disclosures, please refer to www.bankofamerica.com/ukcompanies
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS 7.1 to 7.2

[Bonnie Burkman]

I have upgraded ACSLS 7.1 and 7.0 and 6.1.1 to ACSLS 7.2 without any 
issues so far and I have been importing the previous database info as well.


There are a couple of things that need to be done before performing the 
upgrade and that is to run a complete volrpt for safety's sake to keep 
track of your current database of volumes.
Also perform the command dv_config -d > dynamicvarsCurrentdate to save 
off your current dynamic variable settings (i.e. settings for firewall, 
access control, vol stats, etc) and so you can compare them to the 
settings after the upgrade and import to verify previous settings get 
imported and if not you can go in and reset them.


Then you need to take down the software and run an export of the 
database to a file (as acsss user, db_export.sh -f 
/export/backup/dbexportCurrentdate). Then I bring down the database 
(db_command stop), exit acsss user, clean up shared memory (ipcs and 
then ipcrm -m #s under memory section, ipcrm -s #s under semaphore 
section, ipcrm -q #s under queue section).
I then last of all (for precaution's sake), backup the old acsls 
directories to a tar file (tar -tvf exportdirs.tar /export/home 
/export/backup) so you can also save off any files you have modified or 
placed in these directories as well.
Then do a pkgrm of the old (pkgrm STKacsls). Then I always check whether 
the old directories are still present and if they are, I remove them 
(i.e. rm -rf /export/home/ACSSS, rm -rf /export/home/ACSSA, rm -rf 
/export/home/informix, rm -rf /export/home/lib6, rm -rf 
/export/backup/server_to_server, rm -rf /export/backup/misc, rm -rf 
/export/backup/informix).
Make sure that the following 2 files are setup: /etc/cron.d/at.allow and 
/etc/cron.d/cron.allow with at least root, acsss, acsdb users. Install 
the new package (pkgadd STKacsls).
At this point  I have run into a small issue/error that comes up 
sometimes when you run the /export/home/ACSSS/install/install.sh script 
with it not being able to see the library or some such error message. 
This is because the file /export/home/ACSSS/data/internal/release.vars 
file does not have the ACSDBDIR variable set. If you edit this file and 
put the following info in for this variable, then it works - 
ACSDBDIR=/export/home/acsdb/ACSDB1.0 
Then run the /export/home/ACSSS/install/install.sh and install the 
PUT0702S patch and then any other PTF patches that apply to your 
environment for ACSLS 7.2.


Then I run the acsss_config option 8 to configure a vanilla database 
and then bring everything up vanilla to make sure it works in a vanilla 
format first.


At this point,  if everything works, shut it down completely, log out as 
acsss, clean up shared memory (ipcs, ipcrm -m #, ipcrm -s #, ipcrm  -q #).
Then log back in as acsss and run the import to import the previous 
database info: db_import.sh -f /export/backup/dbexportCurrentdate and 
select options 1,2, and 4.
If you have upgraded any of your library hardware, you will need to run 
the acsss_config again selecting option 8, but don't answer y to the 
second configure library hardware questions or this will wipe out your 
import.
Then if you have added any slots to the library and need an updated 
license, add it at this point.
Then I make sure the database is shutdown (db_command stop) and exit 
acsss user and again clean up the shared memory.
Then when I go back in as acsss I start things up with rc.acsss and I 
rarely have any issues. When I have, I reboot the entire system and 
usually things come up without any difficulty.
Once things are up fully, I double check on my dynamic variable settings 
with a dv_config -d > dynamicvarsCurrdate and compare this file with the 
previous one (diff usually works fine) and I run another volrpt and spot 
check things to verify everything is ok.
The cleaning up of the shared memory so many times is overkill usually, 
but when I don't do this, I have found that is when I have run into 
issues. So I tend to be more thorough and thus overkill.  Good luck!


*Bonnie L. Burkman*

PSD Architect 2

Sun Federal Professional Services

*Sun Microsystems Federal*

[EMAIL PROTECTED] 

Home Office Ph: 717-334-4755
Mobile: 717-487-6282
 

*CONFIDENTIALITY NOTICE - This document contains information that is 
proprietary, confidential or legally privileged. Any such information is 
intended only for use by the original recipient and may not be used or 
relied upon by a third party. Please do not disseminate this proposal 
without the permission of Sun Microsystems, Inc.*




Scott Jacobson wrote:

Has anyone upgraded their ACSLS 7.1 to 7.2?
 
Just curious if there were any issues with database migration from 
Informix to Postgres?
 
I didn't see anything on the topic at Backup Central.
 
The instructions from the StorageTek 7.2 ICAG look straight forward, 
but looks can be deceiving.
 
Any experiences, suggestions or guidelines would be appreciated.
 
Thanks,

Scott
---

Re: [Veritas-bu] ACSLS 7.1 to 7.2

[Schaefer, Harry]

One thing that I noticed historically speaking is that the cleaning tape
counts get reset to 0, so make note of those if you go this route...

Harry S.
Atlanta

 



From: Scott Jacobson [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 16, 2008 12:56 PM
To: Steve Hudson; Jack L Forester; nbu; Schaefer, Harry
Subject: RE: [Veritas-bu] ACSLS 7.1 to 7.2

 

Question, 

 

What about retaining information from your earlier 7.x environment.

 

Maybe I'm under the wrong assumption that a fair amount of historical
information would be lost if you didn't migrate?

 

Thanks,

Scott


>>> "Forester, Jack L" <[EMAIL PROTECTED]> 4/16/2008 10:11 AM >>>

We did the same thing.  We moved it to a new server.  Installed ACSLS
and audited the library.  No issues.

 

Jack L. Forester, Jr.
UNIX Systems Administrator, Stf
Lockheed Martin Information Technology
(304) 625-3946 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Schaefer, Harry
Sent: Tuesday, April 15, 2008 10:49 AM
To: Hudson, Steve; Scott Jacobson; nbu
Subject: Re: [Veritas-bu] ACSLS 7.1 to 7.2

 

We recently upgraded to ACSLS 7.2. It was very simple with no DB issues.
Of course we did not migrate the database. We did a fresh install and a
library audit populated the new database.

Harry S.
Atlanta



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hudson,
Steve
Sent: Monday, April 14, 2008 1:21 PM
To: Scott Jacobson; nbu
Subject: Re: [Veritas-bu] ACSLS 7.1 to 7.2

 

I will be doing this soon as well so I am also interested in real world
experiences.



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Jacobson
Sent: Monday, April 14, 2008 11:41 AM
To: nbu
Subject: [Veritas-bu] ACSLS 7.1 to 7.2

 

Has anyone upgraded their ACSLS 7.1 to 7.2?

 

Just curious if there were any issues with database migration from
Informix to Postgres?

 

I didn't see anything on the topic at Backup Central.

 

The instructions from the StorageTek 7.2 ICAG look straight forward, but
looks can be deceiving.

 

Any experiences, suggestions or guidelines would be appreciated.

 

Thanks,

Scott



The information contained in this email message and its attachments is
intended only for the private and confidential use of the recipient(s)
named above, unless the sender expressly agrees otherwise. Transmission
of email over the Internet is not a secure communications medium. If you
are requesting or have requested the transmittal of personal data, as
defined in applicable privacy laws by means of email or in an attachment
to email you must select a more secure alternate means of transmittal
that supports your obligations to protect such personal data. If the
reader of this message is not the intended recipient and/or you have
received this email in error, you must take no action based on the
information in this email and you are hereby notified that any
dissemination, misuse, copying, or disclosure of this communication is
strictly prohibited. If you have received this communication in error,
please notify us immediately by email and delete the original message. 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS 7.1 to 7.2

[Scott Jacobson]

Question, 
 
What about retaining information from your earlier 7.x environment.
 
Maybe I'm under the wrong assumption that a fair amount of historical
information would be lost if you didn't migrate?
 
Thanks,
Scott


>>> "Forester, Jack L" <[EMAIL PROTECTED]> 4/16/2008 10:11 AM
>>>

We did the same thing.  We moved it to a new server.  Installed ACSLS
and audited the library.  No issues.
 

Jack L. Forester, Jr.
UNIX Systems Administrator, Stf
Lockheed Martin Information Technology
(304) 625-3946


From:[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Schaefer, Harry
Sent: Tuesday, April 15, 2008 10:49 AM
To: Hudson, Steve; Scott Jacobson; nbu
Subject: Re: [Veritas-bu] ACSLS 7.1 to 7.2

 
We recently upgraded to ACSLS 7.2. It was very simple with no DB
issues. Of course we did not migrate the database. We did a fresh
install and a library audit populated the new database*
Harry S.
Atlanta


From:[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Hudson, Steve
Sent: Monday, April 14, 2008 1:21 PM
To: Scott Jacobson; nbu
Subject: Re: [Veritas-bu] ACSLS 7.1 to 7.2

 
I will be doing this soon as well so I am also interested in real world
experiences.


From:[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Jacobson
Sent: Monday, April 14, 2008 11:41 AM
To: nbu
Subject: [Veritas-bu] ACSLS 7.1 to 7.2

 

Has anyone upgraded their ACSLS 7.1 to 7.2?

 

Just curious if there were any issues with database migration from
Informix to Postgres?

 

I didn't see anything on the topic at Backup Central.

 

The instructions from the StorageTek 7.2 ICAG look straight forward,
but looks can be deceiving.

 

Any experiences, suggestions or guidelines would be appreciated.

 

Thanks,

Scott



The information contained in this email message and its attachments is
intended only for the private and confidential use of the recipient(s)
named above, unless the sender expressly agrees otherwise. Transmission
of email over the Internet is not a secure communications medium. If you
are requesting or have requested the transmittal of personal data, as
defined in applicable privacy laws by means of email or in an attachment
to email you must select a more secure alternate means of transmittal
that supports your obligations to protect such personal data. If the
reader of this message is not the intended recipient and/or you have
received this email in error, you must take no action based on the
information in this email and you are hereby notified that any
dissemination, misuse, copying, or disclosure of this communication is
strictly prohibited. If you have received this communication in error,
please notify us immediately by email and delete the original message. 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS 7.1 to 7.2

[Forester, Jack L]

We did the same thing.  We moved it to a new server.  Installed ACSLS
and audited the library.  No issues.

 

Jack L. Forester, Jr.
UNIX Systems Administrator, Stf
Lockheed Martin Information Technology
(304) 625-3946 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Schaefer, Harry
Sent: Tuesday, April 15, 2008 10:49 AM
To: Hudson, Steve; Scott Jacobson; nbu
Subject: Re: [Veritas-bu] ACSLS 7.1 to 7.2

 

We recently upgraded to ACSLS 7.2. It was very simple with no DB issues.
Of course we did not migrate the database. We did a fresh install and a
library audit populated the new database...

Harry S.
Atlanta



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hudson,
Steve
Sent: Monday, April 14, 2008 1:21 PM
To: Scott Jacobson; nbu
Subject: Re: [Veritas-bu] ACSLS 7.1 to 7.2

 

I will be doing this soon as well so I am also interested in real world
experiences.



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Jacobson
Sent: Monday, April 14, 2008 11:41 AM
To: nbu
Subject: [Veritas-bu] ACSLS 7.1 to 7.2

 

Has anyone upgraded their ACSLS 7.1 to 7.2?

 

Just curious if there were any issues with database migration from
Informix to Postgres?

 

I didn't see anything on the topic at Backup Central.

 

The instructions from the StorageTek 7.2 ICAG look straight forward, but
looks can be deceiving.

 

Any experiences, suggestions or guidelines would be appreciated.

 

Thanks,

Scott



The information contained in this email message and its attachments is
intended only for the private and confidential use of the recipient(s)
named above, unless the sender expressly agrees otherwise. Transmission
of email over the Internet is not a secure communications medium. If you
are requesting or have requested the transmittal of personal data, as
defined in applicable privacy laws by means of email or in an attachment
to email you must select a more secure alternate means of transmittal
that supports your obligations to protect such personal data. If the
reader of this message is not the intended recipient and/or you have
received this email in error, you must take no action based on the
information in this email and you are hereby notified that any
dissemination, misuse, copying, or disclosure of this communication is
strictly prohibited. If you have received this communication in error,
please notify us immediately by email and delete the original message. 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS 7.1 to 7.2

[Andrew White]

G'day,

I am also looking at upgrading to 7.2 on a few environments and would be
interested in how people go...

Cheers


> We recently upgraded to ACSLS 7.2. It was very simple with no DB issues.
> Of course we did not migrate the database. We did a fresh install and a
> library audit populated the new database...
>
> Harry S.
> Atlanta
>
> 
>
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Hudson,
> Steve
> Sent: Monday, April 14, 2008 1:21 PM
> To: Scott Jacobson; nbu
> Subject: Re: [Veritas-bu] ACSLS 7.1 to 7.2
>
>
>
> I will be doing this soon as well so I am also interested in real world
> experiences.
>
> 
>
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Scott
> Jacobson
> Sent: Monday, April 14, 2008 11:41 AM
> To: nbu
> Subject: [Veritas-bu] ACSLS 7.1 to 7.2
>
>
>
> Has anyone upgraded their ACSLS 7.1 to 7.2?
>
>
>
> Just curious if there were any issues with database migration from
> Informix to Postgres?
>
>
>
> I didn't see anything on the topic at Backup Central.
>
>
>
> The instructions from the StorageTek 7.2 ICAG look straight forward, but
> looks can be deceiving.
>
>
>
> Any experiences, suggestions or guidelines would be appreciated.
>
>
>
> Thanks,
>
> Scott
>
> 
>
> The information contained in this email message and its attachments is
> intended only for the private and confidential use of the recipient(s)
> named above, unless the sender expressly agrees otherwise. Transmission
> of email over the Internet is not a secure communications medium. If you
> are requesting or have requested the transmittal of personal data, as
> defined in applicable privacy laws by means of email or in an attachment
> to email you must select a more secure alternate means of transmittal
> that supports your obligations to protect such personal data. If the
> reader of this message is not the intended recipient and/or you have
> received this email in error, you must take no action based on the
> information in this email and you are hereby notified that any
> dissemination, misuse, copying, or disclosure of this communication is
> strictly prohibited. If you have received this communication in error,
> please notify us immediately by email and delete the original message.
>
>
>
> !DSPAM:4804c0d1135711403745939!
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
> !DSPAM:4804c0d1135711403745939!
>


-- 
http://systems-u.org
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS 7.1 to 7.2

[Schaefer, Harry]

We recently upgraded to ACSLS 7.2. It was very simple with no DB issues.
Of course we did not migrate the database. We did a fresh install and a
library audit populated the new database...

Harry S.
Atlanta



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hudson,
Steve
Sent: Monday, April 14, 2008 1:21 PM
To: Scott Jacobson; nbu
Subject: Re: [Veritas-bu] ACSLS 7.1 to 7.2

 

I will be doing this soon as well so I am also interested in real world
experiences.



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Jacobson
Sent: Monday, April 14, 2008 11:41 AM
To: nbu
Subject: [Veritas-bu] ACSLS 7.1 to 7.2

 

Has anyone upgraded their ACSLS 7.1 to 7.2?

 

Just curious if there were any issues with database migration from
Informix to Postgres?

 

I didn't see anything on the topic at Backup Central.

 

The instructions from the StorageTek 7.2 ICAG look straight forward, but
looks can be deceiving.

 

Any experiences, suggestions or guidelines would be appreciated.

 

Thanks,

Scott



The information contained in this email message and its attachments is
intended only for the private and confidential use of the recipient(s)
named above, unless the sender expressly agrees otherwise. Transmission
of email over the Internet is not a secure communications medium. If you
are requesting or have requested the transmittal of personal data, as
defined in applicable privacy laws by means of email or in an attachment
to email you must select a more secure alternate means of transmittal
that supports your obligations to protect such personal data. If the
reader of this message is not the intended recipient and/or you have
received this email in error, you must take no action based on the
information in this email and you are hereby notified that any
dissemination, misuse, copying, or disclosure of this communication is
strictly prohibited. If you have received this communication in error,
please notify us immediately by email and delete the original message. 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS 7.1 to 7.2

[Hudson, Steve]

I will be doing this soon as well so I am also interested in real world
experiences.



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Jacobson
Sent: Monday, April 14, 2008 11:41 AM
To: nbu
Subject: [Veritas-bu] ACSLS 7.1 to 7.2

 

Has anyone upgraded their ACSLS 7.1 to 7.2?

 

Just curious if there were any issues with database migration from
Informix to Postgres?

 

I didn't see anything on the topic at Backup Central.

 

The instructions from the StorageTek 7.2 ICAG look straight forward, but
looks can be deceiving.

 

Any experiences, suggestions or guidelines would be appreciated.

 

Thanks,

Scott



The information contained in this email message and its attachments
is intended
only for the private and confidential use of the recipient(s) named
above, unless the sender expressly agrees otherwise. Transmission
of email over the Internet
 is not a secure communications medium. If you are requesting or
have requested
the transmittal of personal data, as defined in applicable privacy
laws by means
 of email or in an attachment to email you must select a more
secure alternate means of transmittal that supports your
obligations to protect such personal data. If the reader of this
message is not the intended recipient and/or you have received this
email in error, you must take no action based on the information in
this email and you are hereby notified that any dissemination,
misuse, copying, or disclosure of this communication is strictly
prohibited. If you have received
this communication in error, please notify us immediately by email
and delete the original message.___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS and Netbackup Enterprise Vault Management

[Hall, Christian N.]

Do you have file called /usr/opv/volmgr/misc/EJECT.txt ?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, March 03, 2008 12:19 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] ACSLS and Netbackup Enterprise Vault Management


We just incorporated a new STK 8500 in our Netbackup environment.  We
have
an AIX 5.3  master running Netbackup 6.0 MP4.  After completing the
nights
backups we use Vault Management with Netbackup to duplicate our data and
send tapes off-site.  As part of the 8500 we just implemented an 7.2
ACSLS
server - STK installed and configured.

Here's the problem.
Once vault runs and all data is duplicated, the tapes fail to eject into
the 8500 cap.  Netbackup vault jobs says " Ejecting 2 tapes and creating
reports", however netbackup just sits.

Things I changed or checked.
Within the vault session/profile I added the new 8500 cap ports, pointed
to
the new robot.
Added MAP_ID to the vm.conf file.
I can go into media in Netbackup and manually eject a tape into the 8500
cap.
No errors in the netbackup vault sessions log file.
No errors in the ACSLS log files.
Set 8500 cap to both manual and automatic and tested - same result.
Opened a sev-1 with netbackup.

Any ideas?





-
"PLEASE NOTE: The preceding information may be confidential or
privileged. It only should be used or disseminated for the purpose
of conducting business with Parker. If you are not an intended
recipient, please notify the sender by replying to this message and
then delete the information from your system. Thank you for your
cooperation."
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS Robot Question

[Major, Rusty]

Justin,
Have you checked to see if there is a running enter command? (query request)
I had this happen before, but I think it was due to running enter when the cap 
was in auto mode, so it really messed the library up. I think I had to down ACS 
and the database and then kill the enter request that was running and flip the 
mode of the cap to manual and back to auto to get it to work again. But this 
was on an SL8500, I'm not sure what kind of library you have. 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz
Sent: Wednesday, September 19, 2007 11:31 AM
To: Paul Keating
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] ACSLS Robot Question

Checked, not running anywhere.

This is a peculiar issue, Sun/STK has escalated the issue to backline support, 
they cannot figure it out yet either.

On Wed, 19 Sep 2007, Paul Keating wrote:

> Then it's a robotic issue.

Check your robotic control hosts to see if someone left robtest running?

-- 


> -Original Message-
> From: Justin Piszcz [mailto:[EMAIL PROTECTED]
> Sent: September 19, 2007 12:26 PM
> To: Paul Keating
> Cc: veritas-bu@mailman.eng.auburn.edu
> Subject: RE: [Veritas-bu] ACSLS Robot Question
> 
> 
> Yes, the cap is in automatic mode.
> 
> Justin.
> 
> On Wed, 19 Sep 2007, Paul Keating wrote:
> 
> > Is your lib configured to auto-empty?
> 
> That should a configuration option on the lib.
> 
> --


La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so.



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans 
délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de 
votre
ordinateur toute copie du courriel reçu.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS Robot Question

[Justin Piszcz]

Found the problem, the cap was out of sync with ACSLS, fixed and now it 
works.


Justin.

On Wed, 19 Sep 2007, Justin Piszcz wrote:


Checked, not running anywhere.

This is a peculiar issue, Sun/STK has escalated the issue to backline 
support, they cannot figure it out yet either.


On Wed, 19 Sep 2007, Paul Keating wrote:


Then it's a robotic issue.


Check your robotic control hosts to see if someone left robtest running?

--



-Original Message-
From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: September 19, 
2007 12:26 PM

To: Paul Keating
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] ACSLS Robot Question


Yes, the cap is in automatic mode.

Justin.

On Wed, 19 Sep 2007, Paul Keating wrote:

> Is your lib configured to auto-empty?

That should a configuration option on the lib.

--



La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the 
Bank of
Canada does not waive any related rights. Any distribution, use, or copying 
of this

email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it 
immediately from

your system and notify the sender promptly by email that you have done so.



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par 
une
personne autre que le ou les destinataires désignés est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans 
délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de 
votre

ordinateur toute copie du courriel reçu.___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS Robot Question

[Major, Rusty]

In ACSLS do a qu cap all

Identifier   Priority  Size  StateMode   Status
   0, 1,0 0 39online   automatic  available

If it shows up as automatic, then it should be pulling the tapes in each time. 
If it's set to manual, you have to do an enter from acsls. 

Change it to automatic by doing set cap mode automatic (cap identifier).

-Rusty

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating
Sent: Wednesday, September 19, 2007 11:25 AM
To: Justin Piszcz; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] ACSLS Robot Question

Is your lib configured to auto-empty?

That should a configuration option on the lib.

-- 


> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Justin 
> Piszcz
> Sent: September 19, 2007 12:22 PM
> To: veritas-bu@mailman.eng.auburn.edu
> Subject: [Veritas-bu] ACSLS Robot Question
> 
> 
> When inserting tapes into an ACSLS robot, the robot is not sucking the 
> tapes into the robot, when I select the cap using SLConsole, I can see 
> the tapes I put into the cap, but they sit there, any idea why they 
> are not being sucked into the library?
> 
> Justin.


La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the Bank 
of Canada does not waive any related rights. Any distribution, use, or copying 
of this email or the information it contains by other than the intended 
recipient is unauthorized. If you received this email in error please delete it 
immediately from your system and notify the sender promptly by email that you 
have done so. 



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il 
contient par une personne autre que le ou les destinataires désignés est 
interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer 
immédiatement et envoyer sans délai à l'expéditeur un message électronique pour 
l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS Robot Question

[Justin Piszcz]

On Wed, 19 Sep 2007, MacKinnon, Gregory (G.R.) wrote:

>
>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf
>> Of Justin Piszcz
>> Sent: Wednesday, September 19, 2007 12:22 PM
>> To: veritas-bu@mailman.eng.auburn.edu
>> Subject: [Veritas-bu] ACSLS Robot Question
>>
>> When inserting tapes into an ACSLS robot, the robot is not sucking the
>> tapes into the robot, when I select the cap using SLConsole, I
>> can see the
>> tapes I put into the cap, but they sit there, any idea why
>> they are not
>> being sucked into the library?
Nope.

>>
>> Justin.
>> ___
>> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>
>
> You wouldn't have tapes with the same bar code
> already in the robot, would you?
>
>
> Gregg
>
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS Robot Question

[MacKinnon, Gregory \(G.R.\)]

 

>-Original Message-
>From: [EMAIL PROTECTED] 
>[mailto:[EMAIL PROTECTED] On Behalf 
>Of Justin Piszcz
>Sent: Wednesday, September 19, 2007 12:22 PM
>To: veritas-bu@mailman.eng.auburn.edu
>Subject: [Veritas-bu] ACSLS Robot Question
>
>When inserting tapes into an ACSLS robot, the robot is not sucking the 
>tapes into the robot, when I select the cap using SLConsole, I 
>can see the 
>tapes I put into the cap, but they sit there, any idea why 
>they are not 
>being sucked into the library?
>
>Justin.
>___
>Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>

You wouldn't have tapes with the same bar code
already in the robot, would you?


Gregg

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS Robot Question

[Justin Piszcz]

Checked, not running anywhere.

This is a peculiar issue, Sun/STK has escalated the issue to backline 
support, they cannot figure it out yet either.


On Wed, 19 Sep 2007, Paul Keating wrote:


Then it's a robotic issue.


Check your robotic control hosts to see if someone left robtest running?

--



-Original Message-
From: Justin Piszcz [mailto:[EMAIL PROTECTED] 
Sent: September 19, 2007 12:26 PM

To: Paul Keating
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] ACSLS Robot Question


Yes, the cap is in automatic mode.

Justin.

On Wed, 19 Sep 2007, Paul Keating wrote:

> Is your lib configured to auto-empty?

That should a configuration option on the lib.

--



La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so.



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans 
délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de 
votre
ordinateur toute copie du courriel reçu.___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS Robot Question

[Paul Keating]

Then it's a robotic issue.

Check your robotic control hosts to see if someone left robtest running?

-- 


> -Original Message-
> From: Justin Piszcz [mailto:[EMAIL PROTECTED] 
> Sent: September 19, 2007 12:26 PM
> To: Paul Keating
> Cc: veritas-bu@mailman.eng.auburn.edu
> Subject: RE: [Veritas-bu] ACSLS Robot Question
> 
> 
> Yes, the cap is in automatic mode.
> 
> Justin.
> 
> On Wed, 19 Sep 2007, Paul Keating wrote:
> 
> > Is your lib configured to auto-empty?
> 
> That should a configuration option on the lib.
> 
> -- 


La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so. 



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans 
délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de 
votre
ordinateur toute copie du courriel reçu.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS Robot Question

[Paul Keating]

Is your lib configured to auto-empty?

That should a configuration option on the lib.

-- 


> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf 
> Of Justin Piszcz
> Sent: September 19, 2007 12:22 PM
> To: veritas-bu@mailman.eng.auburn.edu
> Subject: [Veritas-bu] ACSLS Robot Question
> 
> 
> When inserting tapes into an ACSLS robot, the robot is not 
> sucking the 
> tapes into the robot, when I select the cap using SLConsole, 
> I can see the 
> tapes I put into the cap, but they sit there, any idea why 
> they are not 
> being sucked into the library?
> 
> Justin.


La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so. 



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans 
délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de 
votre
ordinateur toute copie du courriel reçu.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS Robot Question

[Justin Piszcz]

Yes, the cap is in automatic mode.

Justin.

On Wed, 19 Sep 2007, Paul Keating wrote:


Is your lib configured to auto-empty?


That should a configuration option on the lib.

--



-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf 
Of Justin Piszcz

Sent: September 19, 2007 12:22 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] ACSLS Robot Question


When inserting tapes into an ACSLS robot, the robot is not 
sucking the 
tapes into the robot, when I select the cap using SLConsole, 
I can see the 
tapes I put into the cap, but they sit there, any idea why 
they are not 
being sucked into the library?


Justin.



La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so.



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans 
délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de 
votre
ordinateur toute copie du courriel reçu.___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS+SL8500 Issues Remain..

[Martin Ruslan]

LOL
Sorry, don't check the date.. :">
I'm just look from Wesley who replied you also on 31 Aug.. :P

Regards,
mTz


On 9/2/07, Justin Piszcz <[EMAIL PROTECTED]> wrote:
>
> This is from 2006, did you just reply?  I got everything working now.
>
> On Sun, 2 Sep 2007, Martin Ruslan wrote:
>
> > Justin,
> > the ACSLS has a few patches.. not only the firmware on the library, can
> you
> > ask that to your STK support guy?
> >
> > Regards,
> > mTz
> >
> >
> > On 12/19/06, Justin Piszcz <[EMAIL PROTECTED]> wrote:
> >>
> >>> ACS_TCP_RPCSERVICE
> >>> ACS_SSI_SOCKET = media_server.your.domain.com 13741
> >>
> >> These items are set.
> >>
> >>> ACSSA> display drive *,*,*,* -f type serial_num
> >>> 2006-12-18 10:45:59 Display Drive
> >>> Acs Lsm Panel Drive Type Serial_num
> >>> 0 0 1 0 HP-LTO-2 HUM9X00200
> >> Again, when I do the backups one media server at a time, there are no
> >> issues.  It is only when there is a *burst* of jobs, the SN's match the
> >> corresponding addresses for the drives.
> >>
> >>> 1. Tail the acsss_event.log (good for viewing results for the below
> >> suggestio$
> >> Yeah we get that LH_DRIVE_BUSY error.
> >>
> >> We're still investigating.
> >>
> >> Justin.
> >>
> >> On Mon, 18 Dec 2006, Scott Jacobson wrote:
> >>
> >>>
> >>> Justin,
> >>> For my benefit as well, a review from all the suggestions.
> >>> 1.Make sure vm.conf has specific entries:
> >>> ACS_TCP_RPCSERVICE
> >>> ACS_SSI_HOSTNAME = media_server.your.domain.com
> >>> ACS_SSI_SOCKET = media_server.your.domain.com 13741
> >>> ENABLE_AUTO_PATH_CORRECTION (optional)
> >>> 2. From cmd_proc use:
> >>> ACSSA> display drive *,*,*,* -f type serial_num
> >>> 2006-12-18 10:45:59 Display Drive
> >>> Acs Lsm Panel Drive Type Serial_num
> >>> 0 0 1 0 HP-LTO-2 HUM9X00200
> >>> and make sure the serial numbers, acs, lsm, panel and drive number
> match
> >> up with what is displayed under devices/hosts on the master server.
> >>> And though this is painful, I would again try:
> >>> 1. Tail the acsss_event.log (good for viewing results for the below
> >> suggestions)
> >>> 2. From ACSSA use the mount command to move a tape into each drive and
> >> verify it lands in the correct acs, lsm, panel and drive by using
> *query
> >> drive all* and look for the vol ser.
> >>> 3. From the Veritas device (Master/Media server) controlling the
> drives,
> >> use robtest to again move a tape into each drive and verify it lands in
> the
> >> correct acs, lsm, panel and drive, then look under Device Monitor and
> locate
> >> the vol ser that is mounted and select Drive Details. Make sure the
> acs,
> >> lsm, panel and drive from Veritas matches the acs, lsm, panel and drive
> from
> >> *query drive all*.
> >>> If they don't match, 1) you may have a zoning problem or 2) you've
> >> possibly configured your drives incorrectly with Veritas.
> >>> If that isn't it, I'll anxiously be awaiting to hear what Veritas
> finds.
> >>> Scott
> >>>
> >>>
> >> Justin Piszcz <[EMAIL PROTECTED]> 12/18/2006 9:58 AM >>>
> >>> Still not resolved, working with Veritas/STK on this.
> >>>
> >>> On Mon, 18 Dec 2006, Hall, Christian N. wrote:
> >>>
>  Justin,
> 
>  Did you get this resolved with Veritas tech support? What was the
>  outcome?
> 
>  -Original Message-
>  From: [EMAIL PROTECTED]
>  [mailto:[EMAIL PROTECTED] On Behalf Of
> Justin
>  Piszcz
>  Sent: Monday, December 11, 2006 10:25 AM
>  To: Veritas-bu@mailman.eng.auburn.edu
>  Subject: [Veritas-bu] ACSLS+SL8500 Issues Remain..
> 
>  Hi all,
> 
>  I tried everyone's suggestions thus far, have not had any luck
> though:
> 
>  1) tried using TCP communication on all the media servers instead of
> >> UDP
>  2) tried increasing the media unmount delay from 120 seconds to 600
>  seconds, 10 minutes
> 
>  And the problem remains/persists, I kick off 45 jobs and NetBackup
> >> shows
>  32 active jobs.  However 1/2 or 3 (random) jobs will hang saying
>  'Mounting MediaID' - I can check ACSLS and run query drive *, the
> tape
>  it is requesting sometimes is and is not in the drive that it is
>  supposed to be in, confusing... For firmware, what is the
> >> current/latest
>  firmware and for those who have SL8500s without any issues, what
>  firmware are you running?
> 
>  Justin.
> 
>  ___
>  Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
>  http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
> >>> ___
> >>> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> >>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >>>
> >> ___
> >> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> >> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >>
> >
>
___
Ver

Re: [Veritas-bu] ACSLS+SL8500 Issues Remain..

[Justin Piszcz]

This is from 2006, did you just reply?  I got everything working now.

On Sun, 2 Sep 2007, Martin Ruslan wrote:

> Justin,
> the ACSLS has a few patches.. not only the firmware on the library, can you
> ask that to your STK support guy?
>
> Regards,
> mTz
>
>
> On 12/19/06, Justin Piszcz <[EMAIL PROTECTED]> wrote:
>>
>>> ACS_TCP_RPCSERVICE
>>> ACS_SSI_SOCKET = media_server.your.domain.com 13741
>>
>> These items are set.
>>
>>> ACSSA> display drive *,*,*,* -f type serial_num
>>> 2006-12-18 10:45:59 Display Drive
>>> Acs Lsm Panel Drive Type Serial_num
>>> 0 0 1 0 HP-LTO-2 HUM9X00200
>> Again, when I do the backups one media server at a time, there are no
>> issues.  It is only when there is a *burst* of jobs, the SN's match the
>> corresponding addresses for the drives.
>>
>>> 1. Tail the acsss_event.log (good for viewing results for the below
>> suggestio$
>> Yeah we get that LH_DRIVE_BUSY error.
>>
>> We're still investigating.
>>
>> Justin.
>>
>> On Mon, 18 Dec 2006, Scott Jacobson wrote:
>>
>>>
>>> Justin,
>>> For my benefit as well, a review from all the suggestions.
>>> 1.Make sure vm.conf has specific entries:
>>> ACS_TCP_RPCSERVICE
>>> ACS_SSI_HOSTNAME = media_server.your.domain.com
>>> ACS_SSI_SOCKET = media_server.your.domain.com 13741
>>> ENABLE_AUTO_PATH_CORRECTION (optional)
>>> 2. From cmd_proc use:
>>> ACSSA> display drive *,*,*,* -f type serial_num
>>> 2006-12-18 10:45:59 Display Drive
>>> Acs Lsm Panel Drive Type Serial_num
>>> 0 0 1 0 HP-LTO-2 HUM9X00200
>>> and make sure the serial numbers, acs, lsm, panel and drive number match
>> up with what is displayed under devices/hosts on the master server.
>>> And though this is painful, I would again try:
>>> 1. Tail the acsss_event.log (good for viewing results for the below
>> suggestions)
>>> 2. From ACSSA use the mount command to move a tape into each drive and
>> verify it lands in the correct acs, lsm, panel and drive by using *query
>> drive all* and look for the vol ser.
>>> 3. From the Veritas device (Master/Media server) controlling the drives,
>> use robtest to again move a tape into each drive and verify it lands in the
>> correct acs, lsm, panel and drive, then look under Device Monitor and locate
>> the vol ser that is mounted and select Drive Details. Make sure the acs,
>> lsm, panel and drive from Veritas matches the acs, lsm, panel and drive from
>> *query drive all*.
>>> If they don't match, 1) you may have a zoning problem or 2) you've
>> possibly configured your drives incorrectly with Veritas.
>>> If that isn't it, I'll anxiously be awaiting to hear what Veritas finds.
>>> Scott
>>>
>>>
>> Justin Piszcz <[EMAIL PROTECTED]> 12/18/2006 9:58 AM >>>
>>> Still not resolved, working with Veritas/STK on this.
>>>
>>> On Mon, 18 Dec 2006, Hall, Christian N. wrote:
>>>
 Justin,

 Did you get this resolved with Veritas tech support? What was the
 outcome?

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Justin
 Piszcz
 Sent: Monday, December 11, 2006 10:25 AM
 To: Veritas-bu@mailman.eng.auburn.edu
 Subject: [Veritas-bu] ACSLS+SL8500 Issues Remain..

 Hi all,

 I tried everyone's suggestions thus far, have not had any luck though:

 1) tried using TCP communication on all the media servers instead of
>> UDP
 2) tried increasing the media unmount delay from 120 seconds to 600
 seconds, 10 minutes

 And the problem remains/persists, I kick off 45 jobs and NetBackup
>> shows
 32 active jobs.  However 1/2 or 3 (random) jobs will hang saying
 'Mounting MediaID' - I can check ACSLS and run query drive *, the tape
 it is requesting sometimes is and is not in the drive that it is
 supposed to be in, confusing... For firmware, what is the
>> current/latest
 firmware and for those who have SL8500s without any issues, what
 firmware are you running?

 Justin.

 ___
 Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
 http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

>>> ___
>>> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
>>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>>
>> ___
>> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>
>
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS+SL8500 Issues Remain..

[Martin Ruslan]

Justin,
the ACSLS has a few patches.. not only the firmware on the library, can you
ask that to your STK support guy?

Regards,
mTz


On 12/19/06, Justin Piszcz <[EMAIL PROTECTED]> wrote:
>
> > ACS_TCP_RPCSERVICE
> > ACS_SSI_SOCKET = media_server.your.domain.com 13741
>
> These items are set.
>
> > ACSSA> display drive *,*,*,* -f type serial_num
> > 2006-12-18 10:45:59 Display Drive
> > Acs Lsm Panel Drive Type Serial_num
> > 0 0 1 0 HP-LTO-2 HUM9X00200
> Again, when I do the backups one media server at a time, there are no
> issues.  It is only when there is a *burst* of jobs, the SN's match the
> corresponding addresses for the drives.
>
> > 1. Tail the acsss_event.log (good for viewing results for the below
> suggestio$
> Yeah we get that LH_DRIVE_BUSY error.
>
> We're still investigating.
>
> Justin.
>
> On Mon, 18 Dec 2006, Scott Jacobson wrote:
>
> >
> > Justin,
> > For my benefit as well, a review from all the suggestions.
> > 1.Make sure vm.conf has specific entries:
> > ACS_TCP_RPCSERVICE
> > ACS_SSI_HOSTNAME = media_server.your.domain.com
> > ACS_SSI_SOCKET = media_server.your.domain.com 13741
> > ENABLE_AUTO_PATH_CORRECTION (optional)
> > 2. From cmd_proc use:
> > ACSSA> display drive *,*,*,* -f type serial_num
> > 2006-12-18 10:45:59 Display Drive
> > Acs Lsm Panel Drive Type Serial_num
> > 0 0 1 0 HP-LTO-2 HUM9X00200
> > and make sure the serial numbers, acs, lsm, panel and drive number match
> up with what is displayed under devices/hosts on the master server.
> > And though this is painful, I would again try:
> > 1. Tail the acsss_event.log (good for viewing results for the below
> suggestions)
> > 2. From ACSSA use the mount command to move a tape into each drive and
> verify it lands in the correct acs, lsm, panel and drive by using *query
> drive all* and look for the vol ser.
> > 3. From the Veritas device (Master/Media server) controlling the drives,
> use robtest to again move a tape into each drive and verify it lands in the
> correct acs, lsm, panel and drive, then look under Device Monitor and locate
> the vol ser that is mounted and select Drive Details. Make sure the acs,
> lsm, panel and drive from Veritas matches the acs, lsm, panel and drive from
> *query drive all*.
> > If they don't match, 1) you may have a zoning problem or 2) you've
> possibly configured your drives incorrectly with Veritas.
> > If that isn't it, I'll anxiously be awaiting to hear what Veritas finds.
> > Scott
> >
> >
> > >>> Justin Piszcz <[EMAIL PROTECTED]> 12/18/2006 9:58 AM >>>
> > Still not resolved, working with Veritas/STK on this.
> >
> > On Mon, 18 Dec 2006, Hall, Christian N. wrote:
> >
> > > Justin,
> > >
> > > Did you get this resolved with Veritas tech support? What was the
> > > outcome?
> > >
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] On Behalf Of Justin
> > > Piszcz
> > > Sent: Monday, December 11, 2006 10:25 AM
> > > To: Veritas-bu@mailman.eng.auburn.edu
> > > Subject: [Veritas-bu] ACSLS+SL8500 Issues Remain..
> > >
> > > Hi all,
> > >
> > > I tried everyone's suggestions thus far, have not had any luck though:
> > >
> > > 1) tried using TCP communication on all the media servers instead of
> UDP
> > > 2) tried increasing the media unmount delay from 120 seconds to 600
> > > seconds, 10 minutes
> > >
> > > And the problem remains/persists, I kick off 45 jobs and NetBackup
> shows
> > > 32 active jobs.  However 1/2 or 3 (random) jobs will hang saying
> > > 'Mounting MediaID' - I can check ACSLS and run query drive *, the tape
> > > it is requesting sometimes is and is not in the drive that it is
> > > supposed to be in, confusing... For firmware, what is the
> current/latest
> > > firmware and for those who have SL8500s without any issues, what
> > > firmware are you running?
> > >
> > > Justin.
> > >
> > > ___
> > > Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> > >
> > ___
> > Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS+SL8500 Issues Remain..

[Justin Piszcz]

> ACS_TCP_RPCSERVICE
> ACS_SSI_SOCKET = media_server.your.domain.com 13741

These items are set.

> ACSSA> display drive *,*,*,* -f type serial_num
> 2006-12-18 10:45:59 Display Drive  
> Acs Lsm Panel Drive Type Serial_num
> 0 0 1 0 HP-LTO-2 HUM9X00200
Again, when I do the backups one media server at a time, there are no 
issues.  It is only when there is a *burst* of jobs, the SN's match the 
corresponding addresses for the drives.

> 1. Tail the acsss_event.log (good for viewing results for the below suggestio$
Yeah we get that LH_DRIVE_BUSY error.

We're still investigating.

Justin.

On Mon, 18 Dec 2006, Scott Jacobson wrote:

> 
> Justin,
> For my benefit as well, a review from all the suggestions.
> 1.Make sure vm.conf has specific entries:
> ACS_TCP_RPCSERVICE
> ACS_SSI_HOSTNAME = media_server.your.domain.com
> ACS_SSI_SOCKET = media_server.your.domain.com 13741
> ENABLE_AUTO_PATH_CORRECTION (optional)
> 2. From cmd_proc use:
> ACSSA> display drive *,*,*,* -f type serial_num
> 2006-12-18 10:45:59 Display Drive
> Acs Lsm Panel Drive Type Serial_num
> 0 0 1 0 HP-LTO-2 HUM9X00200
> and make sure the serial numbers, acs, lsm, panel and drive number match up 
> with what is displayed under devices/hosts on the master server.
> And though this is painful, I would again try:
> 1. Tail the acsss_event.log (good for viewing results for the below 
> suggestions)
> 2. From ACSSA use the mount command to move a tape into each drive and verify 
> it lands in the correct acs, lsm, panel and drive by using *query drive all* 
> and look for the vol ser.
> 3. From the Veritas device (Master/Media server) controlling the drives, use 
> robtest to again move a tape into each drive and verify it lands in the 
> correct acs, lsm, panel and drive, then look under Device Monitor and locate 
> the vol ser that is mounted and select Drive Details. Make sure the acs, lsm, 
> panel and drive from Veritas matches the acs, lsm, panel and drive from 
> *query drive all*.
> If they don't match, 1) you may have a zoning problem or 2) you've possibly 
> configured your drives incorrectly with Veritas.
> If that isn't it, I'll anxiously be awaiting to hear what Veritas finds.
> Scott
>  
> 
> >>> Justin Piszcz <[EMAIL PROTECTED]> 12/18/2006 9:58 AM >>>
> Still not resolved, working with Veritas/STK on this.
> 
> On Mon, 18 Dec 2006, Hall, Christian N. wrote:
> 
> > Justin, 
> > 
> > Did you get this resolved with Veritas tech support? What was the
> > outcome?   
> > 
> > -Original Message-
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] On Behalf Of Justin
> > Piszcz
> > Sent: Monday, December 11, 2006 10:25 AM
> > To: Veritas-bu@mailman.eng.auburn.edu 
> > Subject: [Veritas-bu] ACSLS+SL8500 Issues Remain..
> > 
> > Hi all,
> > 
> > I tried everyone's suggestions thus far, have not had any luck though:
> > 
> > 1) tried using TCP communication on all the media servers instead of UDP
> > 2) tried increasing the media unmount delay from 120 seconds to 600
> > seconds, 10 minutes
> > 
> > And the problem remains/persists, I kick off 45 jobs and NetBackup shows
> > 32 active jobs.  However 1/2 or 3 (random) jobs will hang saying
> > 'Mounting MediaID' - I can check ACSLS and run query drive *, the tape
> > it is requesting sometimes is and is not in the drive that it is
> > supposed to be in, confusing... For firmware, what is the current/latest
> > firmware and for those who have SL8500s without any issues, what
> > firmware are you running?
> > 
> > Justin.
> > 
> > ___
> > Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu 
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu 
> > 
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu 
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS+SL8500 Issues Remain..

[Scott Jacobson]

Justin,
For my benefit as well, a review from all the suggestions.
1.Make sure vm.conf has specific entries:
ACS_TCP_RPCSERVICE
ACS_SSI_HOSTNAME = media_server.your.domain.com
ACS_SSI_SOCKET = media_server.your.domain.com 13741
ENABLE_AUTO_PATH_CORRECTION (optional)
2. From cmd_proc use:
ACSSA> display drive *,*,*,* -f type serial_num
2006-12-18 10:45:59 Display Drive
Acs Lsm Panel Drive Type Serial_num
0 0 1 0 HP-LTO-2 HUM9X00200
and make sure the serial numbers, acs, lsm, panel and drive number match up 
with what is displayed under devices/hosts on the master server.
And though this is painful, I would again try:
1. Tail the acsss_event.log (good for viewing results for the below suggestions)
2. From ACSSA use the mount command to move a tape into each drive and verify 
it lands in the correct acs, lsm, panel and drive by using *query drive all* 
and look for the vol ser.
3. From the Veritas device (Master/Media server) controlling the drives, use 
robtest to again move a tape into each drive and verify it lands in the correct 
acs, lsm, panel and drive, then look under Device Monitor and locate the vol 
ser that is mounted and select Drive Details. Make sure the acs, lsm, panel and 
drive from Veritas matches the acs, lsm, panel and drive from *query drive all*.
If they don't match, 1) you may have a zoning problem or 2) you've possibly 
configured your drives incorrectly with Veritas.
If that isn't it, I'll anxiously be awaiting to hear what Veritas finds.
Scott
 

>>> Justin Piszcz <[EMAIL PROTECTED]> 12/18/2006 9:58 AM >>>
Still not resolved, working with Veritas/STK on this.

On Mon, 18 Dec 2006, Hall, Christian N. wrote:

> Justin, 
> 
> Did you get this resolved with Veritas tech support? What was the
> outcome?   
> 
> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Justin
> Piszcz
> Sent: Monday, December 11, 2006 10:25 AM
> To: Veritas-bu@mailman.eng.auburn.edu 
> Subject: [Veritas-bu] ACSLS+SL8500 Issues Remain..
> 
> Hi all,
> 
> I tried everyone's suggestions thus far, have not had any luck though:
> 
> 1) tried using TCP communication on all the media servers instead of UDP
> 2) tried increasing the media unmount delay from 120 seconds to 600
> seconds, 10 minutes
> 
> And the problem remains/persists, I kick off 45 jobs and NetBackup shows
> 32 active jobs.  However 1/2 or 3 (random) jobs will hang saying
> 'Mounting MediaID' - I can check ACSLS and run query drive *, the tape
> it is requesting sometimes is and is not in the drive that it is
> supposed to be in, confusing... For firmware, what is the current/latest
> firmware and for those who have SL8500s without any issues, what
> firmware are you running?
> 
> Justin.
> 
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu 
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu 
> 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS+SL8500 Issues Remain..

[Justin Piszcz]

Still not resolved, working with Veritas/STK on this.

On Mon, 18 Dec 2006, Hall, Christian N. wrote:

> Justin, 
> 
> Did you get this resolved with Veritas tech support? What was the
> outcome?   
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Justin
> Piszcz
> Sent: Monday, December 11, 2006 10:25 AM
> To: Veritas-bu@mailman.eng.auburn.edu
> Subject: [Veritas-bu] ACSLS+SL8500 Issues Remain..
> 
> Hi all,
> 
> I tried everyone's suggestions thus far, have not had any luck though:
> 
> 1) tried using TCP communication on all the media servers instead of UDP
> 2) tried increasing the media unmount delay from 120 seconds to 600
> seconds, 10 minutes
> 
> And the problem remains/persists, I kick off 45 jobs and NetBackup shows
> 32 active jobs.  However 1/2 or 3 (random) jobs will hang saying
> 'Mounting MediaID' - I can check ACSLS and run query drive *, the tape
> it is requesting sometimes is and is not in the drive that it is
> supposed to be in, confusing... For firmware, what is the current/latest
> firmware and for those who have SL8500s without any issues, what
> firmware are you running?
> 
> Justin.
> 
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS+SL8500 Issues Remain..

[Hall, Christian N.]

Justin, 

Did you get this resolved with Veritas tech support? What was the
outcome?   

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Justin
Piszcz
Sent: Monday, December 11, 2006 10:25 AM
To: Veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] ACSLS+SL8500 Issues Remain..

Hi all,

I tried everyone's suggestions thus far, have not had any luck though:

1) tried using TCP communication on all the media servers instead of UDP
2) tried increasing the media unmount delay from 120 seconds to 600
seconds, 10 minutes

And the problem remains/persists, I kick off 45 jobs and NetBackup shows
32 active jobs.  However 1/2 or 3 (random) jobs will hang saying
'Mounting MediaID' - I can check ACSLS and run query drive *, the tape
it is requesting sometimes is and is not in the drive that it is
supposed to be in, confusing... For firmware, what is the current/latest
firmware and for those who have SL8500s without any issues, what
firmware are you running?

Justin.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS and 2 fiber networks

[Paul Keating]

Gotchadifferent ball of wax.
 
Ok, then what was the question? Oh yes 
;o)
 
okwell, assuming you have the library "partitioned" and when you say
the master anhd existing media servers see "all FC drives" in the robot,
then you mean in the particular partition, then we can treat this
"partition" as a single robot without ACSLS.
 
any drives you add for the new media servers can be added in several
ways.in one way, you create a brand new "robot" in ACSLS for the new
drives, but that would be my second choicein that case, the new
partition would include a robot and the two new drives, and the new
media servers would see that, and whatever, but I'm not going to get too
much into that, as I don't think it's the best solution.
 
Add your two new drives, add them to the existing partition for which
the master controls the robotzone the new drives to be seen only by
the new media servers, and configure the master as the robot control
host, and you're done.
 
there's no reason the master or existing media servers need to be zoned
to see the new drives, unless you intend for those servers to share the
drives via SSO. The only servers that should be zoned to the drives are
the servers that will write to the drives.
 
Paul
 
 
-- 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob
Stump
Sent: December 15, 2006 3:33 PM
To: Paul Keating; Curtis Preston;
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] ACSLS and 2 fiber networks


The ACSLS already exists as the library is shared between the
NetBackup environment and the MainFrame backup solution. Unfortunately
the true "partiioning" of the library for SL8500 is not available until
next year. Right now only the slots can be divide up.



La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so. 



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans 
délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de 
votre
ordinateur toute copie du courriel reçu.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS and 2 fiber networks

[Bob Stump]

The ACSLS already exists as the library is shared between the NetBackup 
environment and the MainFrame backup solution. Unfortunately the true 
"partiioning" of the library for SL8500 is not available until next year. Right 
now only the slots can be divide up.

>>> "Curtis Preston" <[EMAIL PROTECTED]> 12/15/2006 2:40 PM >>>

I agree with your ACSLS comment.  I try to NOT use it whenever I can.  If I 
have a choice of two configurations to buy, and one uses it and the other 
doesn't, I'll buy the one that doesn't in a heartbeat.  If you don't need what 
it offers (multi-host sharing of a library using apps that don't share), then 
it only adds complexity.  And if you have that requirement, other library 
manufacturers meet that requirement without adding the level of complexity and 
cost that ACSLS brings to the table.  (They just partition their library and 
make it look like more than one library.)

That having been said, there are a number of STK libraries that require ACSLS 
to control them, such as the 8500.  (Although I hear that they're coming out 
with a non-ACSLS version soon.)

---
W. Curtis Preston
Author of O'Reilly's Backup & Recovery and Using SANs and NAS
VP Data Protection
GlassHouse Technologies


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating
Sent: Friday, December 15, 2006 10:47 AM
To: Bob Stump; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] ACSLS and 2 fiber networks

 
 
Absolutely.
 
matter of fact, first thing I'd do would be to take ACSLS out of the picture, 
let the master control the robot, configure all of your media servers to use 
the master as the robotic control device and make your whole env. MUCH simpler.
 
Paul
-- 
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Stump
Sent: December 15, 2006 1:24 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] ACSLS and 2 fiber networks
In an ACSLS environment where you have a single instance of a library
1. The master server is zoned to see all the existing fiber tape drives in the 
library
2. Several media servers are also zoned to see all the existing fiber tape 
drives in the library
3. the master server is configured to be the main scan host.
4. ACSLS server controling the library (duh...of coarse)


Is it possible to create a "NEW" fiber environment to run independantly but 
with the same master as thus:
1. add 2 new tape drives into the currently ACS controlled library 
2. DO NOT zone them to the master (you can't as it is on the old FABRIC)
3. add 4 new media servers on the fiber and zone them to the two new tapes 
drives
4. run SSO in this "NEW" fiber for only the 4 new media servers

I am almost convinced this should work since robotic control is done by ACSLS, 
but. I am still not certain because the master server can not see the new 
tape drives.


La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so. 



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans 
délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de 
votre
ordinateur toute copie du courriel reçu.


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS and 2 fiber networks

[Fielden, Joshua]

> That having been said, there are a number of STK libraries that
require ACSLS to control them, such as 
> the 8500.  (Although I hear that they're coming out with a non-ACSLS
version soon.)

The non-ACSLS version shows the 4 bots (or bot pairs) as individual
robots to the master server, according to what I've heard.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS and 2 fiber networks

[Curtis Preston]

I agree with your ACSLS comment.  I try to NOT use it whenever I can.  If I 
have a choice of two configurations to buy, and one uses it and the other 
doesn't, I'll buy the one that doesn't in a heartbeat.  If you don't need what 
it offers (multi-host sharing of a library using apps that don't share), then 
it only adds complexity.  And if you have that requirement, other library 
manufacturers meet that requirement without adding the level of complexity and 
cost that ACSLS brings to the table.  (They just partition their library and 
make it look like more than one library.)

That having been said, there are a number of STK libraries that require ACSLS 
to control them, such as the 8500.  (Although I hear that they're coming out 
with a non-ACSLS version soon.)

---
W. Curtis Preston
Author of O'Reilly's Backup & Recovery and Using SANs and NAS
VP Data Protection
GlassHouse Technologies


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating
Sent: Friday, December 15, 2006 10:47 AM
To: Bob Stump; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] ACSLS and 2 fiber networks

 
 
Absolutely.
 
matter of fact, first thing I'd do would be to take ACSLS out of the picture, 
let the master control the robot, configure all of your media servers to use 
the master as the robotic control device and make your whole env. MUCH simpler.
 
Paul
-- 
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Stump
Sent: December 15, 2006 1:24 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] ACSLS and 2 fiber networks
In an ACSLS environment where you have a single instance of a library
1. The master server is zoned to see all the existing fiber tape drives in the 
library
2. Several media servers are also zoned to see all the existing fiber tape 
drives in the library
3. the master server is configured to be the main scan host.
4. ACSLS server controling the library (duh...of coarse)


Is it possible to create a "NEW" fiber environment to run independantly but 
with the same master as thus:
1. add 2 new tape drives into the currently ACS controlled library 
2. DO NOT zone them to the master (you can't as it is on the old FABRIC)
3. add 4 new media servers on the fiber and zone them to the two new tapes 
drives
4. run SSO in this "NEW" fiber for only the 4 new media servers

I am almost convinced this should work since robotic control is done by ACSLS, 
but. I am still not certain because the master server can not see the new 
tape drives.


La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so. 



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans 
délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de 
votre
ordinateur toute copie du courriel reçu.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS and 2 fiber networks

[Paul Keating]

 
 
Absolutely.
 
matter of fact, first thing I'd do would be to take ACSLS out of the
picture, let the master control the robot, configure all of your media
servers to use the master as the robotic control device and make your
whole env. MUCH simpler.
 
Paul
-- 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob
Stump
Sent: December 15, 2006 1:24 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] ACSLS and 2 fiber networks


In an ACSLS environment where you have a single instance of a
library
1. The master server is zoned to see all the existing fiber tape
drives in the library
2. Several media servers are also zoned to see all the existing
fiber tape drives in the library
3. the master server is configured to be the main scan host.
4. ACSLS server controling the library (duh...of coarse)


Is it possible to create a "NEW" fiber environment to run
independantly but with the same master as thus:
1. add 2 new tape drives into the currently ACS controlled
library 
2. DO NOT zone them to the master (you can't as it is on the old
FABRIC)
3. add 4 new media servers on the fiber and zone them to the two
new tapes drives
4. run SSO in this "NEW" fiber for only the 4 new media servers

I am almost convinced this should work since robotic control is
done by ACSLS, 
but. I am still not certain because the master server can
not see the new tape drives.



La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so. 



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans 
délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de 
votre
ordinateur toute copie du courriel reçu.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS+SL8500 Issues Remain..

[Justin Piszcz]

Yeah, currently working with Symantec as I write this e-mail.

On Mon, 11 Dec 2006, Hampus Lind wrote:

> Hi,
> 
> I have to go down to the bunker and check what firmware we are on.. I
> probably have this for you tomorrow afternoon.
> 
> You didn't have any errors in acsss_event.log on the ACSLS server? I think
> it's in the /log directory.
> 
> Also, have you been close to the library when this problem occurs? What is
> happening with the arms and elevators? Any strange sounds?
> 
> Have you tried Symantec support?
> 
> I will get back to you tomorrow with firmware...
> 
> 
> Hampus Lind
> Rikspolisstyrelsen
> National Police Board
> Tel dir: +46 (0)8 - 401 99 43
> Tel mob: +46 (0)70 - 217 92 66
> E-mail: [EMAIL PROTECTED]
> 
> 
> -Ursprungligt meddelande-
> Från: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] För Justin Piszcz
> Skickat: den 11 december 2006 16:25
> Till: Veritas-bu@mailman.eng.auburn.edu
> Ämne: [Veritas-bu] ACSLS+SL8500 Issues Remain..
> 
> Hi all,
> 
> I tried everyone's suggestions thus far, have not had any luck though:
> 
> 1) tried using TCP communication on all the media servers instead of UDP
> 2) tried increasing the media unmount delay from 120 seconds to 600 
> seconds, 10 minutes
> 
> And the problem remains/persists, I kick off 45 jobs and NetBackup shows 
> 32 active jobs.  However 1/2 or 3 (random) jobs will hang saying 'Mounting 
> MediaID' - I can check ACSLS and run query drive *, the tape it is 
> requesting sometimes is and is not in the drive that it is supposed to be 
> in, confusing... For firmware, what is the current/latest firmware and for 
> those who have SL8500s without any issues, what firmware are you running?
> 
> Justin.
> 
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> ___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS Question

[Justin Piszcz]

Yeah, thanks and yes I had to define the library on each media server 
host, almost all is working well now, thanks.

Justin.

On Fri, 24 Nov 2006, Dean wrote:

> Justin,
> 
> You don't need SSO to share the ACSLS library. One of the media servers
> should be the robotic control host, just like with a normal SCSI library.
> 
> I think you'll need to define the library on each media server, but specifiy
> your first media server as the control host.
> 
> You'll need SSO if you want to dynamically share the drives inside the
> library between media servers.
> 
> 
> On 11/24/06, Justin Piszcz <[EMAIL PROTECTED]> wrote:
> >
> > If I have > 1 media server in a robot controlled by ACSLS, do I need SSO
> > in order to use it?
> >
> > I want to add multiple tape drives spread across multiple media servers in
> > an ACSLS robot, but only the first media server has control over the
> > robot?  Unless I add multiple robots, one for each of the drives attached
> > to each media server?
> >
> > ___
> > Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >
> 
> 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] ACSLS Question

[Dean]

Justin,

You don't need SSO to share the ACSLS library. One of the media servers
should be the robotic control host, just like with a normal SCSI library.

I think you'll need to define the library on each media server, but specifiy
your first media server as the control host.

You'll need SSO if you want to dynamically share the drives inside the
library between media servers.


On 11/24/06, Justin Piszcz <[EMAIL PROTECTED]> wrote:


If I have > 1 media server in a robot controlled by ACSLS, do I need SSO
in order to use it?

I want to add multiple tape drives spread across multiple media servers in
an ACSLS robot, but only the first media server has control over the
robot?  Unless I add multiple robots, one for each of the drives attached
to each media server?

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

RE: [Veritas-bu] ACSLS

[Barber, Layne \(Contractor\)]

Title: ACSLS



http://jumpdoc.fz-juelich.de/doc_pdf/stk_acsls/ACSLS_611_Quick_Ref.pdf[Layne 
Barber]  

From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Yosifovski, 
TammySent: Tuesday, April 11, 2006 08:50To: 
veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] 
ACSLS

Anyone have a ACSLS PDF (command or installation 
guide) they can pass along?  Version 6.1.1 or later. 
Thanks so much!! 
Tammy Yosifovski 


  
  
-This e-mail is the exclusive, private and confidential property of the sender. Theinformation contained in it is intended solely for the use of the sender and theintended recipient. If you are not the intended recipient you are hereby advised thatany unauthorized disclosure, copying, distribution or the taking of any action inreliance on the contents of this message is strictly prohibited. If you have receivedthis e-mail in error, please notify us immediately by telephone (call the Technical Support Center at 1-888-873-8721) and then destroy this document and any copies in any form immediately. Finally, the recipient should check this email and any attachments for the presence of viruses.  Sender accepts no liability for any damage caused by any virus transmitted by this email.-