{"id":923,"date":"2009-08-29T06:47:32","date_gmt":"2009-08-28T20:47:32","guid":{"rendered":"http:\/\/nsrd.wordpress.com\/?p=923"},"modified":"2018-12-12T15:48:00","modified_gmt":"2018-12-12T05:48:00","slug":"basics-what-inode-did-that-file-have-when-it-was-backed-up","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2009\/08\/29\/basics-what-inode-did-that-file-have-when-it-was-backed-up\/","title":{"rendered":"Basics – What inode did that file have when it was backed up?"},"content":{"rendered":"

I had an odd question recently from a customer – they wanted to know whether NetWorker could tell them what inode a file had when it was backed up. Thankfully, having previous experience with NetWorker and AdvFS<\/a>, I knew that NetWorker did keep track of inode details during the backup.<\/p>\n

The way to find this out is to use the nsrinfo command. Let’s say we’ve got a directory\/mount-point, ‘\/var’, and we want to see what inode it had during backup. In this case, the command that you would run would be:<\/p>\n

# nsrinfo -N \/var\/ clientName<\/pre>\n
(Note the use of “\/var\/”, not “\/var”.)<\/p>\n
So if I want to find this information out for the client ‘nox’, I’d run:<\/p>\n
[root@nox ~]# nsrinfo -vV -N \/var\/ nox<\/div>\n
scanning client `nox’ for all savetimes from the backup namespace<\/div>\n
UNIX ASDF v2 file `\/var\/’, size=660, off=3456572, app=backup(1), date=1251459999 Fri 28 Aug 2009 09:46:39 PM EST, fid = 2304.2147905, file size=4096<\/div>\n
ndirentry->2639214 <\/span>ftp\/<\/div>\n
[root@nox ~]# nsrinfo -vV -N \/var\/ nox\nscanning client `nox' for all savetimes from the backup namespace\nUNIX ASDF v2 file `\/var\/', size=660, off=3456572, app=backup(1), \ndate=1251459999 Fri 28 Aug 2009 09:46:39 PM EST, fid = 2304.2147905, \nfile size=4096\n  ndirentry->2639214\t<\/span>ftp\/<\/pre>\n
(The rest of the output has been snipped.)<\/p>\n
So where, you might wonder, is the inode detail stored in all of this? Look for the ‘fid = X.Y’ part of the output; the inode number is Y – in this case, 2147905. We can verify that by running stat against the directory:<\/p>\n
[root@nox ~]# stat \/var\n  File: `\/var'\n  Size: 4096      \t<\/span>Blocks: 16         IO Block: 4096   directory\nDevice: 900h\/2304d\t<\/span>Inode: 2147905     Links: 25\nAccess: (0755\/drwxr-xr-x)  Uid: (    0\/    root)   Gid: (    0\/    root)<\/pre>\n
As you can see, the inodes match.<\/p>\n
So there you have it – you can use NetWorker to confirm\/check what inode number a file or directory had when it was backed up.<\/p>\n","protected":false},"excerpt":{"rendered":"
I had an odd question recently from a customer – they wanted to know whether NetWorker could tell them what…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[6],"tags":[482,662,937],"class_list":["post-923","post","type-post","status-publish","format-standard","hentry","category-basics","tag-inode","tag-nsrinfo","tag-stat"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t