Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Overview of our setup...

Created: 25 Apr 2014 • Updated: 25 Apr 2014 | 8 comments

Here's what our setup looks like now.

  • Backup Exec will do a full backup of each server to a QNAP starting Friday night at 10pm.
  • When it is finished, it will start on the next server and so on.
  • When all are done (a total of ~2TB), a duplicate job will start Sunday night at 10pm to copy all of the server backups to the external USB (2.0) attached to the QNAP.
  • Each night (Mon-Thurs) incremental backups will run at 10pm and when finished copy the backups to the external USB.

After some testing, this looks like it should work. Is there anything else I should check? Thanks

Operating Systems:

Comments 8 CommentsJump to latest comment

CraigV's picture

Hi,

 

Only thing I can suggest would be:

1. Make sure any AV installed on the NAS isn't scanning the B2D folder as it can slow down backups.

2. If the QNAP can do iSCSI it might be a better option to look at.

3. Any AV installed on the media server needs to have the B2D excluded, and the BE services.

4. Make sure the server's NICs and the switch ports the QNAP is attached too, along with the QNAP's NICs are hard-coded to the fastest setting, ie. 1000MB FULL.

Thanks!

Alternative ways to access Backup Exec Technical Support:

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

nathans77's picture

Ok.

  1. No AV on the NAS.
  2. BE to QNAP is using iSCSI.
  3. We just setup SEPM 12.1.3 to exclude the NAS folder. B2D services are already excluded.
  4. Just made the change. Before, the server and QNAP were auto. Now they are as you said. Our setup is all routed on a ProCurve gig switch.

The duplicates jobs copy the backups from QNAP to the USB 2.0 drive (directly attached to the QNAP). I don't think there's anything else I can do for that to speed it up.

Thanks, CraigV! I'm hoping this will be a good start for our backups. We've been floundering for at least a few months. So if anything bad happens, we're hosed.

Windows Server 2008 R2 Datacenter with Backup Exec 2010 R3 SP4 and iSCSI connection to QNAP.

SEP and SEPM 11.0.7200.1147 thru 12.1.3001.165

CraigV's picture

...with iSCSI you might want to look at enabling jumbo frames to se what sort of performance benefits you can get out of backing up to the NAS. bear in mind this might ned up flat-lining the VM's performance, and if it ends up like this or is unacceptable, then disable it.

Thanks!

Alternative ways to access Backup Exec Technical Support:

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

pkh's picture

Why do you attach the USB drive to the QNAP?  Are you aware that during a backup the information will flow from the QNAP to the media then back to the QNAP again?  It would be better to attach the USB drive to the media server to lessen the impact on your network.  Also, by attaching the USB drive to the QNAP, it is up to you to ensure that it is online and available before the backup starts.  BE will not know the status of the drive, unlike if it is attached directly to the media server.

nathans77's picture

pkh - Our Backup Exec server is a VM on an ESXi. We backup to a USB 2.0 drive on another physical server (I assume you're calling this the media server?), but the speeds at USB 2.0 were causing issues completing in a week before the next one was to start. We currently have a QNAP NAS which does VM backups. So we did an iSCSI setup with the USB drive connected to the QNAP to test it out. We have a job to backup to the QNAP, then have a job to duplicate it to the USB drive. Plus the fact that Symantec said using Seagate USB drives are not compatible so we can't get any support beyond where we were at thus us going the QNAP route.

 

Here's the error we got over the weekend. The first job ran and finished 28 hours later. It seems the windows were missed.

e000e020 - The job was scheduled to run, but the availability window closed before the job could start. There may not have been any destination devices available during the window, or the job may have been submitted to run when the window was closed.

I'm going to create a policy that includes them all to see if that works. If that fails I'm at a loss as we're getting closer to a year of failed backups.

Windows Server 2008 R2 Datacenter with Backup Exec 2010 R3 SP4 and iSCSI connection to QNAP.

SEP and SEPM 11.0.7200.1147 thru 12.1.3001.165

pkh's picture

In BE terms, a media server is the machine which you load BE on. Using a virtualized media server to access real devices is also not supported. You should use a physical machine for your media server

nathans77's picture

Ok, I know according to some docs, it mentions BE should be installed with SEPM. So we'd have to move the entire server from the VM to physical. We'll see what we can do.

Windows Server 2008 R2 Datacenter with Backup Exec 2010 R3 SP4 and iSCSI connection to QNAP.

SEP and SEPM 11.0.7200.1147 thru 12.1.3001.165

pkh's picture

I know according to some docs, it mentions BE should be installed with SEPM

Which document?  I am not aware of such a requirement.  What happens if an installation is not using SEP?