Is it bad practice to backup a backup(.bkf) file?

By DownRightTired ·
**(almost forgot to mention this is in a WS2k3 environment w a single DC)
I have a backup schedule implemented that backs up various databases and user files, as well as the system files for my PDC throughout the week onto a onsite file server. Then once a week my file server makes a backup of those backup files to an offsite NAS device. Is it a bad idea to make a windows backup of a windows backup (.bkf) file? Dont remember seeing anything about it, just has been in the back of my mind for a while.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

depends I guess

by lowlands In reply to Is it bad practice to bac ...

It's not bad practice to backup the .bkf file off site.
Having your servers backup old .bkf files could get somewhat redundant, but then again, better safe then sorry.

Collapse -

wasnt sure about restoring

by DownRightTired In reply to depends I guess

The offsite backup pulls about 6 .bkf files from the file server at one time creating one full normal .bkf file containing 6. Its only done about once a month. I just wasnt sure if there were any issues with restoring backup files from a backup file, you know? Thanks for the response

Collapse -

Well there are a few things that you need to look out for

by HAL 9000 Moderator In reply to Is it bad practice to bac ...

While in theory it's perfectly safe to do the proof is in the pudding as they say. Have you tried to restore from the Backup? Even if that actually works you'll need to try to restore to a different computer to see if that works most times it will not so the backup is useless.

The main problem with DR Plans is that no one fully checks them out and regularly thinks to check that the data is actually there and if there was a complete loss of hardware like in a fire is it possible to restore the data to new computers.

Things like that need to be checked regularly as things change and Hardware can fail along the way or you could get transmission errors creep into the off site backup which makes it useless.

There is really only one possible answer here an that is to actually attempt to restore the data to the computers and see if it actually works and then attempt to restore the same to different systems and see if it still works. If it doesn't you need to make some modifications to your DR Plan.

I do this religiously but then again I had one Government Agency perform daily backup and then take the tapes off site store them for 3 months and then dispose of the old ones meaning reuse them. But when the server died and destroyed everything in it i found that those religiously backup that had been performed daily where nothing more than blank tape because the Tape drive had failed about 6 months previously and as this wasn't considered as an Important job they had given it to the Security Guard who only knew what he was told to do push in the tape press these 2 buttons and then walk away. Which is exactly what he did and the tape only ran for about 5 seconds after he left. Though to be fair to the Guard if he had of been sitting beside the Tape Drive I don't think that he would have known any better.

The Moral of the Story is Check Everything and Keep checking!


Collapse -

on point

by DownRightTired In reply to Well there are a few thin ...

yeh i was also wondering wether i would be able to restore in the event of losing the hardware. I go back and view the backup files and it SEEMS everything is there though i havnt tried to restore it. I know theres a check box somewhere along the backup process that says something about only the administrator or owner having access, ive always left that unchecked.

Well im off to restore. Thnks

ps, cant help but laugh about the security guard incident

Collapse -

I can laugh now as well

by HAL 9000 Moderator In reply to on point

So I use it to show just how easy a mistake can happen.

But at the time it was a totally different story.


Collapse -

When isn't a backup a backup

by rustty In reply to I can laugh now as well

I love the storey of the security guard & the backup, & not unlike others whom have been in this game for 20+ yrs, I have a backup disaster story or 2 of my own.
For me the most memorable was the multinational client whom had his 2IC of IT purchased a new autoloader due to the early expiration of thier existing device.(with some haiiry mammal assistance)
It took 3-4 weeks to pick a replacement device. a further 2 weeks for the justification to be written and submitted.
1 week for delivery, and a further 6 weeks to unbox and rack up. Followed by another 6 weeks to calibrate the SCSI interface, this was then followed by a further 9 weeks to actually workout and implement a functioning backup schedule after he found that the version of backup exec he was trying to use was incompatible with the much needed robot drivers.
This client was a multination corp; it had taken 22 months to get a working backup hardware / software solution inplace. a further 18 months of prior failed backups ment that for 3.5 yrs this company had no reliable recovery or archive data.

Related Discussions

Related Forums