Backup status is in 'creating' status forever for NetApp share for some negative scenarios

[Gireesh Awasthi]

There are two scenarios when backup creation is failing but status of backup remains in 'creating' state forever.

1. When user provide wrong backup type or when config have wrong backend under backup-type stanza, in this case we throw bad configuration exception. The error message is too long due to that db update is failing and backup status is not changing from creating status to failed.

Solution:
--------
We catch the exception and throwing customizing exception

2. When user provide the destination volume in config file which was part of some other relationship which is deleted. In this case when user created the SnapMirror relationship with the volume then relationship health status become 'false'. In this case also, backup creation was remain in creating state for long time.

Solution:
Throw the exception when SnapMirror relationship is created during backup creation is not healthy.