- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- What's best practice backing up DR Groups in EVA B...
Disk Enclosures
1754193
Members
4388
Online
108811
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
тАО06-13-2007 01:34 AM
тАО06-13-2007 01:34 AM
What's best practice backing up DR Groups in EVA BC/CA environment?
ENVIRONMENT:
We have (2) EVA8000 running BC/CA. Both have EVA Command View Suite v6.0.2 for XCS v6.0.
Hosts are HPUX servers running 11i v1 running MC/Serviceguard v11.16 with Metrocluster for EVA v1.0. The hosts are configured using MC/Serviceguard/Metro Cluster disk configuration uses DR Groups.
ISSUE:
Though Mirrorclones are obviously best choice, unfortunately I can't use Mirrorclones because they are not allowed with DR Groups. Don't know why either. I can only use containers/snapclones/snapshots.
BTW....Just in case HP is listening....HP NEEDS TO SUPPORT MIRRORCLONES IN DR GROUPS! THIS IS A MUST HAVE!
QUESTION:
What's best practice to backup my DR Groups using CONTAINERS/SNAPCLONES/SNAPSHOTS etc? I intend to automate the process using RSM or SSSU. Any help is most appreciated!
We have (2) EVA8000 running BC/CA. Both have EVA Command View Suite v6.0.2 for XCS v6.0.
Hosts are HPUX servers running 11i v1 running MC/Serviceguard v11.16 with Metrocluster for EVA v1.0. The hosts are configured using MC/Serviceguard/Metro Cluster disk configuration uses DR Groups.
ISSUE:
Though Mirrorclones are obviously best choice, unfortunately I can't use Mirrorclones because they are not allowed with DR Groups. Don't know why either. I can only use containers/snapclones/snapshots.
BTW....Just in case HP is listening....HP NEEDS TO SUPPORT MIRRORCLONES IN DR GROUPS! THIS IS A MUST HAVE!
QUESTION:
What's best practice to backup my DR Groups using CONTAINERS/SNAPCLONES/SNAPSHOTS etc? I intend to automate the process using RSM or SSSU. Any help is most appreciated!
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-13-2007 02:46 AM
тАО06-13-2007 02:46 AM
Re: What's best practice backing up DR Groups in EVA BC/CA environment?
>>> Though Mirrorclones are obviously best choice
I'm not sure about this, if you only will use for backup, demand allocated snapshots seems to fully fit your needs.
>>> What's best practice to backup my DR Groups using CONTAINERS/SNAPCLONES/SNAPSHOTS etc?
I think that there is not too much change if where out of DR Groups.
First, you should make data consistent to take the snapshot, that is, put database in backup mode or shutdown the db, freeze applications, etc.
You can take a snapshot of the source or destination vdisk if you use sync replication. If you use async replication, your snapshots should be done at the source storage.
After snapshot complete, resume I/O to your LUNs.
Probably, your best option is to use RSM because it can handle errors and send notifications. This is hard to do with SSSU.
I'm not sure about this, if you only will use for backup, demand allocated snapshots seems to fully fit your needs.
>>> What's best practice to backup my DR Groups using CONTAINERS/SNAPCLONES/SNAPSHOTS etc?
I think that there is not too much change if where out of DR Groups.
First, you should make data consistent to take the snapshot, that is, put database in backup mode or shutdown the db, freeze applications, etc.
You can take a snapshot of the source or destination vdisk if you use sync replication. If you use async replication, your snapshots should be done at the source storage.
After snapshot complete, resume I/O to your LUNs.
Probably, your best option is to use RSM because it can handle errors and send notifications. This is hard to do with SSSU.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-14-2007 02:02 AM
тАО06-14-2007 02:02 AM
Re: What's best practice backing up DR Groups in EVA BC/CA environment?
Ivan,
Mirrorclones seem obvious to me becuase my luns are big, and would come in handy when snapping them each day because they only update delta changes made since last snap ( typically 24 hours).
What I've read so far, and sounds like your recommeding it, is to suspend my DR Group links while taking snapshot. That's doesn't sound appealing since I have and HA enviornment, and can't failover with consistent data if my links are suspended. Agree?
I agree with RSM recommendations. Tending lean towards that solution.
Thanks for your input.
Brad
Mirrorclones seem obvious to me becuase my luns are big, and would come in handy when snapping them each day because they only update delta changes made since last snap ( typically 24 hours).
What I've read so far, and sounds like your recommeding it, is to suspend my DR Group links while taking snapshot. That's doesn't sound appealing since I have and HA enviornment, and can't failover with consistent data if my links are suspended. Agree?
I agree with RSM recommendations. Tending lean towards that solution.
Thanks for your input.
Brad
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