Video Screencast Help
Backup Exec

Backup Exec Service Packs Generally Available

Created: 23 Jul 2013 • Updated: 26 Jun 2014 • 56 comments
Drew Meyer's picture
+3 7 Votes
Login to vote

"Do... or do not. There is no try."

-Yoda

 

The Backup Exec team announces the general availability of the two Service Packs for BE2010 and BE2012 that bring support for Windows Server 2012 (via an agent), vSphere 5.1 and a host of quality improvements. Download right now from the TechNote or watch for the patch to be available via LiveUpdate in a few weeks.

Backup Exec 2010 R3 revision 5204 Service Pack 3

Backup Exec 2012 revision 1798 Service Pack 2

These releases mark a major milestone in our plan to restore delight in Backup Exec customers. We know they do not address every concern, but are continued proof of the Symantec commitment that started last fall.

We'd like to thank each of the more than 3500 testers who downloaded and participated in our largest beta ever run, and for helping us correct defects impacting over 1200 customer cases. We expect your experience to improve as it has for the beta testers and we invite you to continue giving us straight feedback on Reddit, Twitter, Google+, Symantec Connect or Spiceworks. If you need support, contact via one of the multiple alternatives to the telephone.

I'll close with some tester comments that came in just this week:

Beta tester quote: “Thanks for making the product so robust and reliable.  It’s great that my backups are all working so well after a long time of pain and failures.”
@jacob_ackerman: The #BackupExec 2012 SP2 beta went really well. We've been running it in our production environment with absolutely NO issues
@brandonmosak: Just finished patching my e14 farm to sp3 & ru1. Be2012 sp2 delivers on the promise. Everything backed up via VMware w/ GRT.

Please roll these Service Packs out! Let us protect your physical and virtual environments with improved grace and power. And thank you for your loyalty.

Drew

 

PS I am now moving to work on the NetBackup product line, but I expect my successor Amy Dugdale to be active and responsive in these same forums. You may always drop either of us a direct line at any time.

Blog Entry Filed Under:

Comments 56 CommentsJump to latest comment

xxcchhyy's picture

Agent for VMware notes

The following information applies to virtual machines that use Windows Server 2012 and VMware ESX/vSphere/vCenter 5.1 or 5.0 with Backup Exec 2012 SP2:

GPT disks are not supported.
 

 

I wait this service pack almost year, and still I cannot backup our vmware infrastructere with it...

-3
Login to vote
kuznetsovia's picture

+

The following information applies to Agent for VMware jobs regardless of the version used:

Conversion from a physical computer or from existing backup sets to virtual disks is not supported for VMware.
 

thist function was available in previous version of backup exec 2012 (sp1) or I miss something?

-1
Login to vote
uogsa's picture

This truly is unbelievable - "

"Agent for VMware notes

The following information applies to virtual machines that use Windows Server 2012 and VMware ESX 5.1 or 5.0 with Backup Exec 2010 R3 SP3:

  • GPT disks are not supported."

Come on, the use of GPT disks is becoming more and more common, especially with people using EFI where you don't have a choice!

 

-3
Login to vote
kml's picture

Hi,

can we apply this patch with Backup Exec 3600 R2 appliance ?

+2
Login to vote
ALiving's picture

Where's the multiple servers in one job feature that was promised?

+1
Login to vote
Brepols NV's picture

The only thing I noticed (and I'm not even sure it wasn't there already in the previous release) is that you can right-click a server group and create a backup job for all servers in the group at once.

This didn't do what I hoped for personally: I tried this on a group that had one Sharepoint server, and the Sharepoint Server Farm-item, and wanted to create one job that backed up the server itself, and the sharepoint environment for GRT recovery. I could create the job in one step, but I didn't have all the options available (only the options for the Server Farm were fully available), and once created, I saw that it created two jobs: one for the Server itself and one for the Server Farm.

Not really what I was hoping for :-)

-3
Login to vote
kuznetsovia's picture

