situation
A server (server1) isn’t necessary anymore. Its name is also deleted from DNS.
The backup-admin hasn’t been informed by his colleagues as usual and wonders why backup of this client is failing. After a phone call he knows that this system is history and no backup of it is needed anymore.
So it’s time to delete all traces of this server in the backup system (in this case EMC networker).
delete Networker client once and for all
The server doesn’t exist in DNS anymore so one has to create a dummy entry for server1 in /etc/hosts on the backup server. In case a colleague has already deleted the machine in Networker management console (NMC) create it once again.
Now one has to delete all still existing savesets of this client in its client index. After that the index itself has to be deleted.
for xxx in `mminfo -av -r "ssid(53)" -c server1`; do nsrmm -d -S $xxx -y; echo delete SSID $xxx ...; done nsrck -YR server1 rm -r /nsr/index/server1/
Now let’s clean up the media database.
nsrim -c server1 -X
Finally one can delete the backup client in NMC and the dummy entry in /etc/hosts on backup server.
Hello,
Thank’s for this very interesting post.
And I have a question: have you any idea in case of clones ? Is it necessary finding and deleting “clone id” before “ssid” ?
Clones are also deleted in the commands mentioned above.
Have a look at this example:
root@backupserver1 # mminfo -av -r "name,savetime(20),level,ssid,cloneid,ssid(53),ssretent,ssflags,sumflags,client,copies,clflags" -q client=client1 -o tname date time lvl ssid clone id ssid retent ssflags fl client copies clflg/oracle 07/20/10 22:00:43 4 3041263719 1279656039 8dcb9c0f-00000006-b5460067-4c460067-44550014-4f222e18 08/20/10 vF cb client1 2/oracle 07/20/10 22:00:43 4 3041263719 1279656038 8dcb9c0f-00000006-b5460067-4c460067-44550014-4f222e18 08/20/10 vF cb client1 2/ 07/20/10 22:00:47 4 2974154860 1279656044 00987c05-00000006-b146006c-4c46006c-44590014-4f222e18 08/20/10 vF cb client1 2/ 07/20/10 22:00:47 4 2974154860 1279656043 00987c05-00000006-b146006c-4c46006c-44590014-4f222e18 08/20/10 vF cb client1 2Networker works with Saveset-IDs. The ssid also includes all clones (see copies=2 in the example). There’s the same ssid (=3041263719) with 2 different cloneid (=1279656039,1279656038). So if you delete a ssid all clones (original saveset and clones) will also be deleted. It is wise to use ssid(53) (=1279656039 8dcb9c0f-00000006-b5460067-4c460067-44550014-4f222e18) instead of ssid because ssid may not be unique and you don’t want to delete wrong data.
If you want to delete a certain saveset or clone you have to use syntax
nsrmm -dy -S ssid/cloneidinstead ofnsrmm -dy -S ssidornsrmm -dy -S ssid(53).Have a look at mminfo and/or nsrmm manpage for more infos