Skip to main content
We have a backup script that suspends and restores writes by going into Universe and setting the SYSTEM()  variable 27/43.  We had a problem when after the script suspended writes the unsuspend failed because user license limits were briefly reached.  What is the best way to recover beyond adding more licenses?
We have a backup script that suspends and restores writes by going into Universe and setting the SYSTEM()  variable 27/43.  We had a problem when after the script suspended writes the unsuspend failed because user license limits were briefly reached.  What is the best way to recover beyond adding more licenses?
I would recommend using the "uv -admin" command. The following options allow for suspending, un-suspending, and reporting the status.

-L{ock} Suspend file I/O.
-R{eport} Current suspension status.
-U{nlock} Unsuspend file I/O.

Neil
We have a backup script that suspends and restores writes by going into Universe and setting the SYSTEM()  variable 27/43.  We had a problem when after the script suspended writes the unsuspend failed because user license limits were briefly reached.  What is the best way to recover beyond adding more licenses?
Does the uv -admin command use a license?
We have a backup script that suspends and restores writes by going into Universe and setting the SYSTEM()  variable 27/43.  We had a problem when after the script suspended writes the unsuspend failed because user license limits were briefly reached.  What is the best way to recover beyond adding more licenses?
uv -admin does not consume a license
Terms & ConditionsAccessibility statement