this function was available in be 2012 rtm and sp1

 

the point is one job for multiple server like in be 2010, not one job per one server

-1
Login to vote
BJA32810's picture

 Case # 04824513

BE 2012 SP2 installed. My Symantec media   Attempting backup of Windows Server 2012 Hyper-V, it fails with the following error: The job failed with the following error: Resources specified for snapshot do not have any valid data on them. Check if files were deleted or renamed. 

 

Symantec Support has been SOOOO helpful so far.   

1st suggestion: Remove the server and recreate the job.  Brilliant. It failed with the same error.

2nd suggestion: Please ensure that the updated version of the Remote Agent is installed on the Remote Servers.  Brilliant.  I did update the remote server agent.  It still fails.

 

I suppose this is an improvement over my previous interaction with symantec support where they told me in no simple terms they weren't interested in helping me.  End of discussion.  Case Closed.

 

Did I mention I'm still getting this loveley message in Windows Server 2012 with the updated Agent software when it starts:

The application (Backup Exec, from vendor Symantec) has the following problem: Backup Exec is incompatible with this version of Windows.  For more information, contact Symantec.

 

WTF Symantec?  I thought Windows 2012 support for the remote agent and being able to backup Windows 2012, including Hyper-V was the whole point of SP2??

 

Way to go on delivering "Quality First" Symantec.  COMPLETE FAIL!

 

-2
Login to vote
Dave21's picture

Well done, BE Team. It's no secret how painful this release has been to get out the door, but you hit your revised shipped date, a key test of rebuilding trust, and started addressing some of the platform support issues.

However, now's not the time to rest: We still desperately need media installs on Windows Server 2012. At this point, I'm not even too fussed about GRT on the applications - I'd just be happy to see a working tape Drive in a 2012 server.

Once that's done, multiple servers to one job and job monitor are still MIA. (If you'd told me 18 months ago the User Interface concerns would be the least of our worries, I wouldn't have believed them...)

Please, please, please get a public roadmap (features and dates) out for Backup Exec 2012 R2 (?) as soon as it's feasible - You've hinted there could be something before 2014, but I can't take that to prospective customers. It's getting embarrassing telling them they're stuck on 3 year old versions of Windows, Exchange, and SharePoint because of the backup software.

We all want you to get this right: We complain because we care. If we didn't, we'd just up sticks and jump to VEEM or one of the other competitors. I want to be able to say, as I used to, that Backup Exec is the gold standard for backups, but at the moment, I just can’t.

 

+2
Login to vote
Brepols NV's picture

Some people were demanding Windows Server 2012 support since november 2012, which I found exaggerated: who wants to use a Server release that was only just released, in his/her production environment AND demand support from other products immediately...

But it's almost been a year now, and that's a bit long to say the least.

A roadmap would be very useful, like Dave21 said: IT administrators can then, at least, start to plan deployment of products that aren't yet supported by BE, and look forward to concrete new features. It would, also, keep customers calm(er), because they know exactly what to expect.

And, depending on how much symantec keeps customer feedback in mind: publishing a roadmap for a next release gives customers feedback in what features they think should at least get the next roadmap. This gives Symantec a chance to -probably- ignore most of the feedback, but also notice, if a lot of customers complain about a feature missing in the roadmap, that they might have to include it to stay on track of their current "customer satisfaction-route".

Or am I too naive for this job? :-)

+1
Login to vote
bandit61's picture

Another issue in Windows Server 2012: you have to set the BackupExec Remote Agent Service to startup Automatic (delayed) by yourself. Otherwise the service will not start, if you reboot Windows Server 2012. Do I really have to do that, or shouldn't Symantec update their install-script??!!

0
Login to vote
LilManTait's picture

Any idea on when SP3 will be released (to fully support Windows Server 2012)?

-1
Login to vote
JoseMan2's picture

How do i create a single job to backup multiple servers in Backup Exec 2012.

NB: backup to tape

