- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Data Protector and removed Shadow Set members ...
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
тАО02-13-2008 11:38 AM
тАО02-13-2008 11:38 AM
Data Protector and removed Shadow Set members - Catch 22
Just getting started setting up backups using DP (v5.5) and my new Alphas. My plan is to dismount one of the three members in a Shadow Set, have Data Protector back it up and then add the member back into the Set. I thought it would be "simple" to have a DP pre-exec command procedure mount the removed member at the start of the backup. Turns out, a seperate VMS DP process does the pre-exec procedure (mounts the drive) and exits (dismounting the drive as it leaves!) The subsequent DP process which will do the backup finds the device "not ready" and fails.
So then the catch-22 is, the removed shadow set member has the same volume name as it's original shadow set and the drive can't be mounted "system-wide", but from what I can see, DP can't keep the drive mounted privately.
Suggestions?
Cheers,
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 12:19 PM
тАО02-13-2008 12:19 PM
Re: Data Protector and removed Shadow Set members - Catch 22
Mount the split shadow member /override=(identification,shadow_membership). Then $set volume ddcu:/label=
I know that TAPESYS will allow you to mount a split shadow set member privately in at least one of their supported pre-processing levels. Multiple post-processing levels available to re-add the member back into the shadow set also.
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 12:31 PM
тАО02-13-2008 12:31 PM
Re: Data Protector and removed Shadow Set members - Catch 22
Cheers,
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 01:00 PM
тАО02-13-2008 01:00 PM
Re: Data Protector and removed Shadow Set members - Catch 22
Cheers,
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 01:12 PM
тАО02-13-2008 01:12 PM
Re: Data Protector and removed Shadow Set members - Catch 22
Duh! I might have over thought my first answer. Why can't you use $Mount/group without changing the volume label? Mount defines the DISK$volume_label in the group table and the volume is not dismounted when the mounting process goes away. If you run DP with under a user account with a unique user group, none of the other users on the system will be able to "see" the second DISK$volume_label logical name and access it by "accident" (only a potential factor if you reference files using the DISK$volume_label logical name).
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 01:23 PM
тАО02-13-2008 01:23 PM
Re: Data Protector and removed Shadow Set members - Catch 22
Forget the pre-processing. Create a DCL procedure that will dismount your shadowset member, mount it privately, then issue an omnib -data command to fire off the backup specification. If you're lucky, the omni processes that will do the actual backup will be subprocesses of this process. If they can't get to the privately mounted disk then I guess they are separate processes and you're stuck with mounting the member with an override=shadow and incurring a full shadow copy when returned to the shadowset.
If you want a sample DCL script of an omnib backup let me know.
I will test this out when I get a chance. I run DP version 6 on my VMS systems but my disks aren't shadowed. I'll have to turn on hbvs on a test system to test this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 01:24 PM
тАО02-13-2008 01:24 PM
Re: Data Protector and removed Shadow Set members - Catch 22
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 01:40 PM
тАО02-13-2008 01:40 PM
Re: Data Protector and removed Shadow Set members - Catch 22
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 01:41 PM
тАО02-13-2008 01:41 PM
Re: Data Protector and removed Shadow Set members - Catch 22
$ mount/group $1$dga307: eva_prod1
%MOUNT-F-VOLALRMNT, another volume of same label already mounted
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 06:32 PM
тАО02-13-2008 06:32 PM
Re: Data Protector and removed Shadow Set members - Catch 22
http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1054171
I know very little about Data Protector. I would have expected it to allow you to have one procedure to make a clean shutdown of applications and a dismount (preferably with /policy=minicopy) of the third member of the shadow set. A second procedure would run at the time the tape drive became available, and this is where you should mount the disk privately (but avoiding the use of /override=shadow, since that eliminates your ability to have the member return to the shadow set without a full copy operation), and then backing up the read-only disk with /NORECORD. Not writing the backup dates to the removed member isn't a big loss, since any changes you would have made would have been erased when the member was reintroduced into the shadow set, e.g. if you would have used /over=(id,shadow) and then mounted the disk with write access, you could have recorded the backup dates on the removed member, but the record dates really belong on the shadow set that the member was removed from. After the backup completes, this same procedure can remount the member into the shadow set, and as long as the node with the master copy of the write bitmap has not shutdown/crashed, the removed member should normalize much quicker than if minicopy were not available.
The above thread also discusses the problems with having multiple volumes with the same label.
Jon