I see that all the time where there is a difference between the export and
import totals - sometimes 2-3 objects (or more) difference - sometimes
occupancy totals varying a little. A long time ago when I first saw
such a difference, I reran the export with mergefilespace and it still
didn't ch
Nothing happens to data on the SOURCE server, where the data is exported
from.
EXPORT NODE just puts a COPY of the client data into a portable format.
You can export the same client, over and over and over.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behal
Enter Q OCC
That shows the same information as auditocc, but broken down by storage
pools.
-Original Message-
From: Blaine Gilbreath [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 09, 2001 10:06 AM
To: [EMAIL PROTECTED]
Subject: Export Question
I am working on an Export process and I a
nt: Monday, April 09, 2001 9:51 AM
To: [EMAIL PROTECTED]
Subject: Re: Export Question
Maybe the missing data is copy storagepool data that isn't included in an
export?
>I am working on an Export process and I am running into some capacity
>discrepancies.
>Below is the process that I
Are you using copypools to protect your primary stg-pools?
If so, q occup and auditocc report the total occupancy of both primary
and copy.
On Mon, 9 Apr 2001, Blaine Gilbreath wrote:
> I am working on an Export process and I am running into some capacity
> discrepancies.
> Below is the proce
Maybe the missing data is copy storagepool data that isn't included in an
export?
>I am working on an Export process and I am running into some capacity
>discrepancies.
>Below is the process that I followed.
>
>1. Run AUDIT LICENSE
>2. QUERY AUDITOCC
>3. The node shows that ADSM has 845GB of d