+2
Login to vote
IMAWSON's picture

I updated to SP2 looking for the feature for mu,tiple servers one job  not there  maybe next SP?

Also now finding that jobs are running SLOWER than before

No going back   Mmmm 

Need to look at the market I think  a NEW Overland LTO-6 24 tape library and its slower on SP2 !!! 

I used to praise Backup Exec, recommend it everywhere    Not any more

 

-1
Login to vote
BJA32810's picture

Day 3 of trying to work with symantec support on case 04824513.

 

SP2 failed to install properly on my server.  it took two days for symantec support to determine this. In the about screen, Backup Exec showed Version 14.0 Rev 1798, however apparently not true.

 

Re-insatlled the service pack. Updated the agents on my servers.  Tried backing up Hyper-V again, and Backup Exec claims everything is fine.  That is until you try to restore.

 

What good is a backup that reports it completed successfully if you can't restore anything?

I can't restore the VHD/VHDX files.   I can't retrieve individual files using GRT.  Support appears clueless and wanted to close my case because Backup job says it completed successfully.  in fact the support rep even hung up on me when I was trying to explain the problem isn't fixed as long as I can't backup and restore hyper-v virtual machines. 

Restore 00058 -- The job failed with the following error: Failed to mount one or more virtual disk images. Backups that were enabled for Granular Recovery Technology may not be available for restore. Restart the Backup Exec Server to address this issue.
 

Reboot the server?  Wonderful advice Symantec.

Let me state again.  A backup is WORTHLESS if you can't restore any data from the backup job.

 

-1
Login to vote
Jaydeep S's picture

This certainly is most frustrating. I have requested internally to have the case escalated for a faster resolution. I have also sent you my direct email address via a forum message.

Does this restore error, occur on all the Hyper-V VMs or is it some specific machines that cause this error.

-1
Login to vote
kml's picture

I installed SP2 last sunday on a customer's environment and since that BE server crashs every night :/

Same issue as this technote ==>http://www.symantec.com/business/support/index?page=content&id=TECH205774

Beremote.exe crashs on bedsvmvcb.dll during VM backups. Backups of physical servers using agent are fine. First VM backup ==> CRASH

We have to reboot the server every morning since monday

Before SP2 we didn't have this issue. It was "fine" (except all the "regular" issues). I'll open a case tomorrow but i think i'll reinstall completly BE without SP2.

I thought SP2 will do miracles and fix everything (as the support keeps told me for weeks). A lot of work remaining.......

-1
Login to vote
lmosla's picture

Hey all, 

I understand the dissapointment and frustration that I am hearing when problems arise after installing the long awaited Service Packs.  Now that these different platforms are supported any issues can be addressed by Symantec Support Engineers.

Please DM me if there are any cases that aren't getting quality level support/attention

also available are Donald Eady and jaydeep S

+2
Login to vote
BJA32810's picture

It woudl be great if your support engineers did some actual work instead of constantly escalating the case.   I'm on Escalation #3 now and still no where close to finding a solution to restoring a windows 2012 hyper-V VM from tape.

At this point I'd be happy to just get the VHDX file and be able to mount it myself in dism to get the files out.   This is completely inexcusable that I can't get a tech on my case that knows how to troubleshoot a problem.   

My Problem is restore from TAPE.  I don't use backup to disk because I have way too many VM's and no where near enough storage on my Media Server to backup every VM to disk.

Can anyone explain why tech support has me chasing diagnostics on backup to disk? instaed of looking at the features I'm actually going to use in real life?

If I can't restore a VM from Tape, Backup Exec is a worthless product to me.

Case # 04824513 - opened on July 29.   today is August 8th and I'm not any closer to having real protection of my Windows 2012 Hyper-V VM's.  My only option is to backup the data in the VM as if it were still a physcial server.  

 

 

-1
Login to vote
Steve Y's picture

BJA32810 issues was resovled  per Microsoft registry change.

 

