- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: System disk backup
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
тАО06-02-2003 07:09 PM
тАО06-02-2003 07:09 PM
System disk backup
I am now thinking of backing up system disk (sys$sysdevice) for my vms system.
The system disks are in general software shadowed (ie SYS$SYSDEVICE is pointing to DSAn: device)
Is it a correct practice by dissolving one member disk from the shadow set and then performing image backup from it?
Thanks,
Patrick.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2003 08:26 PM
тАО06-02-2003 08:26 PM
Re: System disk backup
In theory you should not remove one member
and backup it. Data consistency is not guaranteed in this case, however in real life
this method is very popular and heavily used
by many users. In 99.9% of the times it works.
As long as you understand the potential risk,
I think it is fine.
Guy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2003 11:26 PM
тАО06-02-2003 11:26 PM
Re: System disk backup
But, what should be the backup option when i am doing the backup?
Is the following series of commands ok(say $1$dua100) is the dismounted shadow copy?
$ mount /ov=id $1$dua100:
$ init $1$mkc100:
$ backup /image/ignore=interlock $1$dua100: $1$mkc100:system.bck /save
$ dismount $1$dua100:
$ dismount /unload $1$mkc100:
Sorry to bother, but, i have left VMS fields for 3 years...
Patrick.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2003 12:30 AM
тАО06-03-2003 12:30 AM
Re: System disk backup
To mount the former shadow member disk I think you need to include shadow_member in your override list
$ mount /ov=(id,shadow) $1$dua100:
Mac
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2003 01:29 AM
тАО06-03-2003 01:29 AM
Re: System disk backup
http://h71000.www7.hp.com/openvms/journal/v1/backup.html
There is no point in backing up most of the disk except when it changes and as pointed out in the article above using backup may not be the best way of backing up some things.
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2003 02:14 AM
тАО06-03-2003 02:14 AM
Re: System disk backup
I have some suggestions for your backup.
$ mount /ov=id $1$dua100:
==> This is fine, adding the shadow option will
allow you to write to the disk but that
comes into play when you need to restore
for now I would leave it out.
$ init $1$mkc100:
==> use /media=comp if the drive supports it
$ backup /image/ignore=interlock $1$dua100: $1$mkc100:system.bck /save
==> No need ot add /ignore=interlock, you have
the disk mounted to your process only.
==> add /block=65024 for DLT drives, this saves
a lot of time
==> add /media=comp if the drive supports it,
used both on the init and the backup cmd.
==> If you can afford the time I would use
/verify to make sure your backup can be
read, after all that is the general idea.
$ dismount $1$dua100:
$ dismount /unload $1$mkc100:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2003 01:45 PM
тАО06-03-2003 01:45 PM
Re: System disk backup
I use the method you're suggesting.
I do NOT use the /over=id when mounting it for the backup. There's no need as you're only reading from the device.
You do NOT need the /ignore=interlock as you've got exclusive access.
In addition I have migrated many of the files off the System Disk (e.g. the UAF Files) and I use a script to do a Convert/Share of these files to a backup location. Convert/share gets a cleaner copy of these files.
There was an item in one of the VMS Technical Journals the (wrapped) URL may be of interest.
http://h71000.www7.hp.com/openvms/journal/v1/backup.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2003 07:41 AM
тАО06-04-2003 07:41 AM
Re: System disk backup
We do a Disaster Recovery testing twice a year at SunGard. For the last ten years, I have never had a problem recovering my system disk from my backups.
HTH
Marty
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-05-2003 10:09 AM
тАО06-05-2003 10:09 AM
Re: System disk backup
As been pointed out dissolving the shadow set or using /ignore=interlock are two ways to get a backup of a running system. But please make sure that you understand the risks with any of these options, even if the risk of getting a bad backup is small, that risk is still real.
Also, one of the later replies pointed out that all he ever lost by using /ignore=interlock was some updates to logfiles. It might however be different if you for example have additional applications installed on the system disk.
I've used both of these methods and standalone backup at different times and not had any problem. But test any backup-restore procedure before you put it into production, remember that it isn't the backup that is important - it is the ability to restore it into a working system...
/ShyGuy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-22-2003 10:04 PM
тАО10-22-2003 10:04 PM
Re: System disk backup
MOUNT/SYSTEM DSAn: /SHADOW=($1$DUA100:) label
We have dismounted shadow sets to load patches onto the system as a security measure on disks with 2 shadow disks, and left this way for a couple of days to prove the patches. It is a risk, but we have not had any problems so far (touch wood!)