- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: %BACKUP-F-CLUSTER, unsuitable cluster factor
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-27-2007 05:45 AM
тАО06-27-2007 05:45 AM
I created a 8GB container with CHARON's MKDISK utility (16760160 blocks) to give it a bit of "breathing room". I init'd the disk with:
$ init dka300: vms062 /dir=16000 /headers=1000000 /nohigh /index=begin /max=1000000 /system
The resulting disk has a cluster factor of 17 (as per the formula). The old disk has a cluster factor of 9.
$ backup /image saveset.bck/save dka300: /noinit
gives the error in the subject line.
If I do an image restore, letting it init the drive, it works and results in a cluster factor of 17 on the restored disk.
I would like to retain the values I specified on the init line.
Any ideas? An old patch that might be missing?
Cheers,
Art
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2007 06:22 AM
тАО06-27-2007 06:22 AM
Re: %BACKUP-F-CLUSTER, unsuitable cluster factor
I do not have a suitably configured 6.2 system handy, but I note that:
Headers and Maximum files = 1,000,000
and a disk size of 8,380,080 blocks works out to a average file size of approximately 8 blocks.
Have you tried changing the HEADERS and MAX parameters?
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2007 06:26 AM
тАО06-27-2007 06:26 AM
Re: %BACKUP-F-CLUSTER, unsuitable cluster factor
There is a patch which addresses a similar problem. But is for Alpha 7.3!
It is possible that this bug exists from 6.2 to 7.3?
There is a link to the ECO:
http://ftp.support.compaq.com.au/pub/patches/vms/axp/v7.3/dec-axpvms-vms73_backup-v0200--4.README
Maybe it will help for a workaround.
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2007 06:36 AM
тАО06-27-2007 06:36 AM
Re: %BACKUP-F-CLUSTER, unsuitable cluster factor
Bojan, yes I saw that too and went to look at the last BACKUP patch for VAX (3) but it doesn't mention the -F-CLUSTER error.
Thanks, maybe it's a quick fix.
Cheers,
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2007 06:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2007 06:50 AM
тАО06-27-2007 06:50 AM
Re: %BACKUP-F-CLUSTER, unsuitable cluster factor
Bob, reply back ... you deserve a few more points for making me think ;-)
Thanks and Cheers,
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2007 07:17 AM
тАО06-27-2007 07:17 AM
Re: %BACKUP-F-CLUSTER, unsuitable cluster factor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2008 05:16 AM
тАО10-15-2008 05:16 AM
Re: %BACKUP-F-CLUSTER, unsuitable cluster factor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2008 07:40 AM
тАО10-15-2008 07:40 AM
Re: %BACKUP-F-CLUSTER, unsuitable cluster factor
How big was the old disk, and how big is the new disk? (If I've done the math correctly, it looks like it might be an RZ23 disk? And is this really a 104 MB disk?)
Which VAX? (There are other disk-capacity issues, depending on the VAX model and VAX console.)
Is this BACKUP /IMAGE a system disk?
How many files were on the old disk?
What command(s) did you use to restore the disk?
To INITIALIZE the disk?
What was the original BACKUP command? (You can get this from the BACKUP /LIST -- just post the whole header.)
There are cases where BACKUP cannot restore a disk image due to conflicts in the structures, too.
As for the specified maximum file count here, I've yet to encounter an OpenVMS system that has a disk anywhere near full of one-cluster files. Is that really the case here? (There's a tool around -- DFU? -- that can show the distribution of files sizes.
---
CLUSTER, unsuitable cluster factor for 'device-name'
Facility: BACKUP, Backup Utility
Explanation: During an attempt to initialize an output volume, the Backup
utility found that the cluster factor was too large or too
small for the specified device.
User Action: If the input is a save set, use the BACKUP/LIST command
to determine the volume initialization parameters of the
input volumes. Refer to the description of the DCL command
INITIALIZE, determine a suitable cluster factor, and
initialize the output volumes using the INITIALIZE command.
Then, reenter the command specifying the /NOINITIALIZE
qualifier.
---
I'd tend to start a new thread; where you have control over the thread and over the discussion. Certainly reference the case and the thread here, but your case here does differ from the original thread. Same error, yes, but different commands and different OpenVMS VAX versions.