-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I would think veritas support would not recommend this or condone it, but if
you have no other choice, make sure you have the underlying network 
infrastructure/arch
worked out.  So the network connection to the netapp from the master server, can
it be on a different link than how the NDMP backups take place (unless the 
drives are
on the filer).  Is that link resilient, if solaris ipmp, if linux bonding, if 
Windows ???.
Bottom line is that you are going to tie your backup, or more importantly, 
restore
to a separate infrastructure, not that this is right or wrong, you just need to
think about the ramifications.  Is the NetApp clustered?  Replicated?

Also, on nbu server startup, make sure that the mount is there before NBU
starts.  If you are running out of catalog space, then take note of how
that catalog backups run and what impact that will have.  Also, there may
need to be some tuning if this is NFS for the mount, such as turning off
acl checks, making it run over tcp, make sure the mount is hard but intr, etc...

If this were to work, then it would give you clustering capabilities as well as
an interesting DR solution.

Peter DrakeUnderkoffler
Xinupro, LLC
617-834-2352



Algo Seeker wrote:
> I am running out of space on my internal drives. I am also thinking
> about migrating to a new server. Anybody moved from local file system to
> shared storage. Almost all of my backups are NDMP (Netapps), and as the
> number of files are growing so is the Catalog. What are the pros and cons?
> 
> Any input?
> 
> Thanks,
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFD4iZql+lekZRM55oRAggvAKDNVX6WdkXf9ojMp6Z5k84vLAr3RgCfXBvw
aiLqHalM4mld2GRRY4f11Tw=
=wFJf
-----END PGP SIGNATURE-----