PN Disk Space Alerts

A protected node’s virtual disk (vdisk) requires a specific amount of disk space. onQ alerts you when your protected node’s vdisk capacity usage exceeds 80%.

Error Code	Severity & Subject	Message	Cause	What do I do?
A0901	CRITICAL – Failure of Recovery Node Creation for <PN-Name>	An unexpected error was encountered when attempting to update the contents of a Recovery Node. The error status returned was: SystemErrDiskFull(e:). No further updates to the Recovery Node will be attempted until you select the Initialize button. Please contact Quorum Support to resolve this error.	One of two reasons: • RN was built for the first time and vdisk for one or more volumes is under allocated. • RN was reinitialized (even if earlier RN exists) and vdisk for one or more volumes is under allocated. The error message indicates the relevant disk drive/volume. In this example, e:.	Resize the vdisk.
A0902	CRITICAL – Volume <volume/disk> on <PN-Name> has insufficient disk space	Volume <volume/disk> of Recovery Node <PN-Name> is configured with disk space insufficient to create a new RN from the current snapshot. The previous RN will be left unchanged. The snapshot data for the PN is intact and a new RN will be created when the configured disk space is increased....	Initial vdisk size allocated for a volume on the PN (when PN was configured via the Protect Me button or manually on to the HA) is inadequate because of the growing data on PN in the corresponding volume. In this case, the onQ Manager does not update the RN.	Resize the vdisk.
A0101 A0102	CRITICAL - Diskspace Low	The free Repository space on <Appliance-Name> has fallen below allowable limits...	onQ has a built-in policy whereby if its disk space exceeds 85% onQ begins to “free up” space by deleting PN backups, starting with the oldest backups.	Add more disk space or delete orphan backups manually.
A0103 A0104	CRITICAL - Diskspace Critical	The free Repository space on <Appliance-Name> has fallen below allowable limits...	onQ has a built-in policy whereby if its disk space exceeds 85% onQ begins to “free up” space by deleting PN backups, starting with the oldest backups. In this case, this threshold was reached, so onQ began deleting PN backups, starting with the oldest backups.	Add more disk space or delete orphan backups manually,
A0303	CRITICAL - Free Diskspace Was Critically Low, Some Expirations FAILED: <ApplianceName>	The free Repository space on <Appliance-Name> has fallen below allowable limits. Expiration of oldest backups failed for some PNs. OnQ successfully expired <#ofbackups> oldest backups: $arg2	onQ has a built-in policy whereby if its disk space exceeds 85% onQ begins to “free up” space by deleting PN backups, starting with the oldest backups. In this case, this threshold was reached, so onQ tried deleting PN backups, starting with the oldest backups. Some expirations failed.	Add more disk space or delete orphan backups manually.
A0304	CRITICAL - Free Diskspace Was Critically Low: <ApplianceName>	The free Repository space on <Appliance-Name> has fallen below allowable limits. OnQ expired oldest $arg2% of backups (total of <#ofbackups>) for each Protected Node in order to recover space:" <space>	onQ has a built-in policy whereby if its disk space exceeds 85% onQ begins to “free up” space by deleting PN backups, starting with the oldest backups. In this case, this threshold was reached, so onQ began deleting PN backups, starting with the oldest backups.	Add more disk space or delete orphan backups manually.

v3.6 SP1