Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Index backup question

Status
Not open for further replies.

haasemi

MIS
Aug 19, 2002
68
EU
Hello,

how I have to name a saveset to backup only the index of a client?

I will not use the -O option of the savegrp.exe command.
The option "no save" within the savegroup definition within the NMC works always only one time...

Thanks in advance.

regards
 
You can use any saveset e.g. c:\windows if you skip this saveset with a directive e.g.
<< "C:\windows" >>
+skip: .?* *
nothing except the index will be saved.

A better way exits with Networker 7.6 there you can create a group with nmc and this Group will only backup index savesets.

So consider an upgrade if you dont need lockboxes, for me lockboxes dont work in 7.6.

 
Of course you can do this. But does it make sense to backup the index if nothing has changed at all?
 
I Have the following scenario:

Now: NDMP & Index of the NetApp filer (as storage node) are written to the same pool. This caused that the index is written alone to an additional LTO-4 volume, because the already used one is mounted to the drive of the filer if the NW server want to write the index to the volume.

I don´t want to separate the index or NDMP savesets to separate pools.

I want to have a possibility to backup the group with the NDMP savesets without index backup (this is possible) and have a separate group which only should backup the index of the NDMP backups afterwards.

Ideas?
 
This sounds as if you would have 2 LTO-4 devices enabled for the same pool:
- 1 at the filer to run local backups
- 1 at the server to run local index backups

This is unusual it would result in a NDMP backup (filer data) and non-NDMP backup (the index) which you send back to the storage node (the filer) which can only run NDMP devices. Even if this could be configured, it looks strange to me.

My proposal: On the server, create a separate pool for index & bootstrap backups (best practice anyway). This would ensure that the index save set is just appended and added to the other index (and bootstrap) backups.

 
Strange or not...

How I can force a group/client using the NMC to backup only the index of the assigned clients?

As I wrote the "no save" flag within the group configuration don´t work...
 
In NMC, this is just possible with NW 7.6 as a060463xyz already stated.

For earlier versions, copy the client to a separate group, then from the command line, execute "savegrp -O -G groupname".

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top