Backup Central

Recently came-across a situation - where a user/admin using Folder mounted
disk volumes (rather than Drive letter mapped volumes). For example, the
following folders have mounted disk-volume each about 30 GB:

D:\OT\LM1
D:\OT\LM2
D:\OT\LM3
D:\OT\OP1
D:\OT\OP2
D:\OT\OP3

Obviously, these weren't getting backed-up along with D:\ drive (only 4 GB
its own full-size is getting backed-up, but not the above mounted volumes).

A disk-volume mapped to a drive obviously getting backed-up, for example:
P:\ Q:\ R:\ and S:\ etc all are getting backed-up correctly.

One thing I can think of doing is - enumerating/listing each of these
folders in my SAVESET list to be backed-up, but haven't tried it yet.
Unfortunate side affect is - if user/admin created another/new D:\OT\OP4
mounted-volume, Networker is sure going to miss it, since its not listed
in Savesets lists to be backed-up.

Thought I've seen an elegant solution, can't search/recall. If you guys
have a better one please do share.

TiA
Sri






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

Another nicer solution could be you to write a small perl/powershell/batch
script that list these volumes and then, choose one of the 2 following
options :

1) you manually update using nsradmin the client resource's saveset list
(I am doing such with Solaris and ZFS for my global zones and
excluding fs I do not need a backup) and then you start the networker group
(and by consequence let networker grab backup level and retention
automatically from client's configuration)

or

2) once you have the list of the volume to save,
you start yourself the save cmds specifying pool, retention
to use.

HTH

Thierry

Kind regards - Bien cordialement - Vriendelijke groeten,

Thierry FAIDHERBE
Backup/Storage & System Management

LE FOREM
Département des Systèmes d'Information
Direction Infrastructure

Boulevard Tirou, 104 Tel: +32 (0)71/206730
B-6000 CHARLEROI Mobile: +32 (477)/995319
Fax: +32 (0)71/206199
BELGIUM Mail : Thierry.faidherbe<at>forem.be

-----Message d'origine-----
De : EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] De la
part de Sree
Envoyé : mardi 6 décembre 2011 16:57
À : NETWORKER < at > LISTSERV.TEMPLE.EDU
Objet : [Networker] Netwroker 7.6 Windows 2003 Folder mounted volumes (not
Drive letters) - backing all these volumes up

Recently came-across a situation - where a user/admin using Folder mounted
disk volumes (rather than Drive letter mapped volumes). For example, the
following folders have mounted disk-volume each about 30 GB:

D:\OT\LM1
D:\OT\LM2
D:\OT\LM3
D:\OT\OP1
D:\OT\OP2
D:\OT\OP3

Obviously, these weren't getting backed-up along with D:\ drive (only 4 GB
its own full-size is getting backed-up, but not the above mounted volumes).

A disk-volume mapped to a drive obviously getting backed-up, for example:
P:\ Q:\ R:\ and S:\ etc all are getting backed-up correctly.

One thing I can think of doing is - enumerating/listing each of these
folders in my SAVESET list to be backed-up, but haven't tried it yet.
Unfortunate side affect is - if user/admin created another/new D:\OT\OP4
mounted-volume, Networker is sure going to miss it, since its not listed
in Savesets lists to be backed-up.

Thought I've seen an elegant solution, can't search/recall. If you guys
have a better one please do share.

TiA
Sri






"signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


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

Final scoop on these:

In our quest to "exclude" VSS savesets, we initially worked
with "VSS:*=off" in Save Operations. OK - this reduced some VSS savesets,
but it still backed-up a few pesky un-needed savesets "ASR:\" "SYSTEM
STATE:\" and "SYSTEM DB:\"

Now, came a wonderful solution "All-ntfs" set in under "Save Set:"
selection. This setting was so elegant - until we recently found out that:
such Folder-mounted drives/LUNs were not getting backed-up. Those folder-
mounted drives must be excluded as part of "All-ntfs" savesets we
configured.

For that specific client (which has folder-mounted drives) we now
selected "All" in saveset selection box (of course "VSS:*=off" still being
set in Save operations:). Now we are getting backups for all these folder-
mounted savesets.

Thanks everybody - hope this helps

Thanks
Sree


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