Hi Simon,
In addition to Adam's comments:
the restore making better use of blocks since it gets to re-write your data from scratch, etc.
Directories on the source won't reclaim space from old entries on deletion, but will be reclaimed using restore via NDMPcopy.
You will also probably have a restore_symboltable file on the destination side that is required by restore when doing incrementals.
Cheers, Grant
-----Original Message----- From: Fox, Adam [mailto:Adam.Fox@netapp.com] Sent: Monday, July 09, 2001 8:05 AM To: 'Clawson, Simon'; 'toasters@mathworks.com' Subject: RE: du -s after ndmpcopy - why are the filesizes different?
I guess my question is how different were the results? A couple of percentage different is normal in dump/restore situations, which ndmpcopy is. Things like the restore making better use of blocks since it gets to re-write your data from scratch, etc.
As far as verifying ndmpcopy, remember that ndmpcopy is just a native ONTAP dump/restore so any method you would use to verify your backups would also apply here. Most of them are not fun like what has been suggested of comparing file by file. If you trust your backups, you should be able to trust ndmpcopy.
-- Adam Fox NetApp Professional Services, NC adamfox@netapp.com
-----Original Message----- From: Clawson, Simon [mailto:simon_clawson@mentorg.com] Sent: Monday, July 09, 2001 8:11 AM To: 'toasters@mathworks.com' Subject: du -s after ndmpcopy - why are the filesizes different?
I ran an NDMP copy on my filer to take some qtrees from one volume to another. When I ran du -s on each directory the results were different in most cases.
The question I have is - Is NDMP copy the tool for the job, and how do I verify the results once I have run it?
Any ideas?
Simon
Simon Clawson HDS Team Systems Administrator Mentor Graphics Uk Rivergate London Road Newbury Berkshire RG14 2QB <<Clawson, Simon.vcf>>