HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- OpenVMS Standalone Backup versus Image Backup.
Operating System - OpenVMS
1828584
Members
2679
Online
109982
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
03-28-2007 12:47 AM
03-28-2007 12:47 AM
If you have two nodes A and B in a cluster each with there own system disk and you do an image backup of system disk A from node B so that node B has no open files on system disk A, is that equivalent to doing a standalone backup of disk A?
I'm just trying to find a way of doing fewer standalone backups.
I'm just trying to find a way of doing fewer standalone backups.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2007 12:54 AM
03-28-2007 12:54 AM
Re: OpenVMS Standalone Backup versus Image Backup.
Assuming that node B has no open files on node A's system disk and if node A is shutdown while node B is used to backup this system disk, then the backup is equivalent to a standalone backup.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2007 01:01 AM
03-28-2007 01:01 AM
Re: OpenVMS Standalone Backup versus Image Backup.
If node A is down, and node B has a direct path (i.e. isn't dependent on an MSCP served path) to node A's system disk, then using node B to back up node A's disk should produce as safe a backup as standalone.
If node A is up, then _it_ would likely still have files open for write on its system disk. If that's true then a backup made by node B would NOT be as safe as a standalone backup.
This is true whenever a disk as files open for write, no matter what node has opened the files. There might be other risks as well.
(And of course, if node B doesn't have a direct path/depends on MSCP for access to node A's disk, then you can't back it up at all if node A is down.)
If node A is up, then _it_ would likely still have files open for write on its system disk. If that's true then a backup made by node B would NOT be as safe as a standalone backup.
This is true whenever a disk as files open for write, no matter what node has opened the files. There might be other risks as well.
(And of course, if node B doesn't have a direct path/depends on MSCP for access to node A's disk, then you can't back it up at all if node A is down.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2007 01:02 AM
03-28-2007 01:02 AM
Solution
If you mean use node B to do an image backup of node A's system disk while node A is running, then no, this is not the equivalent of doing a standalone backup of node A's system disk.
Even though node B doesn't have any files open on node A'a disk, node A does. The process doing backup on node B will detect any that are open for write when it does the backup because it won't be able to get exclusive read to them.
The question then becomes, are there any files open for write on node A's system disk that are extremely valuable. If you have moved the authorization and queue files to a common disk for this cluster (so that you can continue to operate in case one node goes down), then the files that remain open for write on the system disk are various log files that system processes write to. If you can tolerate loss of some of the data in these files, then you may not need to do standalone backups.
Even though node B doesn't have any files open on node A'a disk, node A does. The process doing backup on node B will detect any that are open for write when it does the backup because it won't be able to get exclusive read to them.
The question then becomes, are there any files open for write on node A's system disk that are extremely valuable. If you have moved the authorization and queue files to a common disk for this cluster (so that you can continue to operate in case one node goes down), then the files that remain open for write on the system disk are various log files that system processes write to. If you can tolerate loss of some of the data in these files, then you may not need to do standalone backups.
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP