Video Screencast Help

Catalog size is increasing

Created: 09 Apr 2012 • Updated: 15 Apr 2012 | 31 comments
PhaniKumar82's picture
This issue has been solved. See solution.

Team

 

we have installed Netbackup Master server in  D drive which has 207 GB of capacity  of local disk 

But now the issue is /netbackup/db/images folder is occupied 170 GB out of 207 GB and it is increasing day by day very quickly 

 

how to proceed for the above issue because now very low space 30 GB is free now 

 

Regards,

Kumar 

 

Comments 31 CommentsJump to latest comment

revaroo's picture

1) Increase Disk Space

2) Review Retention periods in your backup policies, see if you can lower the retentions of any.

3) Look at catalog archiving

4) Look at catalog compression

Voila

Have a read of this:

Recommendation for sizing the catalog

http://www.symantec.com/business/support/index?pag...

 

PhaniKumar82's picture

first two options wont be possible because existing disk is local disk so even if we increate it also future again it will be occupied and second option also not possible because its customer recommended retention policies 

 

can you explain me about catalog archiving and catalog compression

will there any impact if we doing catalog compression or archiving ?

Regards,

Kumar

 

Nicolai's picture

How to move NetBackup database from C drive (C:\) to D drive (D:\) on a windows master server

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

Personally I go for a disk space increase. 

Assumption is the mother of all mess ups.

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

PhaniKumar82's picture

Do we need to create ALTPATH file each and every client ? or can we create single file for all the clients which are under /images  folder ?

 

Regards,

Kumar

sazz.'s picture

Yes, you have to create it for each and every client.

PhaniKumar82's picture

Then it is very difficult to crate ALTPATH for each and every client becuase in my environment almost 500 + clients are there and it is very difficult to create 500 + ALTPATH files in every client ...

Marianne's picture

For 500 clients your catalog is still fairly small. Seems calculations were not done upfront to ensure sufficient catalog space.

On Windows Master server you need to relocate clients one-by-one and create ALTPATH file in original folder. Start with clients that occupy most space - normally File servers.

On Unix Master servers all images can be relocated as a whole and symbolic link created to point to new location.

Moving images to new drive seems like your best option.

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

PhaniKumar82's picture

hi

is the following method is correct or not which has mentioned by "sesabstian" 

 

 

You can also add a new disk/storage to your Windows Master Server, create the folder with all images on that disk (let's say: e:\Program Files\Veritas\NetBackup\db\images); take a full backup of your catalog, stop all NetBackup services; copy all images from c:\Program Files.... \images to e:\...images; remove or rename the images folder in the original location; run the following command: 

mklink /d images e:\Program Files\Veritas\NetBackup\db\images

 

The command above will create a link to a new location. From the perspective of the Operating System and NetBackup it the images folder under c:\ will access directly images stored under e:\.

 

Regards,

Kumar

mph999's picture

Catalog compression will only give you some more time, it will still fill up eventually.

The best option would be to design the system correctly in the first place, with enough capacity to run for xx time before needing more space.  It is also recommended to install NBU on a different drive than C:\

The next best option would to increase disk space, but I understand this is not possible.

Therefore your best option is to archive the catalog - this copies the .f files (the big part of the catalog) to tape, and then deletes them.  The downside is that to restore a clients files, you first have to restore the .f files.   This is not a big issue, but is another complecation.  The trick is only to archive the catalog for say xx months back, that way, as you probably usually restore from backups in the the past weeke or two, you will hopefully not have to restore the archived catalog too frequently.

The steps to archive are in the Netackup Admin Guide - although quite simple, it is easier to read the manual as opposed to typing out the steps here.

 

martin

 

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

Hey Mate,

 

You can also add a new disk/storage to your Windows Master Server, create the folder with all images on that disk (let's say: e:\Program Files\Veritas\NetBackup\db\images); take a full backup of your catalog, stop all NetBackup services; copy all images from c:\Program Files.... \images to e:\...images; remove or rename the images folder in the original location; run the following command: 

mklink /d images e:\Program Files\Veritas\NetBackup\db\images

 

The command above will create a link to a new location. From the perspective of the Operating System and NetBackup it the images folder under c:\ will access directly images stored under e:\.

 

Hope it helps

 

Sebastian

 

Sebastian Baszczyj

PhaniKumar82's picture

Are you sure about this because there should not be any issue in future when we got any restore for old clients and also please let me know how to reverted back if it is not working ....

 

Regards,

Kumar

mph999's picture

mklink /d images e:\Program Files\Veritas\NetBackup\db\images

This would be unsupported and should not be done.

The correct resolution is either :

1. Add more disk space

2. Add separate 'disk' and mount in place of images dir (need to copy across files from old area)

3. Use ALTPATH

Using an 'unsupported' method may work, it may not.  It may also work and then due to the method used cause issues in the future, which in this area if that happened could well lead to data lose for which Symantec cannot be held accountable and may well be unable to fix.

I see many issues where people make 'hacks' to systems that don't work because they weren't designed correctly.

This issue comes down to design - there was no 'capacity' planning carried out for a start, and as already mentioned, it is not a good idea to install NBU on the system disk.

Martin

 

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

If you see the Marianne van den berg note this can be done on UNIX using soft link 

i think soft link concept is not there in windows till 2008 but from 2008 onwards we can use soft link 

using mklink command so in this case is there any issue if am using nklink command because i have tested on test machine it is worked fine and even i have tested restore also it was succussfull 

the reasong why am asking about this is we have E drive which came from SAN and it can be extended even in future but right now veritas installed on D drive which is local disk and can't be extended 

so using mklink if we move images to E drive then again in future also we can extended it ...

 

is there any other issues while using mklink concept ? if so please explain me so that will choose better option 

 

Regards,

Kumar

 

Sebastian Baszczyj's picture

Hey Mate,

 

This method is described in the HA Admin Guide. I agree - it is for slightly different purpose (just to have images and databases on another drive to allow replication of the drive to another site) but the goal is the same. If it is supported for clustered solutions, I don't see the problem to use it in production. 

 

S

Sebastian Baszczyj

mph999's picture

OK, you have 100% ignored my advice.

If you do this and there are issues, you may lose data - simple.

This has NOT been tested by Symantec, and therefore is unsupported.  The reasin it is unsupported is simply becuase we do not know what will happen and canoot promise that it will work.  Sometime things that are unsupported sem to work fine, until you get a specific set of circumstances that causes a failure.

I sent marianne an email about this - here is her reply to me :

"I am 100% with you on that one.

If it’s not in the manual or in a TN, it’s not supported. End of story.

No guarantees that catalog backup would follow the link or that 7.5 upgrade will work."

What Marianne is saying, and me  - is that if it is not listed in the manuals then it should not be done IF you want Symantec to support you.

You know, the biggest issues I face, and I do this all day, every day - are issues with systems that do not work, where the fix has been 'hacked' and  is unsupported.  Then the customer complains it does not work and gets upset when it cannot be fixed.

It is not our fault that the system has been poorly designed - just becuase the correct action to fix it is difficult, does not mean it should be discounted.

Persoanlly I would look to get the system rebuit if possible - the design is not good, and I  suspect that in the furture you may face other issues.

And yes, I see systems that have issues day in / day out that cannot be 'fixed' because they were simply built wrong/ are underspec'ed etc ...  These system run with continuous problems/ regular failures and this is NOT the fault of the software.

I suggest you take the advice of people who know what they are doing.

In fairness, I will add - I am curious myself as to why the windows link is unsupported, perhaps it should be as it would be a simple solution. But, going on how the situation is at the moment,  I have given the correct advice.

If I were an adminstrator, I would not go against the advice given to me by the company that provides the software.

Martin (Senior UK Symantec Engineer)

 

 

 

 

 

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

Hey Mate,

 

Check p.58 in High Availability Guide for 7.1. 

This method has been tested and it's working fine in 100TB environment. 

S

Sebastian Baszczyj

Marianne's picture

As you know by now, Martin and I have been discussing this via email.

IMHO, it may work, BUT, because it has not been tested and documented by Symantec Engineering, it is unsupported. My biggest concern is as per quote above - what about catalog backups? Will it follow the link? how will catalog restore work? Will 7.5 upgrade work with relocation of image header files?

When it is tested and documented by Symantec Engineering, you will have the assurance that all of the above will work and that you will enjoy technical support should any problems be experienced.

SUGGESTION:

Post 'Request for enhancement' in Ideas section of this forum : https://www-secure.symantec.com/connect/backup-and...  

Please post link here after you have done that - I will be first to 'vote'.

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

PhaniKumar82's picture

Sure i will check with symantec today and update you all 

sinc the above which i have mentioned is not tested on live environment and i have tested on test environment only 

 

Regards,

Kumar

mph999's picture

To save you the bother of logging a call, I work for Symantec as one of the NetBackup Engineers.

Additionally, I have just gone as asked one of the Backline engineers about this - they gave the same answer, that is, it is not supported and should not be done.

Why do you tthink I am giving this answer, and spending lots of time doing so - it is easy for me to say .. sure, you go ahead and fix it with links, but no, I am having to fight to put my point across, to give you the correct answer.

Look at it this way ..

If you go via a supported method you will have no isues - we know it works.

If you go via this new method and in the future you have a issue casued by this and you lose data, then what ?  Exactly how do you explain that to your manager ?

Regards,

Martin

 

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

Yes Martin 

 

i got your valid point ..now tell me what other option you want me to try 

1) adding local disk is not possible because it does not have free clot array controller ...

2)  changing rention policy not possible  because its client requirement

which is the best option you want me to choose apart from the above ...

also we don't have any tape library environment and we have only Data domain 

if you want me to go for catalog archiving or compression ?

 

Regards,

Kumar

mph999's picture

Hi Kumar,

I think given the issue - you would have to use archiving.

Thanks,

martin

 

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

To build a new server with plenty of disk space. Catalog archiving is only a work around - it not a fix.

