Video Screencast Help

Better logs for trouble shooting ?

Created: 14 Aug 2013 | 12 comments

I am working on a clients 2012.   We had an issue a few days ago where their VCenter sent us a warning that thier datastore was getting full and it was due to a snapshot not deleting after the backup was done.    I go through typical logs and they all show the backup was successful.   Is there better logs that I can look at ?   I have seen a couple posts about setting up bigger and better logs that you can run for a while but that doesn't help me to go back in time.   And does this version not show when it creates the snapshot and when it deletes it ?

Thanks

Mike

Operating Systems:

Comments 12 CommentsJump to latest comment

lmosla's picture

Hello,

Take a look here for some info on debugging virtual servers http://www.symantec.com/docs/TECH63926

Kunal.Mudliyar's picture

You can view the Tasks & Events tab in the Vcenter after selecting the VM .

Goto the Events tab and you see events of the backup like creation , removal and consolidation of disks.

event 1.jpg

Technical Support

Symantec

mli7777's picture

Thanks for that thought.   Still a little confused.   I go look at it and it appears to have started not cleaning up a few days earlier.   I am fairly new to this company and we do IT for mid to smaller companies.   So it looks like we started getting a VM alert for this like I said a few days earlier saying it went from a status of Green to yellow and it was not till it went to red that we manually deleted it.   But from the tasks and events I don't see it saying that the remove snapshot failed ?

See attached.   Am I missing something ??   This is the first time the alarms started to email us.

Thanks

Mike

snapshothistory.PNG
Kunal.Mudliyar's picture

Please upgrade to

Backup Exec 2012 revision 1798 Service Pack 2

if not.

This has fixed a lot of Vmware issues.

Please monitor your backups after this.

Technical Support

Symantec

mli7777's picture

Is that what version this is ??   See attached.   It does not mention SP2 but has the 1798 .

 

Thanks

 

Mike

backupexecvers.PNG
pkh's picture

The .1244 means that SP2 has been installed.

Kunal.Mudliyar's picture

Yes it looks like SP2.

Also from the screenshot looks like BE is doing backups correctly and later removing snapshots too.

I did some reserch on that alarm, found this VMware KB

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2037464

Please see if this helps.

Technical Support

Symantec

mli7777's picture

I checked that out.   But we did have a snapshot there that was growing and taking up space.   So we are afraid it will one day take up to much space and effect all servers on that setup.

We did delete the snapshot and it is not coming back on  every backup but I expect it to come back sometime.  So starting some dialoge in case someone else has experienced this.

Thanks

Mike

 

Kunal.Mudliyar's picture

We had this issue and this was the fix

http://www.symantec.com/docs/TECH200709

Installing Hotfix 199866 and making registry changes , so in case if there are orphan snapshots left befind it will clean it up.

If you have upgraded to Sp2 , you should not face that issue.

In case you see the orphan snapshot coming back try the fix mentioned in the registry fix.

 

 

Technical Support

Symantec

mli7777's picture

Sounds good.

Going to make the regitry changes as they were set for defaults.   So going to try that.

I am assuming SP2 meets the minimum requirement it mentions ?

Requirements: Before making the changes listed in this technote, Hotfix 19986 (or later) must be installed on the Backup Exec server.

Thanks for the help.

Mike

Kunal.Mudliyar's picture

Yes SP2 includes that hotfix

Technical Support

Symantec

mli7777's picture

Cool sounds good.

Thanks the help.

Should not hear from me again.  :)

At least for this.

Mike