Forum Discussion

paranoidsystems's avatar
paranoidsystems
Level 3
9 years ago

BE 15 failing on GRT VM back up. (out of space but there is still space)

Hi Guys,

 

first time poster here, got a couple of questions and an issue. I have a new hyper-v server here (2012 running two VM's).

My orginal post on the 8th of Jan just sat for days only visible to me or not approved or something so I apologise if that suddenly appears.

currently setup is like this.

Host with 2 VM's

VM1 AD VHD (15.8gb)

VM2 File Server VHD (482gb)

RD1000 unit with 1tb cartridges has 410gb of 931gb free after back up

the VHD for the AD is on my system drive (238gb of 278gb free)

The VHD for the File server is on my DATA array (331gb of 836 gb free)

I use a "tape" every weekday and they are set for 5 days protection.

I have the agents installed on both VM's and test run is ok. All credentials work when tested. The back up fails with a communication error and error about the back-up-to-disk folder being full. If I disable GRT then the back-up works. but that way I do not have the actual VHD's on my back up "tape". I am not sure if I have set something up wrong or do I need the same amount of space free on system drive as the size of the VHD I am backing up? any help would be appreciated.

15
Backup and Recovery
Backup Exec
Not Applicable
  • pkh's avatar
    pkh
    9 years ago

    If you take a look at the date of the document, you would see that it is only issued last week.  It is not an old problem which you were not made aware of earlier.

15 Replies

Sort By
Show More
  • paranoidsystems's avatar
    paranoidsystems
    Level 3
    9 years ago

    well I have all but given up now. Turned off GRT and back-ups working again. and they are only 20gb smaller than my GRT enabled backups so I dont know what to think anymore.

  • beyond-done's avatar
    beyond-done
    Level 2
    9 years ago

    It's a known issue...  here is the tech article.

    http://www.veritas.com/docs/000100424

    Took 3 months for this.  Worst support experience ever.  We'll be looking at other vendors.

  • pkh's avatar
    pkh
    Moderator
    9 years ago

    If you take a look at the date of the document, you would see that it is only issued last week.  It is not an old problem which you were not made aware of earlier.

  • paranoidsystems's avatar
    paranoidsystems
    Level 3
    9 years ago

    Thanks PKH that seems to be exactly my issue. Hope this gets resolved at some point. Atleast I know it's on the radar now. 

  • beyond-done's avatar
    beyond-done
    Level 2
    9 years ago

    I know the document was just published last week.  My issue is with the run around that I got without any real troubleshooting just to have them finally give me a tech article that was published a week earlier and telling me it is a known issue.  Basically, if someone would have done their job 3 months ago, they would have known about the issue a lot earlier and I wouldn't have wasted weeks of my time dealing with inept support technicians that don't understand the basics of how the product works and how to troubleshoot it.

    Just FYI, I worked for Symantec for 9 years doing technical support.  I know how it works and I know the problems that BE Support is having with their outsourced people.  It's terrible.  However, if Veritas wants to keep their support outsourced to a company that can't provide a basic level of support then I'm suggesting that my company take their business elsewhere.  Veritas made the decision to accept the risk and this is the consequence that they get. /rant off.