With 500+ clients (and growing ??) this will be a constant issue -  You need to solve the root cause.

 

Assumption is the mother of all mess ups.

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

mph999's picture

Yes, I agree with you also, but given the options at the moment, archiving is probably the best,

I think this should be treated as a workaround and used while a proper design is created which  I understand is very difficult in a live situation, but if this server runs into issues in the future, the pain now of fixing it properley is a lot lot less than the pain of the issues you could face.

The key to any backup environment using any backup software working properly, is design.

Martin

 

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

My message was intended for Kumar not to you. Sorry for the unclear post crying

Assumption is the mother of all mess ups.

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

Sebastian Baszczyj's picture

Hi Marianne,

 

The link created that way works identically as on softlink on Unix. 

The Catalog backup is working fine,

The upgrade to 7.1.0.3 worked fine

There are no performance related issues

I will test upgrade to 7.5 soon, but I don't envisage any issues. .... 

 

As mentioned - because this was done to separate Catalog/EMM from the binaries, there are 2 Master Servers - one online and one standby. 

 

Please note that when you cluster windows Master Servers - you need to (VCS installer actually does it) use similar method. 

 

Hope it helps. 

Sebastian Baszczyj

Marianne's picture

NBU is currently installed on the 2nd internal drive (D), right?

My suggestion:

Purchase a new, bigger drive to replace current D-drive.

Perform catalog backup, then remove NBU.
Install new bigger D-drive, install NBU and restore catalog backup.

You really have to do the maths first (see 1st reply above). I have seen 600GB image catalog for 200 clients.

 

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

PhaniKumar82's picture

Team

when i raised call with symantec they have given the following solution

can i proceed with the below ?

 

1. Perform catalog backup

 

2. Shut down Netbackup.

Make sure all processes have stopped by running command:

D:\veritas\netbackup\bin\bpps

 

3. Copy all files/folders from D:\ drive to E:\ drive

 

4. Copy all files/folders from E:\ drive to D:\ drive

 

5. Rename D:\veritas folder to D:\veritas_original

 

6. Change drive letters. i.e D:\ to E:\ and E:\ to D:\

 

7. Reboot master

 

8. Stop Netbackup scheduler from starting any netbackup jobs:

D:\veritas\netbackup\bin\admincmd\nbpemreq -suspend_scheduling

 

9. Verify main services are running:

D:\veritas\netbackup\bin\bpps

nbemm,

bpdbm,

 

10. Verify EMM database is responding:

D:\veritas\netbackup\bin\nbdb_ping

 

11. Open Netbackup console and check following:

policies

storage units

media .. check time assigned column - any media with valid backups should have date in this column

tape drives

disk pools

- open BAR gui and check you can view files for restore.

 

If any data is lost, you need to shut down Netbackup and call Symantec Support.

 

12. If everything is ok, you can resume Netbackup scheduler and test backups:

D:\veritas\netbackup\bin\admincmd\nbpemreq -resume_scheduling

 

Regards,

Phani Kumar

SOLUTION
Marianne's picture

Awesome! Your support engineer deserves a 'thumbs up'!

Please ask the engineer to publish this solution as a TN.

The only reason why this will work is because NBU was installed on a non-system drive (D-drive and not the default C:\Program Files).

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

mph999's picture

Yes I agree that would work - so you can 'upgrade' to a bigger disk.

For some reason (probably because I can't read' I thought NBU was insalled on the system drive, so please accept my apologies regarding that point.

Regards,

Martin

 

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

Hi All,

I am Kumars team mate .

 I will like to know:

1. How safe is windows option robocopy in terms of files,folders  permission while carrying out step 3 i.e all the permission as in orginal ones replicated to new drive. 

We have tested it on netbackup 7.1.0.3 master server ( VM test machine) & its fine with respect to  no of files/folders & total data being copied.Find the output as below :

             
                  Total    Copied   Skipped  Mismatch    FAILED    Extras
    Dirs :       424       419         5                0                      0         0
   Files :      4485      4485       0                0                      0         0
   Bytes :   1.427 g   1.427 g   0                0                      0         0
 
 Times :   0:00:55   0:00:54                       0:00:00   0:00:01

   Speed :            28311885 Bytes/sec.
   Speed :            1620.019 MegaBytes/min.

   Ended : Wed Apr 11 16:13:01 2012       

Directories missed are the system volume information & recycle bin (hidden ones )
Can be ignored as total no of files /folder & data size is same as it was before robocopy.

2.As we will be shutting down netbackup services &copying files.

Is there any other better option for copying the files instead of robocopy .

3.We will be copying D:\ drive (physcial ) to NEW SAN DRIVE instead of E:\ drive.

Need to know if any precautions we need to take before renaming the drive letter & rebooting the windows server other than checking data copied is same as the earlier one ,having catalog backup & ALL_LOCAL_DRIVE backup.

Regards

Dhawal

 

 

 

 

 

 

 

 

 

 

PhaniKumar82's picture

Thank you very much team i have successfully moved netbackup from local drive D to SAN drive E without any issues 

now every thing looks fine 

Regards,

Kumar