Hyper-v 2012 backup fails with the error "Failed to mount one or more virtual disk images"
http://www.symantec.com/docs/TECH207309
 
Hyper-V Virtual Machine(s) fails to start with the error "An error occurred while attempting to start the selected virtual machine(s)" after Backup Exec is installed on Windows 2008 R2 Host machines.
http://www.symantec.com/docs/TECH124353
 
Error message when you manage a VHD file in Windows Server 2008: "A Virtual Disk Provider for the specified file was not found”
http://support.microsoft.com/kb/2013544
 
+3
Login to vote
Andrew Wiggin's picture

Thanks for posting this. Too often problems are posted and solutions get neglected.

-1
Login to vote
BJA32810's picture

I can verify that one simple Regedit, described in KB2013544 fixed my problem with GRT restores from VHD/VHDX.  It also seems to create issues with backup to disk jobs, which I wan't planning on using anyway.

 

What I find amazing is the fact it took 3 escalations and repeated posts on these boards to get to this simple fix.

 

I find it more amazing that Symantec claims this "bug" is Microsoft's problem.  However microsoft clearly states in the KB:

There is a timing issue with FSDepends.sys and with VHDMP.sys. This timing issue occurs when certain backup programs are installed on computers that are running Windows Server 2008. By default, the FSDepends.sys start value in the registry is set to Manual. When any third-party backup software loads its tape device driver, the software can sometimes result in FSDepends.sys and VHDMP.sys not initializing correctly.

 

So basically when you install Symantec Backup Exec on Windows Server 2008/2008 R2 it breaks the ability to mount a VHD file on that windows server.  If Backup Exec is never installed, the feature to mount VHD's is never broken.  But this is a Microsoft Bug!

-3
Login to vote
HienV's picture

I have a problem restoring individual exchange 2007 mailbox with symantec 2012.  I worked with your level one and level two technicians but the issue couldn't be resolved.  I was wondering if you can help me resolved this issue so I don't have to go through this again in the future.  My email address is hienv@ths-wa.org or I can be reached at 206-323-0930 x229.  Previous Problem Case # 04896145

Thanks,

0
Login to vote
phil57's picture

Hi guys,

I have seen a lot of feedback on BE 2012, but how is the situation with BE 2010 R3 SP3?

I have an Exchange 2007 and BE 2010 R2 and I plan to upgrade to Exchange 2010 SP3 and BE 2010 R3 SP3 but I would like to know if anyone is suffering issue before doing it.

 

Thanks.

-1
Login to vote
Giacco's picture

Hi guys!

 

One question: When could I install Backup Exec Server 2012 on a Windows 2012 Server?

 

Thank you very much!

-1
Login to vote
Jaydeep S's picture

This will happen in the next releases of BE. There is no information about the eta of this next release/patch at this time.

-3
Login to vote
emmnet's picture

I am using BE 2013 R3, for sometime time my backup keep on failing with the below error message

The request could not be performed because of an I/O device error.
V-79-57344-33992 - The backup storage device has failed.

Can some please help me
 

-1
Login to vote
Jaydeep S's picture

Check if you are getting any Hardware related event ids like 5, 7, 9, 11, 13 in the Windows event viewer. Also, it would be helpful if you submit a new thread for this issue as the error might not have to do anything with the service pack and more generic in nature.

-1
Login to vote
emmnet's picture

please find below error message in event viewer

180px_BackExec Error_0.PNG

-1
Login to vote
Nas Khoodoruth's picture

Simplified Disaster Recovery is not yet supported for Windows Server 2012sad

-1
Login to vote
mtkinf's picture

I'm not going through that SP1 debacle again. This time, I'm waiting for SP2a before proceeding. Lesson learned.

-1
Login to vote
Zinc666's picture

Sorry to hear some are still having problems with BE 2012.  We're on BE 2010 R3 SP3 and haven't had any issues backing up from Windows Server 2012 or Exchange 2010 SP2, although we're not doing anything fancy with VM backups.  We hope to move to Exchange 2010 SP3 soon.

