01-06-2013 06:34 PM
Hi Folks,
After we have upgraded 7.5.0.1 suddly database image growth is increaed and we have increase file system size 100GB last month but within one month again it reached 95%...Please let us know any other modifcation required on 7.5.0.1 datagrowth reduction..
Thanks,
Susi.S
Solved! Go to Solution.
01-07-2013 09:21 AM
It does seem extreme to be deleting backup images due to lack of space on the NBU server
Would it not be better to add disk space rather than deleting your backups?
01-06-2013 07:40 PM
01-06-2013 07:55 PM
NBU 7.5 actually stores a bit less in images folder because the header files are moved into EMM database.
The biggest space consumers remain the '.f'' files - same as previous versions.
Factors that play a role (extract from NBU 7.5 Admin Guide I):
01-06-2013 11:27 PM
Adding to Mariannes excellent post, you could have some files left in the tmp directories eg:
/usr/openv/netbackup/db/images/<client>/<ctime>/tmp
Files go in there during backup, and get moved up a level if it completes successfully, and should be deleted if it fails. If the system has an unclean shoutdown, files could be left behind, but, I wouldn't expect this to be a regular occurance, so it not likely to be the issue - however, worth checking.
As Marianne said, NBU 7.5.x does noy use more catalog space, in fact it uses slightly less - I'm not aware of any known issues with it, so sussect the most likely cause is one of those listed by Marianne.
Martin
01-07-2013 03:05 AM
Can you tell us the Operating System you are using and if you have identified which area is suing up the disk space?
Is it the /images/ directory or somewhere else (tmp / temp etc.)?
Thanks
01-07-2013 06:47 AM
Hi Marianne,
We found some of client incremental backup size is more than 300GB for daily basis.Those client images utilizing much more size...Is the any way to compress image size of those clients alone ???
01-07-2013 06:48 AM
Its solaris and windows client...under /image/client only utilizing much more size....
01-07-2013 06:51 AM
Hi Martin,
under /tmp is not utlizing much more size..I could see /usr/openv/netbackup/db/images/<client>/<ctime>/catstore utlizing much more size...Is there any way to compress it?
01-07-2013 07:32 AM
We found some of client incremental backup size is more than 300GB for daily basis.Those client images utilizing much more size...Is the any way to compress image size of those clients alone ???
That is normal the more the data the image would be bigger, we have incrementals more than 500 GB in our environment. You can do the archiving or compression on complete catalog as per my first post but not for some clients. Please consider again your retention If you have longer retention then this will happen. You have to plan accordingly as per you environment
01-07-2013 08:00 AM
Actually we have expired most of the incremental backup of the particular client but still its not removing from /opt/openv/netbackup/db/images/client/time-stamp..Please let us know how we will remove those files under /opt/openv/netbackup/db/images/client/time-stamp..
01-07-2013 08:35 AM
If they are on tape then use bpexpdate -deassignempty -force
If on disk use nbdelete -allvolumes
Followup using bpimage -cleanup -allclients
If you have already expired them then the last command above should do the trick for you
01-07-2013 08:41 AM
Hi Mark,
We have catalog image on the disk only...I have did below steps to get free space..
1)Expired entire november month on one client(this client is utilized much space)
2)Run bpimage cleanup to cleanup images..
Please let us know nbdelete -allvolumes will delete only expired images???
01-07-2013 08:48 AM
Yes - it is perfectly safe to run - from the guide:
Queries the image list in the EMMdatabase to obtain the list of volumes with
deleted fragments. It removes the fragments from those volumes and deletes
eligible imported snaps, unimported snaps, and tar images in that order.
-allvolumes calls bpdm on master server to delete imported snaps. It also
queries the storage servers with unimported snapshots but does not direct
bpdm to delete them.
This clears down the disk itself - the bpimage command cleans the catalog
Does it run with 100% success?
01-07-2013 09:07 AM
Yes..bpimage cleanup completed 100% success...Please find the below for details..
01-07-2013 09:21 AM
It does seem extreme to be deleting backup images due to lack of space on the NBU server
Would it not be better to add disk space rather than deleting your backups?
01-07-2013 09:27 AM
Incrementals running as Full? Please provide backup policy details
bppllist -L <policy_name>
01-07-2013 09:43 AM
Actually problem is we have taken cold data base backup for particular server and removed exclude list for all database file systems,then we forgot to add in the exclude list after cold backup completes...Because of that reason its huge file system having that database server and image size increased due this issue.,,
01-07-2013 09:44 AM
We have schedueld correct one but its database file system we forgot to add on exclude_list after cold backup completes...
01-07-2013 09:50 AM
Partial output? Incremental schedule has to be in same policy as the Full schedule.
01-07-2013 09:51 AM