Moving NSR/Indexes between partitions

[eeicai]

Hello,

Any help would be greatly appreciated.
We have a NT backup server running Legato Networker v6.2.
Due to a necessary rebuild last week, the software was installed to the C partition and this is where the NSR/index information resides.

However there is only 100MB free whilst on E: 12Gb is free.
Are there pitfalls/dangers moving everything to E?
Many thanks,
Carlo

 

[605]

Nothing is easier than that. However, as there is an index for each client, you have to repeat the procedure for each client:

1. Shut down NetWorker
2. Move (or copy) the whole index directory to anothet location
3. Restatrt NW
4. Start NWADMIN
5. If not already done, make the hidden attributes appear
6. Adjust the client index path for each client.
7. Check the index


Another method should work as well and is probably much faster:
1. Shutdown NW
2. De-Install the software.
This will leave all databases behind.
3. Move the databases to the desired location
4. Install NW at the new location

 

[eeicai]

Many thanks for your advice Instructor.
I will attempt to this tomorrow (fingers crossed).
Once I copy the whole NSR folder on the C drive (1.26GB) to another location, am I safe to roll back to this scenario if something horrible happens?

 

[605]

Sure - as long as you adjust the index path again. You may even leave the original location behind. And of course you may still recover from the index backup.

 

[eeicai]

Hi Instructor,

When I copied the NSR folder from C to E, not 100% of it came across, got no error messages, but compared sizes.
When I ran a test backup, It took me 3 times to stop it.
It said "Resource number 107257 for client should have resource number 107258" ??????
Before I ran the test backup, I changed the clients index to the new location. Now I have rolled back to the original and am still getting this error msg (have deleted the index path for client), I assume blank means go back to original?

 

[HelpNow]

When you leave the index path blank it might have created secound index for the client under default index directory, if the original install path was not followed, this might have created 3rd location for the inded ( original, moved, new install path).
You should also run the usuall index check to check the consisteancy, i.e nsrck -L5 and or nsrim -X.
If all fail, you might want to delete the index path and run nsrck -L7 client name to recreate it.

 

[605]

I never said that you should move the NSR path - i was talking about the index (/nsr/index/client_name) directories. Please follow the procedure.

 

[eeicai]

Thank you both for your advice. Now I see, the point you make about moving the index only and leaving NSR on C drive.
Will however this mean that logs/informaion will be written to C drive?

 

[605]

Nothing will change except for the index path.

 

[eeicai]

Hi Instructor,

Is there a special way of copying the indexes from C: to E:, just the the copied amount does not match the origianl amount. Does 'copy' fail to copy some 0kb files for example?

 

[Chacalinc]

just the the copied amount does not match the origianl amount

keep in mind the fragmentation. Files commonly used tend to get fragmented. With a disk to disk copy you are defragmentating the file(s), so the required space is less than the original one.

Does 'copy' fail to copy some 0kb files for example?

it depends on your operative system, NW has nothing to do here. But OS will copy files even if they has no content (0 bytes).

cheers.

 

[605]

The key info you need comes from
nsrls clientname or from
nsrinfo clientname

Just make sure that the number before and after the move match.

 

[csp67051]

I have successfully moved indexes from one location to another using the following command.

***Ensure that no backups or restores are running on the NetWorker server, then shut down the NetWorker Backup & Recover Server Service

Command:
uasm -s -i "C:\Program Files\nsr\index\SERVER1" | uasm -r -m "C:\Program Files\nsr\index\SERVER1"="D:\nsr\index\SERVER1"

Once the copy is complete restart the NetWorker Backup & Recover Server Service and you will also need to point the client to the new index location within the NetWorker Administrator program.

 

[605]

This was the old (5.x) procedure which in general still would be valid. However, the command is rather complicated and it is not necessary any more. It was just the official procedure because Legato wanted to ensure that "holey" database files were properly handled.

As they do not exist with NW since 6.0, copying/moving the directory if sufficient.

 

[eeicai]

Thanks to all. As a workaround, I have left the old indexes on C drive and created/pointing this weekend's FULL backups to E drive and after checking all were successful

Will this be ok long term? or will there be restoring/recovering file issues?
Thanks again

 

[605]

He - what about a bit of belief. Does it really matter where the index is as long as you do know the position?

 

[eeicai]

Can anyone help here? Does Networker User (for doing restores) need to know where the old indexes are stored? (thought it might have done this automatically)

Indexes are now pointing at E drive since Feb 18th but the old indexes are still on C, when I request a restore from the 14th Feb, it says
"No entries backed up to server {Client1} at time ....."
Any help much appreciated

 

[605]

All file indexes are always at only location.

If you see the above message, can it be that the save sets have already become recoverable? - If so, the CFI information has been deleted alredy.