Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Option for renaming a policy

Created: 03 Aug 2009 • Updated: 24 Feb 2010 | 16 comments
V.Dinesh's picture
96 Agree
2 Disagree
+94 98 Votes
Login to vote
Status: In Review

It would be better if the netbackup could provide us the option to  rename a policy with the right click....

Comments 16 CommentsJump to latest comment

Randhir Sharma's picture

Yes,it would be a better option if we can just rename a policy without creating a new one.

0
Login to vote
Venkatesh K's picture

Im just wondering,
 
why would you want to rename a policy ?

what according to you are the benifits from renaming the policy ?

answerers to these questions will have good support

as per current Netbackup if renaming is allowed then it should till be treated as same policy else it may start backup of the client as full backup from the day it is renamed.

Thanks & Regards, Venki Dont forget to Vote for + if you think suggestion is good, and mark as solution if it has resolved your problem.

-1
Login to vote
Rusty Major's picture

This is available on the command line. Check the commands guide for the right command, I don't recall it off the top of my head.

0
Login to vote
Andy Welburn's picture

NAME
bppolicynew - create, copy, or rename a NetBackup policy

SYNOPSIS
/usr/openv/netbackup/bin/admincmd/bppolicynew policy_name [-verbose] [-M master_server,...]
/usr/openv/netbackup/bin/admincmd/bppolicynew policy_name -sameas existing_policy_name [-verbose] [-M master_server,...]
/usr/openv/netbackup/bin/admincmd/bppolicynew existing_policy_name -renameto policy_name [-verbose] [-M master_server,...]

DESCRIPTION
bppolicynew performs one of the following operations on a NetBackup policy:
■ Create a new policy with default attribute values
■ Create a new policy with the same attributes as an existing policy
■ Rename an existing policy

Therefore should "be easy enough" to make it into an option on the GUI ;)

-1
Login to vote
Roobix.Cube's picture

If bppolicynew renames a policy, the existing association of images with the policy is lost. This means that the images that were created before the policy was renamed are not included in a list of images for the renamed policy. The command does not rename a policy with the same name as an existing policy.

+2
Login to vote
Fred2010's picture

It would be great if indeed ALL objects could be renamed:

For instance Storage Lifecycle Policies cannot be renamed either (Nor can they be copied, which is annoying as well)

+1
Login to vote
Roobix.Cube's picture

Yes, I know it's trivial, but over time adminstrators in my domain have used a combination of policy names:

  • all lower case letters
  • first letter capital
  • all capital letters

This influences the order they appear in the Admin Console, thus not allowing the entire list to be alphabetical.  You cannot use bppolicynew to change a policy from CAPS to lower case because it thinks they're the same name.

+1
Login to vote
alazanowski's picture

I agree, specifically is a problem when you need to change capitalization, or change a current old policy to meet the new standard.

-Austin Lazanowski Backups cost way too much until you needed them.

0
Login to vote
Yogesh.Jadhav's picture

 Policy changes can be done using commands bppolicynew and bpplinfo as well. The policy details can also modified using othre policy related commands without using gui.

Thanks & Regards

Yogesh Jadhav
-1
Login to vote
Holowinski's picture

Not sure if it is supported or what kind of other problems it would cause, but I know you can copy a folder in the db\class folder and that creates a new policy, so I assume if you rename it that would work too.

0
Login to vote
JustinLP's picture

I agree with most all comments/suggestions above. Renaming a policy is very much needed functionality (without adverse effects). Either that, or the ability to create a folder under the Policies node (for purposes of logical grouping, quicker navigation, and probably a few others that I'm not thinking of at the moment). For example, I'd like to be able to group my Exchange Information Store policies together, and then separately have the actual Exchange server host backup policies grouped together in another folder. I could somewhat group them by a separate naming convention for my policies, but that wouldn't follow along with my organizations current convention. If I decided on a new naming standard, then I'd like to force all policies to adhere to the new one, but using the current method of renaming doesn't sound like it's a good option for me at this time due to the fact that it will break the associations with the backup images.

It's not a deal breaker by any means, but from the standpoint of an admin that already has a ton of stuff on his plate as it is (as I know many like me do), both the ability to safely rename or the ability to group policies into some sort of containers sure would be nice to have.

I saw the article on how to rename a policy using bppolicynew, but I'd prefer not to break the association with the backup images. I know this isn't a support forum, but the online support article I saw applied to NBU 6.0. Does anyone know if this is still the case for NBU 6.6.5?

+1
Login to vote
nbustarter380's picture

We are using netbackup 7 1 client and I have the same question

What if the policy is renamed incorrectly for example bellow01 was name mellow01 and it did one full backup only can I use the Gui to rename it? If not what would be the best way to correct this? What about the reprecussions? if any

Also, it would be ok if anything was lost becasue they wouldn't be correct anyway.

0
Login to vote
mansoor.sheik's picture

Hi,

Good and Need idea..

0
Login to vote
Efi G's picture

agree also for SLP's

0
Login to vote
Shaun Taylor's picture

This would come in quite handy! I also like the idea of being able to group policies too.

0
Login to vote
DG-2005's picture

you can get around this for renaming by navigating to

?:\Program Files\Veritas\NetBackup\db\class

and renaming the folder there, do a refresh and it applies to NBU w/out creating new FWIW

7.6.0.2 running to DD4200, duplicating to 2x DD670

7.6.0.3 running to 3x 5230  

0
Login to vote