Backup Central

Is there a way to configure a scheduled clone job such that it EXCLUDES specific savesets rather than INCLUDING them? For instance, using mminfo query commands in Networker and adding an exclamation point before certain parts of the query will give you the opposite results...or results that are NOT like the data that is being queried for.

Example:

mminfo -a -r "volume,client,savetime(22),totalsize,nfiles,name,ssflags,sumflags,pool" -q "!incomplete" -t yesterday

This would return all NOT INCOMPLETE backups, but rather successful ones and not incomplete ones. If you remove the exclamation point, then it queries for the incomplete status.

With that being said, obviously this has nothing to do with cloning, but I wanted to see if there is similar functionality that I can use. I am trying to exclude VSS savesets from going to our tape media as we have a Data Domain that retains data for 30 days. I would think that after a month one would no longer need the VSS savesets...maybe even a week, no? Maybe this is something to add to the Networker wish list?


- In the scheduled clone job properties in the NMC, under filter savesets by name, one could put "!VSS ASR DISK:\" and that would exclude it from being cloned, while cloning other data, rather than putting "VSS ASR DISK:\" to ONLY clone that specific saveset.

Any thoughts on ways to configure the clone job to do this? Currently, our clone jobs send ALL FULL backups from the last week to tape, including the VSS savesets, since they are full backups also. Hopefully this makes sense...please bare with me as I am self-taught and don't have any formal training with Networker.

Thanks in advance!

Bryan



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

I tried this from the command line but it will obviously not work:

C:\>mminfo -q "client=name1,level=full,savetime>-7days,name='C:\'" -r "client,name,level,savetime" -ot
client name lvl date
name1 C:\ full 20.04.2012

C:\>mminfo -q "client=name,level=full,savetime>-7days,!name='C:\'" -r "client,name,level,savetime" -ot
client name lvl date
name1 C:\ full 20.04.2012

C:\>


So i do not expect it to run from the GUI as well. This is NW 7.6.2.5

Doh! "incomplete" is a flag attribute which only has the values of 'true' or 'false' AND only applies to query constraints....so you are correct, the methodology I had previously mentioned will not work.

So am I wrong for not wanting the VSS savesets to go to tape every week? It just seems like a lot of wasted tape media to store offsite for 6 months. The only ones I would want to keep offsite would be the VSS savesets on my Domain Controllers just to be safe, but again, I still think that is unnecessary. Please correct me if my thinking is incorrect...

I'm assuming there is a way to do this such that:

1. When backups occur for the filesystem savesets, like C:\, D:\, etc., I can send those to a media pool called 'Filesystems'
2. Then have another group that runs the VSS saveset backups and sends them to a separate media pool called 'VSS', for example?
3. I could then filter the clone job to only grab the full backups from the 'Filesystems' pool
4. Set a 1 month retention period on the 'VSS' pool which never goes to tape media.

We have over 200 clients so I'm thinking that this would be a huge configuration change (and a boat load of work).

Any thoughts about VSS savesets and if they really need to go offsite while retained onsite for 1 month? I can't think of a scenario where one would have to go back 1 month for a VSS saveset, but I have also never run into a situation like that. Perhaps I don't understand VSS as well as I should? If I don't need to keep them more than my DataDomain retention period of 1 month, would the configuration I outlined above be the proper way to handle this? Thanks again.

I am running NW 7.6.2.7 on Windows Server 2008 R2 Standard 64-bit.


-Bryan


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On Behalf Of bingo
Sent: Thursday, April 26, 2012 3:49 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] Scheduled Clone Jobs - How To Set Exclusions Rather Than Fil

I tried this from the command line but it will obviously not work:

C:\>mminfo -q "client=name1,level=full,savetime>-7days,name='C:\'" -r "client,name,level,savetime" -ot
client name lvl date
name1 C:\ full 20.04.2012

C:\>mminfo -q "client=name,level=full,savetime>-7days,!name='C:\'" -r "client,name,level,savetime" -ot
client name lvl date
name1 C:\ full 20.04.2012

C:\>


So i do not expect it to run from the GUI as well. This is NW 7.6.2.5

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld < at > avus-cr.de via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------




via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

We created a tape pool called VSS, and we back up the VSS data to those tapes. We do volume clones; those tapes are never cloned, only the tapes with meaningful data on them. We have a 3-month retention policy on the VSS tapes. Hence, the VSS data goes away after three months.