Zoltan -
This, of course, is the historic "Many small files" challenge.
Recommendations on it are summarized in ADSM QuickFacts, based upon
our communal pursuit of it in our shops.
You've provided no information about the client system itself, where
memory and swap space contribute to the issue,
@VM.MARIST.EDU
Subject: Re: [ADSM-L] ANS5013E Not enough memory for backup operation
Restore? Whoever thinks about that ;--)))
I would predict a lot longer than that.
When we had a major SAN failure on our old email server (25M objects), it
took 15-days to completely restore. The OS
Thanks for the info.
Wanda Prather <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
10/09/2008 12:13 PM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] ANS5013E Not enough memory for backup operation
Yo
<[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
10/09/2008 11:43 AM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] ANS5013E Not enough memory for backup operation
What does one think will happen if one needs to restor
in the logs
> and didn't know what to do about them", not that they ever thought of
> contacting me..
>
>
>
> Wanda Prather <[EMAIL PROTECTED]>
> Sent by: "ADSM: Dist Stor Manager"
> 10/09/2008 11:41 AM
> Please respond to
> "ADSM: D
ase respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] ANS5013E Not enough memory for backup operation
Hi Zoltan,
I've seen the problem on clients with as few as 10m files.
When you do a typical incremental backup, the first thing that
sage-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan
Forray/AC/VCU
Sent: Thursday, October 09, 2008 9:24 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] ANS5013E Not enough memory for backup operation
Is there a "realistic" maximum number of files a Windo
Correction:
When I said "active backup set, that was a bad thing to call it.
What I meant was a list of the active versions stored on the server for that
client.
The client compares against that list to determine if a file has changed or
been deleted since the last backup.
On Thu, Oct 9, 2008 at
area, but it will let the host actually get a complete
backup without dying.
Ben
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan
Forray/AC/VCU
Sent: Thursday, October 09, 2008 9:24 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] ANS5013E Not e
Hi Zoltan,
I've seen the problem on clients with as few as 10m files.
When you do a typical incremental backup, the first thing that happens is
that the server pushes down to the client a list of the "active" backup
set.
The problem is with the client handling that list.
I'm surprised you aren't
ill let the host actually get a complete
backup without dying.
Ben
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan
Forray/AC/VCU
Sent: Thursday, October 09, 2008 9:24 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] ANS5013E Not enough
Is there a "realistic" maximum number of files a Windows client can handle
before having this kind of problem?
This system has 30-40 MILLION objects/files.
Not sure if this error is caused by the large number of files or a client
problem. They are currently running the 5.5.0.6 client. Recommende
12 matches
Mail list logo
