On Linux/Unix environments creating symbolic links is enough, on Windows environments should be so easy as Linux/Unix creating ALTPATH touch file but I always insert the directories to the list used for Cold Database Backup even because I've never had the curiosity to try without that and because if the customer wants to configure a cold database backup in the future, it will be ready to do (Not that I recommend cold database backups but If I leave on their hands, I pretty sure they will forget doing this). All restores I did this way worked fine.
Anyway, I recommend you (if possible) instead of moving only some image databases, move all of them to the same location * (is always better having them away from system disks, better if is in a storage LUN) cause is so much easier to manage them.
Having your image database on a Storage LUN or another disk not the system disk, suppose that you loose your NetBackup Master Server's System Disk but not the data on LUN (or other disk that is not the system disk), the recovery procedure will be so much faster as image database is the large database on NetBackup and you will not need to recover them.
-------
* = Moving all image databases on Windows
-------
- Backup everything;
- Stop NetBackup using bpdown (you could stop just some services but NetBackup will be unavailable anyway);
- Create the new location directory (if not done yet);
- Move all content under {install_path}\netbackup\db\images\ to the new location;
create a touch file called ALTPATH under {install_path}\netbackup\db\images\ with the new path address inside (just one line with the new address);
- Start NetBackup using bpup;
- For warranty, insert the new path address (same as inside the touch file) in the Directory List used for cold database backups);
- Test everything (Backup, Catalog Search, Restore).
Done.
Hope it helps
Message Edited by Raphael Carvalho on 01-21-2009 02:23 PM
