April 26, 2013 at 8:28 am
Hi,
In my production environment there are only two drives C: and D: drives. The backups has to go the mapped drive named Z: The backups are failing now.
I went to backup maintenance plans history and found this message
Error msg: Could not find a part of the path 'z:\\xxx_TransactionLog_20130426091520.txt'.
can any one help me whats going on here.
April 26, 2013 at 8:33 am
Why the two back slashes here?! z:\\xxx_TransactionLog_20130426091520.txt
---------------------------------------------------------
It takes a minimal capacity for rational thought to see that the corporate 'free press' is a structurally irrational and biased, and extremely violent, system of elite propaganda.
David Edwards - Media lens[/url]
Society has varying and conflicting interests; what is called objectivity is the disguise of one of these interests - that of neutrality. But neutrality is a fiction in an unneutral world. There are victims, there are executioners, and there are bystanders... and the 'objectivity' of the bystander calls for inaction while other heads fall.
Howard Zinn
April 26, 2013 at 8:36 am
Use a UNC path, not a mapped drive. The mapped drive is only visible to the user that mapped it, not to the SQL Server service account, under whose context the backup is made.
John
April 26, 2013 at 8:40 am
does the\\ is the problem... that what it is showing in error msg. There should be one \ for fixed drives. It is a mapped drive so i am thinking there should be two slashes.
April 26, 2013 at 8:40 am
John Mitchell-245523 (4/26/2013)
Use a UNC path, not a mapped drive. The mapped drive is only visible to the user that mapped it, not to the SQL Server service account, under whose context the backup is made.John
I think mapped drive would still work if you logon to the server using the SQL Server service account and then mapping the network drive.
---------------------------------------------------------
It takes a minimal capacity for rational thought to see that the corporate 'free press' is a structurally irrational and biased, and extremely violent, system of elite propaganda.
David Edwards - Media lens[/url]
Society has varying and conflicting interests; what is called objectivity is the disguise of one of these interests - that of neutrality. But neutrality is a fiction in an unneutral world. There are victims, there are executioners, and there are bystanders... and the 'objectivity' of the bystander calls for inaction while other heads fall.
Howard Zinn
April 26, 2013 at 8:44 am
I'm not sure it would, to be honest. They'd be two different sessions. You'd need to test. But even if it did work, I'd strongly recommend against it. The service account is for running the service, and should not be used for interactive logons, whatever the reason.
John
April 26, 2013 at 10:20 am
UNC path would be preferable.
Where exactly is Z: mapped to? You may not really know unless you log on as the service account.
In an ideal world you should be backing up to the default backup location.
Then you do not need to specify the path, only the file name.
You can set the default backup location as a UNC path, make sure the service account has the correct
permissions and "Bob's your uncle"!
One not of caution, if you are using default backup location on a cluster, make sure you set the registry
key on all of the nodes!
April 29, 2013 at 7:20 am
I dont know about UNC path can any one help me where can i get the relevant information. how to use UNC path.
April 29, 2013 at 9:48 am
UNC path
Universal/Uniform Naming Convention. A UNC path describes the location of a volume, directory, or file.
The format for a UNC path is \\server\volume\directory\file and is not case-sensitive. For example:
\\Shared1_svr\Shared1\WGroups\Network\Orders.xlsRather than describe the location of a file or directory by drive letter, the Network Group will typically communicate a UNC path to describe the actual location of a file or directory. Windows drive letter mappings are arbitrary, whereas a UNC path is specific and applies to all operating systems.
Note: The UNC method started with the UNIX operating system. UNIX uses the forward-slash character as a path separator. Many network services (ex. FTP) have their origins in the UNIX operating system, so they use forward-slashes instead of the backslashes that DOS/Windows uses. It is important to recognize this distinction when using these services.
************************************
Every Dog has a Tail !!!!! :-D
April 29, 2013 at 9:51 am
UNC pathnames
UNC stands for Universal (or Uniform, or Unified) Naming Convention and is a syntax for accessing folders and files on a network of computers. The syntax is
\\<computer name>\<shared directory>followed by any number of directories and terminated with a directory or file name.
For example:
\\pondermatic\public\studyarea.gdb
\\omnipotent\shared_stuff\wednesday\tools
The computer name is always preceded by a double backward-slash (\\).
In UNC, the computer name is also known as the host name.
A few rules for UNC pathnames ar the followinge:
UNC paths cannot contain a drive letter (such as D:).
You cannot navigate to directories above the shared directory.
The Store relative pathnames option for documents and tools has no effect on UNC pathnames.
In ArcGIS, you can use a UNC pathname anywhere a pathname is requested. This is particularly advantageous for shared data on a local area network (LAN). Data can be stored on one computer and everyone with access to the computer can use the data as long as the computer is not turned off or removed from the network.
In Windows, you can share a folder so that other users on your local area network can access it. In ArcCatalog or Windows Explorer, right-click a folder, click Sharing and Security, then follow the instructions on the dialog box that opens.
************************************
Every Dog has a Tail !!!!! :-D
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply