I'll assume you have cache=yes on the pool.  What if you set cache=no for
the next migration?  Perhaps that will clear up this problem.  If not, you
could delete the volume from the pool after the migration and then re-add
it.  That's a pretty big hammer, but once you've migrated all the data you
can you will be safe.

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (240) 539-7175
Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com
www.storserver.com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Ghanekar, Prasanna
Sent: Thursday, May 24, 2001 9:16 AM
To: [EMAIL PROTECTED]
Subject: Audit Volume not Helping


Hi Everyone,

I'm running ADSM V3.1.2.40 on Windows NT server with SP5.
Every night when the Migration process begins it gives me errors about two
nodes pointing to the damaged files on the disk volumes such as "Data1.dsm".

Message:
ANR1168W Migration skipping damaged file on volume D:\DATA1.DSM: Node
PEASGAI1_CLIENT,
 Type Backup, File space \\peasgai1\c$, File name \ADSM.SYS\REGISTRY\PEASGA-
I1\MACHINE\ SAM.
When I run Audit on this volume with the Repair ?fix option, it goes through
the process, finds damaged files , marks those files as damaged but doesn't
delete. I get the following message at the end;
ANR2314I Audit volume process ended for volume D:\DATA1.D- SM; 21127 files
inspected, 0 damaged files deleted, 569 damaged files marked as damaged.
 How do I avoid getting the same messages during the migration process ?
Thanks in advance,
Prasanna


Prasanna Ghanekar
 <<...OLE_Obj...>>
EDS Pontiac East
2100 S Opdyke Rd
MI 48341
*: (248) 972-4547

Reply via email to