Path names exceeding 256 characters

[Harry_Dunn]

We currently run CPS backing up a server to a NAS box and by doing so it creates a folder containing the server's name and a folder for each partition underneath.

The servers name is always 15 characters long + 1 for the partition name adding 16 characters on top of the current path which means some file paths exceed 256 characters and CPS is unable to see down that far to backup the data.

Has anyone else come across this problem? Is there a work around or fix or is it just a flaw in CPS as it is with another program we use called bullet proof folders?

[Harry_Dunn]

bump

[Harry_Dunn]

backing up the data using v10d to tape works fine. I have created a file where the path name is over 400 characters and this was backed up/restored without a problem.
I have also setup shares further down the path meaning it is below the 256 characters and CPS is able to pickup the data fine using this method.Message was edited by:
Harry Dunn

[Shilpa_pawar_2]

Hi,

What is the OS on NAS? Are you backing up unix data?

Are you also getting any errors on this directories?

Ensure that NTFS file and directory names are not longer than 255 characters.
.
Refer to the following link for more information.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/fs/naming_a_file.asp

NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.

[Harry_Dunn]

Thank you for your speedy reply...

OS = Windows 2003 Server with service pack 1 and Microsoft storage server.

No UNIX data

Ensure that NTFS file and directory names are not longer than 255 characters.
When you have 4.5k users spread across 30 sites it's impossible to manage the file structures they create and seeing they can use 256 characters on the windows servers they will. The problem happens when the data is moved to the NAS box as extra characters are added to the path \\\\ adding 16 characters to the path.

This is no longer an issue as it was found to be a limitation of the OS on the NAS box. The data was on the NAS box but wasn't reporting as being so.

[Harry_Dunn]

Double post :\

[Deepali_Badave]

Hello,

Thank you for an update.