Multi-streaming from a user init job with a file list
Updated: 24 May 2010 | 11 comments
Good day,
Has anyone ever setup a user initiated backup job that uses a file list and configured it successfully for multi-streaming?
I've got a server that runs a script to generate a file_list.txt and then runs bpbackup against that file.
The file contains a multitude of paths, such as:
G:\Data\1
G:\Data\2
G:\Data\3
G:\Data\4
etc
Wildcards are, unfortunately, not an option in this scenario.
The policy is configured to allow multiple streams but it always treats the backup as 1 job.
I've even tried adding 'NEW_STREAM' directives into the file list but it just pops a Status Code 69 (invalid specification) when I do that.
Any ideas?
discussion Filed Under:
Comments
Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige
Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige
Yeah, it's been crazy busy preparing to go to 6.0 here ...
Anyway, the reason we're using a user initiated backup with a file list is because the selections in the file list will change from day to day. Obviously that wouldn't work well from a policy point either.
The server admins are using NTFS 'junction points' (http://support.microsoft.com/kb/205524) on this server and it's turning out to be tricky to backup. For some reason, if we backup the drive 'as is', it backs up all the junction points AND the data behind them (this would be a good thing, you'd think, but isn't). However, when we try to restore from a 'junctioned' backup, it restores only the junction point, but not the data behind it. So, like, half the backup taken is useless due to that.
I'm trying to set it up so that the client initiates the backup and the file list contains only the folders that are still 'live' on the drive. The admins have setup a script, but it does about 120 folders (about 5-10gb a pop) all as 1 job. From a performance point of view, I think we could get better perfornamce if each folder was a separate job (ie: multi-streamed).
My last idea is to have their script initiate a job with each folder it finds, as opposed to just adding that folder into the file list ...
Message Edited by David Parker on 11-09-2007 01:04 PM
USAGE: bpplinclude policy_name [-v] [-M master_server,...] -L|-l
bpplinclude policy_name [-v] [-M master_server,...] -add path_name ...
bpplinclude policy_name [-v] [-M master_server,...] -add -f filename
bpplinclude policy_name [-v] [-M master_server,...] -delete path_name ...
bpplinclude policy_name [-v] [-M master_server,...] -delete -f filename
bpplinclude policy_name [-v] [-M master_server,...]
-modify {old_path_name new_path_name} ...
Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige
Hmm, so you're suggesting having the client dynamically regenerate the backup selection for the policy and then initiate a manual backup?
Can you add directives (ie: NEW_STREAM) with bpplinclude? I don't see it listed there ...
From a policy perspective, the selection should look like:
NEW_STREAM
<folder>
NEW_STREAM
<folder>
NEW_STREAM
<folder>
etc
EDIT:
Bob, you are still THE MAN!
This will work perfectly for what I need ...
Synopsis:
1) Client deletes policy selection
2) Client generates new policy selection
3) Client updates policy with new selection
4) Client initiates a manual run of the policy
Jackpot!
Assuming bpplinclude.exe is included on the client ...
Message Edited by David Parker on 11-09-2007 01:59 PM
Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige
You'd think text was text ...
But when I used bpbackup (no -i) and -f, and had 'NEW_STREAM' in the file list, it errored out (SC 69).
Doesn't look like bpplinclude is part of the client install; must be a master/media only thing ...
I suppose I could load the admin programs onto this client and set it up that way ...
Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige
Right right.
But with -f I was putting NEW_STREAM INTO the file_list.txt file ... not specifying it as the -f switch =P
-i is only going to be helpful if I can manipulate the policy selection list from the client ...
Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige
Ah ha!
See, that's the definitive statement I was unable to find in the manuals.
I thought that was the case though ...
Ok, my options are down to:
1) install the admin programs on the client so i can run bpplinclude
or
2) have the client's script initiate 1 job per entry in the file list (as opposed to initiating 1 job and passing the file list)
Would you like to reply?
Login or Register to post your comment.