- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: MSL2024
StoreEver Tape Storage
1748282
Members
4025
Online
108761
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО01-10-2008 03:53 PM
тАО01-10-2008 03:53 PM
Re: MSL2024
Network Storage Router thats if you are using Fibre
One drink away from sleeping on the pavement
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2008 09:49 AM
тАО01-11-2008 09:49 AM
Re: MSL2024
Your reseller forgot to tell you one critical point.
The configuration you use works great and is fully supported by HP -- If your ISV software supports that mode --.
This model typically requires backup software where there is a single master server and multiple media agents can be installed on different servers. The media agents all send mount/dismount requests back to the master server.
I don't know enough about BE to say whether it supports this mode but it certainly won't work as two different installations.
The configuration you use works great and is fully supported by HP -- If your ISV software supports that mode --.
This model typically requires backup software where there is a single master server and multiple media agents can be installed on different servers. The media agents all send mount/dismount requests back to the master server.
I don't know enough about BE to say whether it supports this mode but it certainly won't work as two different installations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2008 10:49 AM
тАО02-12-2008 10:49 AM
Re: MSL2024
I can tell you that Backup Exec dosen't support that kind of configuration. I think what your reseller meant was that you can backup data from 2 servers at the same time. This would be done through the backup jobs.
Here's what I would do:
With 2 drives, you need a LEO (Library Extension Option) license for the second drive. BE won't be able to use the second drive until you have this installed. Once that is installed you need to create 2 seperate backup jobs. For simplicity I'm assuming that you have your RAWS pushed out to the clients.
OK, this is simple.
Job 1 backs up to Drive 1. and Job 2 backs up to drive 2.
You select which job goes to which drive based on your data storage needs.
In this config, you don't have to set partitioning on the library and both servers get backed up to seperate drives.
There is no way to connect the second drive to a seperate server and have the library know about it since both drives are controlled by the library and not the servers you are trying to connect them to. Only one server can be connected to the library. I would suggest that you connect the library to a dedicated backup server and run the jobs seperately to each drive.
You could go one step further and partition the library (without a mail slot) so that each half of the library is only used for the specific job.
i.e. Job 1 - Drive 1 - Partition 1.
Rinse and repete with job 2.
It may not be the right combo for you. you are the one that is going to have to figure that out!
Good Luck and let us know what you came up with!
Here's what I would do:
With 2 drives, you need a LEO (Library Extension Option) license for the second drive. BE won't be able to use the second drive until you have this installed. Once that is installed you need to create 2 seperate backup jobs. For simplicity I'm assuming that you have your RAWS pushed out to the clients.
OK, this is simple.
Job 1 backs up to Drive 1. and Job 2 backs up to drive 2.
You select which job goes to which drive based on your data storage needs.
In this config, you don't have to set partitioning on the library and both servers get backed up to seperate drives.
There is no way to connect the second drive to a seperate server and have the library know about it since both drives are controlled by the library and not the servers you are trying to connect them to. Only one server can be connected to the library. I would suggest that you connect the library to a dedicated backup server and run the jobs seperately to each drive.
You could go one step further and partition the library (without a mail slot) so that each half of the library is only used for the specific job.
i.e. Job 1 - Drive 1 - Partition 1.
Rinse and repete with job 2.
It may not be the right combo for you. you are the one that is going to have to figure that out!
Good Luck and let us know what you came up with!
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP