- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- How to remove shadowset member to be used as backu...
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
тАО01-27-2005 09:05 PM
тАО01-27-2005 09:05 PM
Re: How to remove shadowset member to be used as backup
That's a good point, because it reduces the risks. In fact we do have a structure like you described and I think I am gonna use it.
Ian,
I did not forget, did not have time yet.
Regards,
Cor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-30-2005 12:42 PM
тАО01-30-2005 12:42 PM
Re: How to remove shadowset member to be used as backup
(and everyone else)
HOLD ON! This is not a good plan. The fundamental purpose of shadowing is to protect you from bad blocks. As soon as you reduce a shadowset to less than TWO members you are actually DOUBLING your exposure to bad blocks.
Remember shadowing is NOT a tool for making backups easy, it's NOT a tool for making I/O faster. You paid the big bucks for shadowing licenses to eliminate bad blocks. So, to use it in a way that *increases* your exposure makes no sense.
A simple rule to follow... don't ever reduce a shadowset to less than TWO members.
In this case, take a spare disk, add it to the shadowset and let it copy, then remove the newest disk as your backup.
As long as you're on V7.3 or higher, and there are no open files on the disk, a member dismounted from a shadowset will be in a consistent state.
As of V7.3-2, if you really can't find a 3rd member, then you can minimise your exposure to bad blocks by forcing a full merge on the shadowset:
$ SET SHADOW/DEMAND_MERGE DSA1
Note that this doesn't *eliminate* the risk, but it makes sure that all existing bad blocks are detected and corrected.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2005 01:55 AM
тАО01-31-2005 01:55 AM
Re: How to remove shadowset member to be used as backup
I agree with you about one of the purposes of using shadow sets being bad blocks. However the primary purpose that they have served in my experience is redundancy. The probability of having more than a single drive failure in a shadowset is much much lower than that for a single drive. This makes it very unlikely that the users would ever be subjected to a loss of access to the drive due to single drive failures. The primary risk for any period of time where the shadowset is reduced to 1 member is that any failure of that drive will result in loss of access and possible loss of data that has not been backed up.
I agree completely with the preferability of adding in a 3rd member to copy the disk rather than reducing the shadowset to 1 member if it is going to be a prolonged situation. As always, these risk management decisions involve tradeoffs: time, money, exposure to loss, efficiency, etc....
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2005 04:31 AM
тАО01-31-2005 04:31 AM
Re: How to remove shadowset member to be used as backup
thanks for pointing out the thing I completely overlooked, and which others may therefore overlook as well, although from the other side.
In _MY_ perspective, I did not even think in reducing to single member. We reduce 3-member sets to 2-member.
At the current prices of diskdrives, any single issue is sooooo much more expensive, in repair time alone already, and if you factor in the production hours lost...
We are on record of requesting the 3 member limit to be expanded. We would much prefer to have 2 members at each site, plus the availability to ADD the backup member, instead of having to take it out!
Proost.
Have one on me.
Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2005 10:40 AM
тАО01-31-2005 10:40 AM
Re: How to remove shadowset member to be used as backup
One more important point. You need to know that your application has a consistent database on the the shadowsets. Either a way to hold or force outstanding I/O or shut down. A "flying dismount" may lead to problems with data consistency. The shadowing manual has many cautions about ensuring data consistancy when dismounting a shadow set member, mostly saying "you should know your application and take appropriate steps."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2005 06:54 AM
тАО02-01-2005 06:54 AM
Re: How to remove shadowset member to be used as backup
>The primary risk for any period of time >where the shadowset is reduced to 1 member >is that any failure of that drive will >result in loss of access and possible loss >of data that has not been backed up.
No so!
At any time there is a small, but finite probability that any individual block on a disk will go bad. We won't know it's bad until we read it. With very large numbers of blocks, even very small probabilities start to turn into certainties. In any case the probability of ANY block on the disk going bad within a specific time period is many orders of magnitude higher than that of the whole disk failing.
So we need to accept bad blocks WILL happen, guaranteed! However, provided the corresponding block on all other shadow members doesn't also go bad before we read the bad block, shadowing will be able to repair the damage from known, good data. (note that bad blocks behave like Schrodinger's cat in the classic physics thought experiment).
A shadow set with two members may have a number of bad blocks on one member, and a (hopefully different) set on the other member. As long as those sets don't intersect, then we don't care - they effectively don't exist. But, if we break the set, we've exposed all the bad blocks on both members.
Before minicopy, breaking the set was the equivalent of doubling the probability of exposure to bad blocks because a latent bad block on the surviving member would be realised when it was read, and the ones on the removed member would be propagated to the backup and realised when it was restored.
Mini copy helps a lot, because we might get the shadow set back together before reading one of the bad blocks, so our exposure is reduced to the set of blocks read while the shadow set is reduced.
Forcing a merge before breaking the set will make sure every block on every member is read, thereby finding any bad blocks and fixing them from a good member.
Even with mini copy, reducing a shadow set to a single member represents an easily avoided risk, especially considering the low cost of storage.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2005 08:19 AM
тАО02-01-2005 08:19 AM
Re: How to remove shadowset member to be used as backup
Lawrence
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2005 01:56 PM
тАО02-01-2005 01:56 PM
Re: How to remove shadowset member to be used as backup
do a similar task given that it reads all blocks on all
members and compares them? Obviously it won't do any
writing, which a merge will do.
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2005 08:35 PM
тАО02-01-2005 08:35 PM
Re: How to remove shadowset member to be used as backup
Purely Personal Opinion
- « Previous
-
- 1
- 2
- Next »