+2
Login to vote
MrK1024's picture

Thanks, Zinc666.  It's nice to hear about your positive experience.

-1
Login to vote
Andrew Wiggin's picture

I've also had good experiences with 2010. I am looking forward to installing this service pack. And, maybe by the time my environment needs v2012, it will be patched to a point where I want to use the new interface...

-1
Login to vote
MixedMindz's picture

I'm surprised anyone still uses Symantec for anything other than a legacy environment.

Server 2012 came out a year ago. To say this functionality in BackupExec is late is being more than nice.

If I waited for this ServicePack I'd be out of a Job. (and I'm finding tech support much more timely and usefull with my new backup vendor.)

By The way, How's Exchange 2013 support coming along? (and yes I mean GRT)

Get in the game or get out of it.

 

 

0
Login to vote
RussKincaid's picture

Why am I getting a 403 error trying to download from the Technote?

-1
Login to vote
lmosla's picture

RussKincaid, 

Which Technote are you attempting to download? Try again maybe with a different browser or clear your cache.

-1
Login to vote
drmont1's picture

(Bit of a long read, but I think worth it...)

So I have been using Backup Exec for my entire career in IT - since 1994. I think that is why the product exists today. If it were not for people using what they have been for so many years I think that the product would be completely dead. Not having features released - AT THE SAME TIME as the OEM is not competetive. Symantec, like other major ISVs, has access to Microsoft Betas long before anyone else - for the very purpose of being able to co-release software. Microsoft wants third party support day-one so that they can facilitate a faster adoption rate.

I just renewed and upgraded all of our systems to support the V-Ray licensing model and it + 2 years of maintenance bundled together cost our company a significant amount of $ at my recommendation. I could have recommend CommVault - which I have used, and who now has a mid-market license model that is competative with BackupExec. I have used NetBackup before and I find that for the marginal improvements over BackupExec it provides, its interface is difficult and it is a bear to troubleshoot. Thus, I stay with BackupExec.

I have had many vendors tell me "BackupExec is a dead product". I don't believe that - I think there is a good foundation from many years of positive capital and ease-of-use that the Symantec BE team can build upon. There are still many engineers in my field who are giving BackupExec a last chance over the coming years. But as annual renewals come due, it is always a time to reconsider.

Therefore, while it is my inclination to remain with the product, and my plan to do so for the next year or two, if features are not delivered quickly with stablity I am afraid that the extra cost of going to CommVault or another solution will self-justify themselves to me and my management. Backup Exec is NOT a dead product, and provided Symantec continues to provide funding to the product line (and not siphon all of the maintenance $ into the corporate profits) I think BE can catch up and even surpass similar products. ArcServe is still inferior and CommVault will always be superior in some ways due to its cost, but BackupExec has always held a place inbetween the low and high end.

We need:

1) Support for Windows 2012 R2 - on DAY 1. We plan to migrate to R2 day-one because of it being more an incremental release. We need many of the features it has, especially Hyper-V replica async repl. control. Start burning the midnight oil and bring in extra hands if need be to support this and I think the BE team can recover from the year-long delay in supporting 2012 R1.

2) BE R2 for 2012 BE install support soon - by October would be great.

3) Polishing of SP2 with maybe an SP2a rollup at the end of August.

4) Tape is NOT dead - so don't ignore it. It is not going to be dead anytime soon. In fact, tape purchases bottomed out a year or two ago and are now back on the upswing. Why? Because storing archive data for infinity even on deduped disk is much more costly than throwing it to tape.

5) Increase the 64TB dedupe store limit to 128 or 256TB - 4TB drives are cheap and building a DAS 288TB BE device is easy. Yet we literally have to buy extra media servers due to this limit.

 

+1
Login to vote
Amy Dugdale's picture

As Drew mentioned in his original post, I have recently taken over his responsibilities for Backup Exec. I hear you and understand your frustration. We’ve captured the features you want and those are top priorities for upcoming versions. We have brought in extra hands and are burning the midnight oil so that we can make this right for you and all of our customers. Your points are well taken and we would like to discuss them with you further. I will private message you now to schedule a call with me and a senior member of our product management team.

-1
Login to vote
Chuck Bridgeland's picture

Any chance this will resolve the problem with BE2012, SBS 2011 and Dell Rd1000 cartridges? 

https://www-secure.symantec.com/connect/forums/can... (Cartridges can not be moved from Windows NT backup media set, and fill up.)

-1
Login to vote
Martinus-Apotheke's picture

BE2012 menu feels somehow faster now and more responsive -> Good

But still no possibility to setup a hourly incremental backup job from lets say 9am to 9pm -> not good

I have to create one job for every hour (13 different jobs) to cover 9am to 9 pm -> still not good

This used to be in BE2010 and older versions...

-1
Login to vote
ThomDav's picture

Hi everyone,

I already installed BE 2012 SP1 on my server in April of this year but I have to wait because BE 2012 SP1 doesn't work with VMware vSphere 5.1

Now, the BE 2012 SP2 is ready. What is the best way to install this new release on my server (Windows Server 2008 R2 ) ?.

Thanks you for your advice !

Best regards,

Thomas

 

 

-1
Login to vote
Donald Eady's picture

ThomDav, 

 

       Sorry for the late response... if youre media server has internet access you can just run LiveUpdate and get ahold of SP2 that way this would probably be the easiest way to do so..

 

You can also find the downloadable for both SP2(2012) and SP3 (2010) at the link below

http://www.symantec.com/business/support/index?page=content&id=TECH66724

I hope this posting was helpful

  

-1
Login to vote
ThomDav's picture

Hi Donald,

Thanks you for your reply.

I already download BE 2012 SP2 and copy ISO file to a DVD.

I try to read the Quick Install but it didn't talk about how to install SP2 over SP1. This is the same guide that help you to install the SP1 or SP2 for the first time on a server.

In my case, should I uninstall BE 2012 SP1 first ?. If yes Symantec can give us the process to do ?

 

 

-1
Login to vote
Elias AbuGhazaleh's picture

Simply run SETUP.EXE and it will automatically detect that this is an upgrade situation.  Follow the on screen instructions to properly upgrade to SP2.

If you uninstall SP1, you will lose all of your settings, jobs, history, schedules, etc. (Not recommended)

-1
Login to vote
BJA32810's picture

Simply run SETUP.EXE and it will automatically detect that this is an upgrade situation. Follow the on screen instructions to properly upgrade to SP2.

If you uninstall SP1, you will lose all of your settings, jobs, history, schedules, etc. (Not recommended

 

This is not true.  I downloaded the full ISO and ran setup.exe to upgrade my BE 2012.  It appeared to go through the process, but then it did not register that SP2 was installed after it was completed.

After trying some backups, they failed, and I had to open a ticket with support to get the problem resolved.  They made me reinstall the standalone patch, not use the ISO.

+1
Login to vote
Elias AbuGhazaleh's picture

That of course should not have happened.  Can you send me your support case ID that you opened, I'd like to follow up on this with our support group to find out what was going on.

-3
Login to vote
BJA32810's picture

case: 04824513

 

It took tech support three days and they finally advised me to install the patch from the attachments at the bottom of this tech note:

http://www.symantec.com/business/support/index?page=content&id=TECH203155&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1376655817867cslqW9LU2A0dlR7zr3RJk3Plg22bSKo212lal

 

That resolved the backup errors when running a Hyper-V 2012 backup job, however it was still nearly two weeks before someone came up with a fix that allowed me to restore from a Hyper-V 2012 VHDX.

 

Even Live update was not finding the patch immediately after release was made public.  I would hope it is by now, but when you've been waiting for support for Windows 2012 Hyper-V for over 7 months, you don't want to wait for a patch to show up in live update.  

 

-1
Login to vote
ThomDav's picture

Hi BJA !

Thank you for sharing your experience, it's great to know that didn't happend like the process of Symantec.

For me, BE 2012 SP1 is already installed and I don't want to lost my time in the update process. So that why I ask this community to know the feedback on this process SP1 -> SP2.

Live Update look so easy, I'm little bit afraid !

Cheers,

 

 

 

 

-1
Login to vote
Elias AbuGhazaleh's picture

ThomDav,

You can download the full product (full ISO) either from Fileconnect (https://symantec.flexnetoperations.com/control/symc/registeranonymouslicensetoken) where you have to supply your serial number

OR

Download it from our Trialware site (http://www.symantec.com/products-solutions/families/trialware-popup.jsp?fid=backup-exec) and use your license key during the installation.

Download from either one of these links will provide you Backup Exec 2012 SP2, and just to confirm it has support for VMware vSphere 5.1.

On the server that you have Backup Exec 2010 SP1 installed, you can simply run LiveUpdate to download the patch and perform the upgrade.

-1
Login to vote
ThomDav's picture

OK thanks you very much !

-1
Login to vote
ThomDav's picture

On the server that you have Backup Exec 2010 SP1 installed, you can simply run LiveUpdate to download the patch and perform the upgrade.

 

I confirme that it's the right way to do. I try it and get BE 2012 SP2 on my server Windows.

Thanks again !

 

-3
Login to vote
Elias AbuGhazaleh's picture

Thank you for the confirmation ThomDav.  Glad to hear you were able to upgrade.

-3
Login to vote
ThomDav's picture

Hi everyone !

I use Backup Exec 2012 SP2 with a tape library HP (24 slots)

- Cartridge 1 in Slot 1, Cartridge 2 in slot 2, ...., Cartridge 20 in Slot 20.

- Slot 0 reserved for Mailslot.

I want to create backup with the following strategy:

  Monday Tuesday Wenesday Thursday Friday
First week Cartridge 1 Catridge 2 Catridge 3 Catridge 4 Catridge 5
Second week Cartridge 1 Catridge 2 Catridge 3 Catridge 4 Catridge 6
Third week Catridge 1 Catridge 2 Catridge 3 Catridge 4 Catridge 7
Fourth week Catridge 1 Catridge 2 Catridge 3 Catridge 4 Catridge 8

I also create media set "Monday" and associate with Catridge 1

I try to set up my first backup of Monday and use the media set "Monday".

BUT, my backup is stored in Cartridge 6.

Anyone how to force a backup to use media that located in a media set ?. For my case what I want is:

Backup Monday (1st week)        ->  Cartridge 1

Backup Tuesday  (1st week)      ->  Cartridge 2

Backup Wenesday (1st week)    ->  Cartridge 3

Backup Thursday  (1st week)     ->  Cartridge 4

Backup Friday  (1st week)         ->  Cartridge 5

Backup Monday (2nd week)        ->  Cartridge 1

... so on.

 

Thanks you for you help !

 

Thomas

 

 

 

 

 

-1
Login to vote
angexpress's picture

Our company upgraded from Retrospect to Backup exec 2010 just before 2012 was released.  When 2012 was released we went ahead and did the upgrade which was a visual upgrade but lost some key features which ended up feeling like a downgrade.

Here are the issues I'm still dealing with:

1. On occasion Backup exec felt that it should take a tape from a different set and record to it.  I ended up Partitioning my tape library to prevent this after a few heart attacks

2. Can't backup multiple servers from a single script (come on)!!!

3. Backup to Disk doesn't overwrite when it fills up.  I find that I have to manually delete the older backups so it can continue backing up

I'm wasting so much time looking at the backups and fiddling that I'm patiently waiting to see what Backup exec does by end of year, if I don't see anything come out to make my life easier, I'm dumping it and upgrading my old Retrospect software.

Angelo

 

 

-3
Login to vote