- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: MSL4048 & Backup Exec: Media Removal Problems
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2009 02:06 PM
тАО05-06-2009 02:06 PM
MSL4048 & Backup Exec: Media Removal Problems
We have a persistent issue with the following setup:
- MSL4048 LTO4 FC, latest firmware
- 4/12 SAN Switch, lastest FOS
- 3x BL460c, Windows 2008, latest firmware/drivers
- 1x BL460c, Windows 2003, latest firmware/drivers
- Veritas Backup Exec 12
We can't open the magazines, BE says that the library is locked. We've already tried:
- Disable library locking (registry) http://support.veritas.com/docs/319285
In one of our tests, the library was isolated and connected only to the W2K3 hosts, in this test we disabled the "Removable Storage" service and everything ran just fine.
We tried to shutdown this Removable Storage service in Windows 2008, (net stop "removable storage") but OS reports that the service does not exist (?).
We want to be able to remove the magazines without shutting down the MSL nor running LT&T to disable the locking.
Thanks in advance for any insight,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2009 11:15 PM
тАО05-06-2009 11:15 PM
Re: MSL4048 & Backup Exec: Media Removal Problems
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2009 11:48 PM
тАО05-06-2009 11:48 PM
Re: MSL4048 & Backup Exec: Media Removal Problems
In the BE 12 Devices tab , right click on the msl device drive and unlock . then from the fromt panel from the msl tape libraray unlock the magazzine using the key pads.. This will solve the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 07:59 AM
тАО05-11-2009 07:59 AM
Re: MSL4048 & Backup Exec: Media Removal Problems
This issue has been solved, our resident BE expert nailed it. In the Windows 2008 servers She:
1. modified the account permissions for the account running the BE services, assigning the following user rights: log on as batch, act as part of the O.S., log on as a service, create token, back up files, restore files, manage auditing.
2. disabled IPv6 and entered the localhost entries in the hosts file
127.0.0.1 localhost
127.0.0.1 localhost.localdomain
I know it's strange, but after these changes the unlock job ran flawlessly,
Thanks all for your help,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 08:17 AM
тАО05-11-2009 08:17 AM