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 ;)

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.

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.

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.

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?

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.