FYI,
same here...but my range/ratio was:
~2 mil occ to 25 mil deleted objects...
Never solved the mystery... gave up :->
--
Sasa Drnjevic
www.srce.unizg.hr/en/
On 2019-02-25 20:05, Zoltan Forray wrote:
> Here is a new one...
>
> We turned off backing up SystemState last week. Now I am
You're seeing the same issue I've seen.
Q OCCUP values for SystemState seem to have no relationship to the number that
are eventually deleted.
The value on Q OCCUP is always much lower than what is reported in Q PRO.
And, deleting system state takes a LONG time.
-Original Message-
From
Here is a new one...
We turned off backing up SystemState last week. Now I am going through and
deleted the Systemstate filesystems.
Since I wanted to see how many objects would be deleted, I did a "Q
OCCUPANCY" and preserved the file count numbers for all Windows nodes on
this server.
For
I have this node which is stuck with bad replication information that is
keeping me from deleting its backups/filespaces. Replication has been
turned off on this server. Any attempt to delete the filespaces produces
this error:
2/25/2019 10:35:12 AM ANR2017I Administrator ZFORRAY issued command:
Hi Hans,
Yes. It's like before. If you do a "Typical" install, it only installs
the base client. It won't be listening to any ports unless you install
and configure services that would required to listen. Like a Prompted
Scheduler.
The web user interface for restore will only be installed
Is it possible to install the client without a running web-server and
without the client listening to any port? (CAD controlled scheduler,
polling).
Hans Chr.
On Mon, Feb 25, 2019 at 6:07 AM Mark Yakushev wrote:
> Hi Tom,
>
> The increase in size is attributed mostly to this item:
>
> "Simplifi
