- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: No free block left after backup/image
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
10-14-2020 08:11 AM
10-14-2020 08:11 AM
Re: No free block left after backup/image
Gérard,
in your first screenshots, you've used BACKUP/IMAGE, that should have correctly initialized the output disk. Were these screenshots from different tests ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-14-2020 08:21 AM
10-14-2020 08:21 AM
Re: No free block left after backup/image
i used first /image and faced the 0 free block left problem. i then used the other backup.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-18-2020 05:04 AM - edited 10-18-2020 05:29 AM
10-18-2020 05:04 AM - edited 10-18-2020 05:29 AM
Re: No free block left after backup/image
I would have expected the BACKUP/IMAGE to initialize the disk with the same clustersize as the input disk. You can either initialize the disk prior to the backup and specify BACKUP/NOINIT or just make sure that there is no symbol set up for backup that is turning off the initialization stage. As you have seen, the difference in clustersize will cause the space usage change you are seeing.
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-18-2020 12:05 PM
10-18-2020 12:05 PM
Re: No free block left after backup/image
Thank's Dan i Will use a backup noimage and noinit alter manual initilization.
regards
Gerard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-18-2020 01:23 PM
10-18-2020 01:23 PM
Re: No free block left after backup/image
No. Please use BACKUP/IMAGE for the entire disk. The key here is to add the qualifier /NOINIT. This will make sure that your initializaton won't be overwritten. Truthfully, BACKUP/IMAGE should have preserved the clustersize of the disk being copied, but for whatever reason it did not. An IMAGE copy is required here to preserve any back links etc.
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-18-2020 09:04 PM
10-18-2020 09:04 PM
Re: No free block left after backup/image
As it is not a system disk i think i can use a backup of [*...]*.*;* with the /by_owner qualifier on the destination.
I think the backup/image on the first post did the initialisation with the same clustersize as the source disk. The différent clustersize later in this post is the result of a manual initialization and backup. ( result of différent trys)
Btw i will try the /image/noinit ...
Thank you fit your help
Gerard
- « Previous
-
- 1
- 2
- Next »
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP