Forum Discussion

Mike55's avatar
Mike55
Level 3
12 years ago

Moving / Backup of Bkf Files (Revisit)

I've was searching around looking for a better way or the proper way to transfer backups from one BE2012 server to another and found this post, "Moving / Backup of Bkf Files" https://www-secure.symantec.com/connect/forums/moving-backup-bkf-files.  I've been fighting with CAS/MBS replicated deduplication accross a wan with it's complex recovery requirements, instability and failures and I was looking for a simpler method.

After using 2012, I'm a little annoyed at what I just read in "Moving / Backup of Bkf Files".

Senario 2,
You backup to a fixed disk drive and regularly copy the b2d folder to a drive on a different media server  using explorer. However this media server runs it's own jobs.

Because this media server has almost certainly used the same bkf and img names already you get the same conflicts mentioned in scenario one.

Yeah, I bet it does cause problems in BE2012.  You see in 12.5 and BE2010 there's a section in the options called Media Management.  That's where I modified all of the file and folder prefixes that Backup Exec uses when I set up the application, so that I could give them a prefix unique to that BE server.  ex.  bs01IMG, bs01B2D, bs01"""", etc.  This allowed me to keep track of the source of my backups and also it meant that they were unique when read on a different independent Backup Exec server.  Another option in the same location, was the ability to set the next value for the file name, which could also be used to separate backups between servers if needed.

The more simplified BE2012 admin console doesn't have these media management options or I just can't find them.

So my question is, In BE2012 what is the proper way to transfer backups from one BE2012 server to another existing independent BE2012 server?  How does one make this material transportable so that it can be recovered elsewhere?  I'm not interested in solutions involving the creation of a empty server to be able to read one backup file.

The previous solution is reposted below:

Moving / Backup of Bkf Files

Colin Weaver Symantec Employee Technical Support Accredited
24 Aug 2011 : Link

A Word of Warning: Never copy B2D data files with Explorer - unless preparing for a DR situation (or a server migration) against the media server itself. As such Kiran's answer is a better answer than RahulGs

i.e. If you want to store backup data on a USB disk then you should put the b2d device on that USB disk and write the data directly to there with Backup Exec (either as a direct job or a duplicate)

If you copy b2d data around using Explorer and the run the inventory abnd catalog operations on media server that has been in use (so the database is not empty) then the existing b2d inventory in that database can cause problems.

There are at least two scenarios with Backup Exec that can cause problems  relating to this.

Scenario 1

You backup to a fixed disk drive and regularly copy the b2d folder to a drive on a remote server or a USB disk using explorer.

Backup Exec continues to write new data into the b2d folder and eventually overwrites some of the files you copied meaning the BKF and IMG folder names are the same but their content is changed. You then need to do a restore from something you manually copied away so you copy this B2D data back into a new B2D folder on the media server and then attenpt to inventory and catalog it.

This will either result in a conflict of two media with same name on the server, or if you thought of that and termporariliy removed the newer versions you will have problems as the content of the Backup Exec database maintains media familes and indexes that are aware of the state of the newest version of the media.and having the older version supplied results in inconsistent information.

Scenario 2

You backup to a fixed disk drive and regularly copy the b2d folder to a drive on a different media server  using explorer. However this media server runs it's own jobs.

Because this media server has almost certainly used the same bkf and img names already you get the same conflicts mentioned in scenario one.

Explanation:

Think of Backup Exec as being a very large relational database with 1 part inside the Backup Exec SQL Database, 1 part on the catalogs and one part actually being the media (BKF, IMG, OST, Tape)

Make any part of that inconsistent compared with the other two parts and you will have problems.

 

As such you can only reliably catalog copeid bkf and img media in the following situations

1) On the original media server when that media has not been used by later jobs

2) If later jobs have used the media, then on the original media server when every piece of media in that media family has been deleted from Backup Exec (not a good idea if the media your are deleting contains newer data that you might also need at some point)

3) In a DR Situation where a media server contains a brand new empty database

 

Note for a Full DR sitution your best option to remain consistent is

1) Make the Backup Exec Databse maintenance run after all your daily backup jobs finish.

2) Copy or backup the BEDB.bak created by the database maintenance, the rest of the data directory and the existing catalog folder and all your b2d locations to a secondary location.

3) Be prepared to put all this information back if yiou have a disaster.

 

No RepliesBe the first to reply