Thanks for the confirmation.



From:
"Prather, Wanda" <wPrather AT ICFI DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
06/07/2010 11:10 AM
Subject:
Re: [ADSM-L] EMC Celerra CIFS backups
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



Got multiple customers doing that.

Domain all-local
Domain  \\hostname\mountpoint    \\hostname\mountpoint2  etc

Works just fine.
No need to map the drive to a drive letter.

Only gotcha, most people run the TSM scheduler from the default "system"
account, which has no network logon privileges, so it can't access those
UNC names.  You have to change the LOGON properties of the TSM scheduler
service to run under a Windows account with domain privileges (and
preferably an account whose password doesn't expire).

W


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Monday, June 07, 2010 10:53 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] EMC Celerra CIFS backups

Looking for recommended/suggested procedures to perform these kind of
backups.

>From what the IBM Windows client book says about "NetApps" CIFS backups
(assuming they apply to EMC as well), it is just a "mount the CIFS/NFS
drive and back it up".

However, digging through some previous discussion threads related to
this
topic, I never fully grasped the resolution to the issue of using a
"DOMAIN  \\mountpoint" statement and whether using a DOMAIN statement
precludes the need to perform a manual mount of the filesystem to a
drive-letter or that the DOMAIN statement automagically processed the
filesystem without the need for a "net.  One discussion seemed to imply
if
this did work, it was a "bug".

So, how do you backup CIFS?
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html