Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Virus & exception convert to a virtual machine

Created: 19 Apr 2013 | 11 comments

Our company was hit pretty hard today with a virus...  I think at this time I have all of the servers cleaned off and virus free...  So after cleaning off our servers I took our backups off hold.  However now when I start any back up job I get an exception as soon as a job starts, titled 'Convet to virtual machine".  The message is:

Failed to load the configuration xml file.
C:\Program Files\Symantec\Backup Exec\Catalogs\SPHSDNS2\CatalogProcessTemporaryFolder\{AEAF3E75-D531-428F-8221-DBEF25D56E85}\p2v.xml
 
we do not have any VM's and this problem only happened after the virus...  I am sure I am going to have more questions over the weekend, but how do I fix this?  As always thanks so much for the help.  I love this forum.
Operating Systems:

Comments 11 CommentsJump to latest comment

prs246191's picture

I read this article before I posted...  Does this apply to me even though we don't have VM's?  I guessing it applys because our san is a virtual drive?  Why did this happen after the virus...  The machine that the san is connected to was not afftected by the virus.

pkh's picture

It is more related to the condition for SDR and P2V.

prs246191's picture

So the hope is I update the san drivers and that will fix the problem

prs246191's picture

it also makes the job fail...  Updateing the SAN driver will fix it?

pkh's picture

I think the only way to solve this problem is to exclude your virtual SAN drive from the backup and then back it up using another job.

prs246191's picture

I have all of our backuos going to the SAN drive.  From BE 2012 I have had them going there for over a month without error or exception.  From our previous versions of BE they have been going to the SAN drive for over 6 months with out problems.  So why now?  And just to make it clear the SAN drive is not being backed up, it has the backups going to it.  Also that p2v.xml is not in that folder, the folded ia empty.

prs246191's picture

The problem seems to be with sdr...  When I backup just a sindle drive I do not get any errors or exceptions (backing up to the hd of another server)...  However when I fully select a server and sdr is on, backing up to the local disk of another server is when I get the error... Why?

pkh's picture

The reason is given in the document which I have quoted earlier.

prs246191's picture

The job just fails now for the given reason...   I don't really understand what you mean.  All of my jobs ran  for a month now, why after the virus did all of them fail for the exact same reason...  

prs246191's picture
I was reading another post and I don't believe that 184002 does not apply to me.  I don't know what else to try
 
DISKPART> list disk
 
  Disk ###  Status      Size     Free     Dyn  Gpt
  --------  ----------  -------  -------  ---  ---
  Disk 0    Online      1758 GB      0 B
  Disk 1    Online       103 GB      0 B
 
DISKPART> select disk 0
 
Disk 0 is now the selected disk.
 
DISKPART> detail disk
 
DELL PERC 6/i SCSI Disk Device
Disk ID: 99559BCD
Type   : RAID
Bus    : 1
Target : 0
LUN ID : 0
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C   OS           NTFS   Partition    132 GB  Healthy    System
  Volume 1     E   DATAPART1    NTFS   Partition   1626 GB  Healthy
 
DISKPART> select disk 1
 
Disk 1 is now the selected disk.
 
DISKPART> detail disk
 
DELL PERC 6/i SCSI Disk Device
Disk ID: ECEB8082
Type   : RAID
Bus    : 1
Target : 1
LUN ID : 0
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 2     D   DATAPART2    NTFS   Partition    103 GB  Healthy
 
DISKPART> k