Video Screencast Help

How to create single pass backup in BE?

Created: 23 Mar 2012 • Updated: 27 Mar 2012 | 5 comments
This issue has been solved. See solution.

I've read much of information about Symantec doing the single pass backup.

However I cannot find something similar in my Backup Exec and at this point I cannot understand what checkboxes to select.

And moreover - am I correct understanding that BE will make an image of my physical machine and then allow me granular recovery of my SQL databases? If it is not possible - probably I misunderstood the idea of that single pass backup.

Comments 5 CommentsJump to latest comment

CraigV's picture

...by a single-pass backup, I suspect it means a backup of a VM with everything in it. If it has an application like SQL installed, and you have the SQL agent on your media server, then it allows you to do a GRT restore from the backup it created.

For normal physical servers you'd have to look at IDR, or backing up normally.

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Nene's picture

Hi CraigV,

I am interested in your response to IvicaB.

When you talk about IDR, how do i use it when i need to restore my server?

Thank u.

Ken Putnam's picture

See the 2010 Admin Guide page 1748

If this response answers your concern, please mark it as a "solution"

pkh's picture

For physical servers, it is possible to backup all your flat files and SQL databases in one job.  You just select all your files and all your SQL databases.  However, this is not recommended as you would need to turn on AOFO to backup your flat files and you should turn OFF AOFO when you backup your SQL databases.  So in practice, you need at least 2 jobs; one with AOFO on to backup flat files and another job with AOFO off to backup SQL databases.

 

FYI, when you use IDR to restore your servers, it does not restore SQL or Exchange databases.  These databases need to be restored separately after the server is restored using IDR and then re-booted.

SOLUTION