We are only just starting to do this, but we did some testing and our plan is:
Very small servers: Install NetBackup Standard Client in the Global Zone and backup all file systems from there - can only be done if there are no applications like Oracle in the non-global zones. Medium servers: Install NetBackup Enterprise Client in the Global Zone, backups as above but can use SAN Client or SAN Media server to move more data. Most servers: Install NetBackup Media Server in the Global Zone, backups as above but can install NetBackup Standard Client in a non-global zone with the Application & Database pack (Oracle Agent). That non-global zone would backup to the Global Zone Media Server, the internal network is fast. Note that under the latest licencing a Standard Client licence is also required even to backup the global zone, as the Media Server licence only covers backing up the NetBackup software. It would be possible for a client in a non-global zone to backup to a quite different Media Server, so you could have variations of these. What we did have to do was change our installation processes so the Standard Client is installed in /opt/openv not /usr/openv. Otherwise the non-global zone inherits the soft link from /usr to /opt from the global zone if there is a NetBackup Server product installed in the global zone in the default Solaris configuration, and you cannot install the software. Exclude lists will need very careful construction if there are NetBackup clients in the non-global zones. Originally we were going to put the PureDisk Deduplication Option plug-in onto the Media Server in the global zone, which would have deduplicated the data before it left the chassis, but we are not now going to do backup to disk. I have to say that this is not like your approach with storage snapshots, and I don't think we yet know what the CPU load impact will be like. William D L Brown veritas-bu-boun...@mailman.eng.auburn.edu wrote on 10/06/2009 08:54:09: > Hello, > > for a couple years we are heavily using Solaris 10 zones. > So far we backup them using ufsdump/vxdump. We are investigating > Netbackup as a replacement for ufsdump/vxdump. Our home-made > backup scripts work more or less in the following way: > > 1. For all <zones>: > 1.1 zlogin <zone> > 1.2 shutdown <application - mainly Oracle> > 1.3 shutdown <zone> > > 2. For all <zones>: > 2.1 create snapshot and storage checkpoint (depends on license we have) > 2.2 start <zone> (automatic application startup) > > 3. For all vxfs snapshots > 3.1 vxdump to tape > > 4. For all ufs snapshots > 4.1 ufsdump to tape > > Basically we need similar approach using NetBackup (or if there is > more optimized approach - please tell me). > Can you share your experience regarding this topic ? > What is your approach ? > How many zones do you backup using NBU ? > How long does your backup last ? > > > > Regards > Przemyslaw Bak (przemol) > -- > http://przemol.blogspot.com/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ---------------------------------------------------------------------- > Dobra czy zla wiadomosc? Zawsze warto oszczedzac. Teraz 5,5%. > Sprawdz > http://link.interia.pl/f21b0 > > _______________________________________________ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > ----------------------------------------------------------- This e-mail was sent by GlaxoSmithKline Services Unlimited (registered in England and Wales No. 1047315), which is a member of the GlaxoSmithKline group of companies. The registered address of GlaxoSmithKline Services Unlimited is 980 Great West Road, Brentford, Middlesex TW8 9GS. ----------------------------------------------------------- _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu