11-10-2016 05:05 AM
Master Server 7.7.2 - Windows 2008 R2
Media Server 7.7.2 - Windows 2012 R2
Client 7.7.2 - Windows 2012
We have a file server that has millions of files and I am looking to divide the volumes into 4-5 streams but I can't figure out an easy backup selection like the following:
NEW STREAM
H:\a-g
New Stream
H:\h-l
I know that this is something that is possible for Unix but not for windows. Has anyone else run into something like this?
Solved! Go to Solution.
11-11-2016 12:04 AM
The method suggested by @watsons has been working for us at various customer sites.
And both uppercase and lowercase gets backed up.
NEW_STREAM
X:\Users\a*
X:\Users\b*
X:\Users\c*
X:\Users\d*
.....
...
NEW_STREAM
X:\Users\g*
X:\Users\h*
X:\Users\i*
X:\Users\j*
.....
....
NEW_STREAM
X:\Users\m*
X:\Users\n*
X:\Users\o*
X:\Users\p*
.....
NEW_STREAM
X:\Users\.....
.....
11-14-2016 08:36 AM
Windows is not case sensitive.
You can prevent data loss:
creating a policy with file list ALL_LOCAL_DRIVE
creating a policy with file list e:\data*
Then on the client, create a policy specific exclude list, that exclude e:\data* (for the ALL_LOCAL_DRIVE directive). Then if someone create e:\somedir, that directory will be protected by the ALL_LOCAL_DRIVE directive.
11-10-2016 06:58 AM - edited 11-10-2016 07:00 AM
one way of doing it, is placing data into seperate top level folder like
e:\data1
e:\data2
e:\data3
Then from the policy specify as file path e:\data* and chekmark "use multiple streams".
As you mention, advanced regular expression does not work under Windows.
11-10-2016 07:01 AM
I thought about doing that but lets say someone adds a new folder and I never catch it? I also want to avoid case sensitive issues
11-10-2016 07:14 AM
Hello,
supposing thar dividing your H: disk into several disks backed up then as separate streams is not probably feasible, you can try other approaches:
if you have a basic disk or tape on Media Server, consider FlashBackup policy for the whole disk.
If you have dedup disk on Media Server, consider Use Accelerator attribute in your MS-Windows policy
if you have a change to virtualize this server, or if it is already a virtual server, consider VMware/Hyper-V policy.
Details in appropriate Admin Guides.
Regards
Michal
11-10-2016 07:19 AM
The client is a Hyper-V VM but the data is sitting on NTFS deduplication volume and from what I am reading flash type backups are not supported on these volume types. So I am going to assume hyper-v snapshot backups are not supported either...
Also the Accelerator is enabled but it still runs for 24 plus hours to do a full backup.
11-10-2016 07:35 PM
Would this work for you?
NEW STREAM
H:\a*
H:\b*
H:\c*
H:\d*
H:\e*
H:\f*
H:\g*
NEW STREAM
H:\h*
H:\i*
H:\j*
...
(so on and so forth.., and don't forget to have H:\0* up to H:\9*)
Don't have to worry about case sensitivity I guess, if the client is Windows.
11-11-2016 12:04 AM
The method suggested by @watsons has been working for us at various customer sites.
And both uppercase and lowercase gets backed up.
NEW_STREAM
X:\Users\a*
X:\Users\b*
X:\Users\c*
X:\Users\d*
.....
...
NEW_STREAM
X:\Users\g*
X:\Users\h*
X:\Users\i*
X:\Users\j*
.....
....
NEW_STREAM
X:\Users\m*
X:\Users\n*
X:\Users\o*
X:\Users\p*
.....
NEW_STREAM
X:\Users\.....
.....
11-11-2016 04:03 PM - edited 11-11-2016 04:05 PM
In a Windows backup policy this should work:
H:\[a-g]*
H:\[h-l]*
etc...
11-14-2016 08:36 AM
Windows is not case sensitive.
You can prevent data loss:
creating a policy with file list ALL_LOCAL_DRIVE
creating a policy with file list e:\data*
Then on the client, create a policy specific exclude list, that exclude e:\data* (for the ALL_LOCAL_DRIVE directive). Then if someone create e:\somedir, that directory will be protected by the ALL_LOCAL_DRIVE directive.