I believe best practice is to limit 4 jobs per datastore. This limits the number of snapshots happening and is a VMware limitation,not NBU. When you have too many snaps going on, things get unstable. Try doing 4, or less, per datastore. There's a global setting you can use, and I think a policy setting as well to limit this behavior.
On Wed, Feb 13, 2013 at 12:42 AM, pranav batra <pranav_vent...@hotmail.com>wrote: > We are backing up 16 jobs simultaneously in one policy. > But we have recently started facing this issue. > > PranavB > > ------------------------------ > Subject: RE: [Veritas-bu] VM snapshot deletion too slow > Date: Wed, 13 Feb 2013 06:33:14 +0000 > From: simon.wea...@iscl.net > To: pranav_vent...@hotmail.com; veritas-bu@mailman.eng.auburn.edu > > > Could be a resource issue. Check on the backup host for any outstanding > bpfis processes running. > Maybe reboot backup host and try again. > How many VM's are you backing up? I have seen this problem, and I had to > reduce the number of VM's down in each backup. > s. > > ------------------------------ > *From:* veritas-bu-boun...@mailman.eng.auburn.edu on behalf of pranav > batra > *Sent:* Wed 13/02/2013 06:01 > *To:* Veritas > *Subject:* [Veritas-bu] VM snapshot deletion too slow > > Hello Geeks, > > I am facing issues while snaspshot deletion at VMWARE side. > We are using Netbackup 7.5 and backing up our virtual machines with vmware > policy. > > Earlier snapshot creation and deletion was not that slow. > Now clients are taking like 6-7 hours for snapshot deletion and this is > making vm too lsow. > > Any piece of advise ? > > PranavB > > _______________________________________________ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > >
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
