Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Basic Disk storage unit and deleted images to import

Created: 11 Jul 2013 • Updated: 16 Jul 2013 | 8 comments
This issue has been solved. See solution.

Hello,

I would like to test import fonctionnality on Netbackup 7.1.0.3  on a basic disk storage unit when an image is deleted from the catalog (expired manually), and when all files related to this image have been first copied to another directory (outside the basic disk storage) then deleted from the basic disk.

How can I import this specific backup image ? I mean when you run action / initiate import, you have to specify the path . If I specify the path to the storage unit, will Netbackup try to import ALL images, even images already known in the catalog ?

I.E : basic disk storage unit path is /netbackup/das/disc01

And image-to-import files are in /netbackup/image-to-import directory

If I specify  netbackup/image-to-import directory when I initiate import, phase I and phase II import are successful, but the files cannot be moved to /netbackup/das/disc01 (if I do that, I get media error when I verify this image)

Thank you

Operating Systems:

Comments 8 CommentsJump to latest comment

Nicolai's picture

How to import disk images into VERITAS NetBackup

http://www.symantec.com/docs/TECH43834

The TN mention NBU 6.0 but I believe it's still valid

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Mark_Solutions's picture

Things tend to work better when the folder specified is already a storage unit

So either make the new folder to be a storage unit already or just copy the files back to the original disk storage unit.

When you run the import it will read all images in that location - any it already knows about it will just skip through and only actually import the ones that it doesn't have in its database

If you have also duplicated the images to tape then the image already exists (copy 2) so you would need to run the phase 2 import of the disk images from a command line using the -cn 1 switch (bpimport -cn 1)

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Marianne's picture

If I specify  netbackup/image-to-import directory when I initiate import, phase I and phase II import are successful, but the files cannot be moved to /netbackup/das/disc01 (if I do that, I get media error when I verify this image)

Pretty much expected, right?

If you wanted the images in  /netbackup/das/disc01, you should've copied it there in the first place and imported it from there.

The path where data resides is part of the catalog entries.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

mph999's picture

"How can I import this specific backup image ? I mean when you run action / initiate import, you have to specify the path . If I specify the path to the storage unit, will Netbackup try to import ALL images, even images already known in the catalog ?"

Yes, it will look at all images, but if they exist in the Catalog will simply skip them.

"If I specify  netbackup/image-to-import directory when I initiate import, phase I and phase II import are successful, but the files cannot be moved to /netbackup/das/disc01 (if I do that, I get media error when I verify this image)"

Correct, it will fail.  As Marianne stated above, put the images in the path that is defined as the STU.

Martin

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
SOLUTION
Marianne's picture

I'm curious - what is the purpose of this exercise? 

You won't move contents of tape around outside of NBU, right?
Why do you want to do it with DSU?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

mph999's picture

Maarianne makes a good point  - I think I see in this case that you are doing DR and just asking a few questions which is fine.

The folowing is not directed at you, it is simply a bit of advice.

Do not start introducing STU paths into the system that were not there before.  OK, it's fine for a test but should not be done in real DR, or any other time.  That gets rid of the point Marianne is making about moving images about.

Can it be done, yes it can, ... but with all good intent, people they go on to make more adventureous  'changes' that are outside what you should really be doing, and once into this habit, its a downward spiral.

Why do I mention this, simply because it leads to broken systems ...

I think now I've seen most things done, and the results of not readng and following what's in the manuals have been from a few failed  backups to complete loss of every backup in the environment.

I have a simple rule - if it's not in the manuals you don't do it because it's unsupported.  Sure, people come up with 'exceptions' and better ways of doing things, that's fine, but discuss it with us first (i mean Symantec support  ) and get an ok nod it's safe to procede.   Otherwise you risk the infamous "It's not supported" comment.

I do appreciate that you have taken the time to ask advice, and as I said, the comments above are meant generally.

Of course, playing on a test system, do what every you want, that 's the way to lean safely - but be careful of what could be unsupported actions on live systems.  I've seen things put in place that appear to ork, but cause devastaing results further down the line.  

You have the advice of x3 of the top skilled members on this thread, Marianne, Nicolai and Mark and they are all suggesting the same thing ...

Martin

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
DavidE31's picture

Thanks all for your replies

The purpose is that we've been asked to protect a VERY IMPORTANT full backup of a system, in case we need a restoration in a few months, from this specific backup ONLY.

That's why I've done the following :

- extended retention period of this backup image to 6 month

- duplicated this backup image as copy 2, retention period 6 months

And to prevent the fact that somebody would expire these images and leave us with no data to restore, I made a copy of the image related files to another directory, tar them and protected the tar file onto another server ... :-)

I tried to imagine how could I reimport the files extracted from the tar file if backup images would have disappeared. I don't mean to create another Storage Unit to import the files as the master server is in a production environment and don't have to be changed, but I was not sure how phase I import would act if I specified the DSU path to import, and you gave me the answer, thanks again. Now I have to validate how much time it will take to reimport only one image when all the DSU specified in the path field is read by NBU

By the way, I didnt mention that for this NBU environment, we dont have LTO devices, we only backup on disks, that's why I tried this tar file solution ...

mph999's picture

That seems reasonable, given the requirements.

M

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805