- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Restoring saveset greater than 512GB fails
Operating System - OpenVMS
1748143
Members
3582
Online
108758
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
тАО04-01-2008 04:52 PM
тАО04-01-2008 04:52 PM
Restoring saveset greater than 512GB fails
We are able to perform an image backup of a disk yet the corresponding restore fails with
%BACKUP-F-LARGECNT, $1$DGA2049: is too large to be processed
$ backup/image/log tape:data.bck/norewind $1$DGA2049:
%BACKUP-S-CREATED, created $1$DGA2049:[000000]000000.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[000000]BACKUP.SYS;1
%BACKUP-S-CREATED, created $1$DGA2049:[000000]CONTIN.SYS;1
%BACKUP-S-CREATED, created $1$DGA2049:[000000]CORIMG.SYS;1
%BACKUP-S-CREATED, created $1$DGA2049:[000000]PRD.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD]DB1.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD.DB1]CDB.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD.DB1.CDB]ADMIN.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD.DB1.CDB.ADMIN]DB1.DAT;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD]DB2.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD.DB2]CDB.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD.DB2.CDB]DB2.DIR;1
%BACKUP-F-LARGECNT, $1$DGA2049: is too large to be processed
BACKUP job terminated at 27-MAR-2008 13:29:18.24
The saveset is 565GB in size.
Total of 1 file, 565.42GB/565.42GB
We are running VMS 7.3-2.
Have we reached a limit with backup ?
%BACKUP-F-LARGECNT, $1$DGA2049: is too large to be processed
$ backup/image/log tape:data.bck/norewind $1$DGA2049:
%BACKUP-S-CREATED, created $1$DGA2049:[000000]000000.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[000000]BACKUP.SYS;1
%BACKUP-S-CREATED, created $1$DGA2049:[000000]CONTIN.SYS;1
%BACKUP-S-CREATED, created $1$DGA2049:[000000]CORIMG.SYS;1
%BACKUP-S-CREATED, created $1$DGA2049:[000000]PRD.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD]DB1.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD.DB1]CDB.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD.DB1.CDB]ADMIN.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD.DB1.CDB.ADMIN]DB1.DAT;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD]DB2.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD.DB2]CDB.DIR;1
%BACKUP-S-CREATED, created $1$DGA2049:[PRD.DB2.CDB]DB2.DIR;1
%BACKUP-F-LARGECNT, $1$DGA2049: is too large to be processed
BACKUP job terminated at 27-MAR-2008 13:29:18.24
The saveset is 565GB in size.
Total of 1 file, 565.42GB/565.42GB
We are running VMS 7.3-2.
Have we reached a limit with backup ?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-01-2008 05:03 PM
тАО04-01-2008 05:03 PM
Re: Restoring saveset greater than 512GB fails
How big is the target disk volume, and what is the volume cluster factor?
This could be a too-small cluster factor, or a disk that's above a terabyte; either one is bad. Or it could well be something else.
As a first step, I'd INITIALIZE the disk with a larger cluster factor (minimally) and the appropriate numbers of headers and files for the volume, and add the /NOINIT onto the BACKUP command.
The usual suggestion around being (or getting) current on your patch kits applies. Particularly the UPDATE, BACKUP, SCSI/FC and any other mandatory kits, given this case.
Entirely unrelated to the problem here and strictly as I'm paranoid, I prefer to add /SAVE onto the saveset parameter within the BACKUP command though it is likely in this case that tape: is mounted /FOREIGN.
This could be a too-small cluster factor, or a disk that's above a terabyte; either one is bad. Or it could well be something else.
As a first step, I'd INITIALIZE the disk with a larger cluster factor (minimally) and the appropriate numbers of headers and files for the volume, and add the /NOINIT onto the BACKUP command.
The usual suggestion around being (or getting) current on your patch kits applies. Particularly the UPDATE, BACKUP, SCSI/FC and any other mandatory kits, given this case.
Entirely unrelated to the problem here and strictly as I'm paranoid, I prefer to add /SAVE onto the saveset parameter within the BACKUP command though it is likely in this case that tape: is mounted /FOREIGN.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-01-2008 05:05 PM
тАО04-01-2008 05:05 PM
Re: Restoring saveset greater than 512GB fails
> Have we reached a limit with backup ?
Sure looks that way.
alp $ help /mess /faci = backup LARGECNT
LARGECNT, 'device-name' is too large to be processed
Facility: BACKUP, Backup Utility
Explanation: The specified volume is too large to be processed by the
Backup utility. Possibly the specified cluster factor is too
small.
User Action: Retry the operation using a larger volume cluster factor.
Perhaps an explicit INITIALIZE of the
destination disk (and BACKUP /NOINITIALIZE)?
I wish that I owned that much tape, let alone
disk space, so that I could care more.
Sure looks that way.
alp $ help /mess /faci = backup LARGECNT
LARGECNT, 'device-name' is too large to be processed
Facility: BACKUP, Backup Utility
Explanation: The specified volume is too large to be processed by the
Backup utility. Possibly the specified cluster factor is too
small.
User Action: Retry the operation using a larger volume cluster factor.
Perhaps an explicit INITIALIZE of the
destination disk (and BACKUP /NOINITIALIZE)?
I wish that I owned that much tape, let alone
disk space, so that I could care more.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP