Forum Discussion

Ajith_Sankar's avatar
12 years ago
Solved

Need to change image db path

Hi Folks

  Master : Netbackup 7.6.0.2 with Appliance 5230, Windows 2008 R2 64-bit

At present Netbackup is on C:\, i wanted to move the image database to D:\. Please let me know any simplest solution. I dont want to implement Altpath fix.

Also let me know the procedure incase of move both image and relationla database to different path.

 

  • No idea how to do it in wndows, have you got any unix of linux servers,  easier to take a list of clients from the master, run it through a script on unix to create the script to run on the windows master

    If the file client_list  contains a list of clients.

     

    cat client_list |while read LINE 

    do

    echo "mkdir d:\netbackup\imagedb\images\$LINE" >>script

    echo "write output "d:\netbackup\imagedb\images\$LINE" | out-file "C:\Program Files\Veritas\NetBackup\db\images\$LINE\ALTPATH"" >>script

    done

    This should create a file on the unix machne call script, that contains two lines for each client in cllient_list :

    mkdir d:\netbackup\imagedb\images\client1

    write output "d:\netbackup\imagedb\images\client1" | out-file "C:\Program Files\Veritas\NetBackup\db\images\client1\ALTPATH"

    You then copy 'script' to the windows machine and run it in powershell.

    The first line for each client creates the dir, the second line puts the PATH to the alt location in the ALTPATH file in the top level of the images dir, for that client.

    NOTE:

    I'm not 100% sure the windows comaand write output is correct, I haven't tested it and don't have any windows  machines nearby to test on, but it gves an idea how it could be done, just might need some adjustment.

    Mark S might be along at some point, he might be able to advise how to do it completely in windows ...

     

17 Replies

Replies have been turned off for this discussion
  • The copy old/ new method as above won't work - I've been thinkig about this and the NBDB in the original C install contains the path, which when coped to <other drive> will be incorrect.  Reinstalling NBU on that new drive fixes the registry entries, but not the DB.

    You would have to first, with NBU still installed on C use nbdbadmin to change the DB location to the new drive, then copy the files across to a tmp location, reinstall NBU on the new drive then copy the original install back to the proper location - or, something along those lines.

  • The main reason to move from C to D is space crunch in C drive. Now i am thinking instead of miving from C , i belive in windows we can map some drive space(either from storage or from other local drive) as folder in c drive. Is that possible to place that mount on C:\Program files\veritas\NetbackupDB and copy all subdirectories inside NetbackupDB into newly created NetbackupDB mount.

     

  • I think with windows you don;t extend a specific dir, it is all at drive level.  So add the space to C:\ , job done.

    Personally, it would be wise to move the install to a dedicated drive letter, for a start, it will perform better due to reduced disk activity.

  • Ahh didn't know that Riaan ... interesting.

    Unless I've misunderstood, it's still talking about a seperate drive, just giving it a path, not a letter.

    So I think my advice is still the same, a separate physical drive is best to avoid disk thrashing.

  • I dont want to implement either Altpath or any registry value entries change to move the image db. All those would cause failures when we do an upgrade of nbu. All i need is some free space for image db. Would like to give a try this mapping option that taking from local hard disk. Hope that should work without changing any configuration settings/registry values related to netbackup.

  • It is a separte drive yes, just mounted on C:\Program Files\Veritas as example. Same concept as in the unix world where we would mount  a large SAN drive as /usr/openv/netbackup/db/images if we had a huge catalog. I'm not sure if Windows has any issues with the location of the folder mount point i.e. it has do be on D:\Folder mount, and not C:\anything.