[Veritas-bu] VSP leaving drives behind

2003-12-16 11:13:28
Subject: [Veritas-bu] VSP leaving drives behind
From: cheryl.king AT intrado DOT com (King, Cheryl)
Date: Tue, 16 Dec 2003 09:13:28 -0700
I had the problem where it tries to backup file systems that aren't there.  It 
fails with F: or G: does not exist and never actually backs up these file 
systems.  I was using the ALL_LOCAL_DRIVES when it failed and changed to 
specific drives as a work around.  The WIN system that I have the problem on is 
on a Master/Media servers that was 4.5 FP4 (Solaris) and upgraded recently to 
4.5 FP5.  I thought FP5 was supposed to fix it but it didn't.  Now you've got 
me thinking and I probably just need to go cleanup the WIN system and the 
problem won't happen.

My second Master/Media server (Solaris) which has many Window systems it backs 
up, has never had the problem.  It was at 4.5_MP2 and then recently upgraded to 
FP5.  It went from MP2 to FP5 so it never ran FP3 without the FP5 patches.  I 
believe there is a fix in FP5 so I'm surprised that you say you are on FP5.

Anyway I'll work on that problem system and let you know if it clears up.  It 
only happes when scheduled FULL backups run once a week. 

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Mark
Sent: Tuesday, December 16, 2003 4:27 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] VSP leaving drives behind

I have also seen this problem and we could only delete the snapshot drives by 
rebooting the client. It VSP screws up a few times you can end up with a number 
of snapshot drives on your disk and the disk space can fill up. More concerning 
is that this will only be discovered if you examine your drive for any *.vsp 

Message: 8
Date: Thu, 11 Dec 2003 17:11:52 -0600
From: David Rock <dave-bu AT graniteweb DOT com>
To: veritas-bu AT mailman.eng.auburn DOT edu
Reply-To: David Rock <dave-bu AT graniteweb DOT com>
Subject: [Veritas-bu] VSP leaving drives behind

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I am running 4.5 FP 5 on a Solaris master server and have discovered on
a Windows 2000 Client with VSP enabled that when VSP screws up and
causes the job to fail, it is not getting rid of the snapshot drives it
created. rebooting the machine cleans them up, but stopping and
starting the Netbackup client service does not. Does anyone know of a
way to clean up the snapshot drives without rebooting the client?

This would not be so bad, except the drive it's snapshotting is 400 Gig
and NetBackup thinks it is a valid drive. So the next time it runs a
backup job, it thinks it is supposed to back up the snapshot drive AND
the real drive, making 800 Gig of backups instead of 400 Gig. Yuck.

David Rock
david AT graniteweb DOT com


Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
Version: 6.0.544 / Virus Database: 338 - Release Date: 25/11/2003

Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu