- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: VAX/VMS Standalone Image backup of System disk
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
тАО12-22-2008 12:39 AM
тАО12-22-2008 12:39 AM
VAX/VMS Standalone Image backup of System disk
I want to craete a standalone image backup from the system disk to send to a remort site to clone the same server there. It is as old as VMS 5.5 and VAX server. I made online image backup but doubt that it will boot or not ?
Please advise me as what could could be the best way.
Thanks is advance
Nisar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2008 12:48 AM
тАО12-22-2008 12:48 AM
Re: VAX/VMS Standalone Image backup of System disk
if you've used BACKUP/IMAGE to back up your system disk, then you have created a bootable copy of your system disk. If you've done this while the system was running, the backup of certain files may have been skipped. Using /IGNORE=INTERLOCK would be better, but a real standalone backup would be the best way.
You can create a bootable standalone backup environment on your system or any other disk with @SYS$UPDATE:STABACKIT device: - then boot this with B/E0000000 device (if it's on the system disk) or B/0 device (on a non-system disk) and create your consistant standalone backup of the system disk.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2008 04:03 AM
тАО12-22-2008 04:03 AM
Re: VAX/VMS Standalone Image backup of System disk
I concur with Volker, and suggest that you take particular emphasis on several areas.
First, having an alternate bootable image is a very useful thing. Having a standalone bootable image (typically located as Root F) is particularly useful. It is far easier to recover from an accident if there is an alternate set of configuration files. The separate ability to to a Standalone BACKUP without extra media is different, but no less useful.
Also, remember to change the system name, SCSID, and network addresses (DECnet and TCP/IP) of the cloned pack as soon as is possible (preferably as soon as the disk is created). Far too many network accidents are caused by accidentally booting a duplicate network persona (address) where it can be seen by the network.
Of course, verify that you have done the proper licensing for the other system and load the correct licenses into the license database.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2008 02:34 PM
тАО12-22-2008 02:34 PM
Re: VAX/VMS Standalone Image backup of System disk
> (typically located as Root F) is
> particularly useful [...]
As VH implied, the default location (on a
system disk) is "E" (SYSE), not "F", but yes,
a Standalone BACKUP installation is pretty
small, so I normally have one on every disk
in the system. If you have a CD-ROM drive,
you don't need to worry so much, but if your
only other bootable medium is a TK50 tape,
then any other option (even floppies) looks
good.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2008 06:41 PM
тАО12-22-2008 06:41 PM
Re: VAX/VMS Standalone Image backup of System disk
If you have a CD drive, or even a spare disk, you can boot "standalone DCL" on a VAX, just like on an Alpha. Just boot an operating system distribution CD V6.1 or higher from root 1. You'll get a $$$ prompt. It's a bit more flexible than standalone backup as you can execute most DCL commands.
I know you said you're running V5.5, but the version you use to backup the disk doesn't matter. Bits are bits. Just use the same boot CD at both ends.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2008 11:08 PM
тАО12-22-2008 11:08 PM
Re: VAX/VMS Standalone Image backup of System disk
Thank you for noting the typographical error in my reply.
The default place to put Standalone BACKUP is [SYSE], which is a useful convention. I should note that I know of nothing that makes that a requirement in any way.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-23-2008 02:17 AM
тАО12-23-2008 02:17 AM
Re: VAX/VMS Standalone Image backup of System disk
>>>
The default place to put Standalone BACKUP is [SYSE], which is a useful convention. I should note that I know of nothing that makes that a requirement in any way.
<<<
True, with ONE exception. And that happens to be exactly Bob's earlier typo.
[SYSF] is created and used during OS upgrades. After succesful upgrade it is removed.
If you EVER have to use [SYSF] (the only valid reason I know of is a 16 node, no satellites, pure-VAX cluster) then upgrading becomes a real specialist's job.
But that config seems pretty obsolete nowadays.
hth
Seasonal greetings.
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-14-2009 11:23 PM
тАО01-14-2009 11:23 PM