commvault.com commvault.com
Solved

Guest Files and Folders Restore does not restore everything

  • 18 August 2021
  • 6 replies
  • 332 views
F
Rank
Userlevel 2
Badge +6

Hi,

 

Today I tried to to restore a Folder directly to a VM but only 5 of 6 Items were restored (if I restored the same folder directly to the MA all was fine). For this I used the Command Center.

I think this one file which was not restored has a problem if Commvault copies it over the network.

Here is a snippet of the log:

 

8164  d1c   08/18 09:16:09 29346 CVSAgentlessRestoreToVM::CopyToGuest() - Creating guest dir [D:\tmp\Scripte\]
8164  d1c   08/18 09:16:09 29346 CVWinGuestAPI::CopyFileToGuest() - MoveFileExW failed[2]! \\?\C:\Program Files\Commvault\ContentStore\iDataAgent\JobResults\CV_JobResults\2\0\29346\ForGuestVM\Scripte\geöffnete Dateien anzeigen.cmd -> \\?\UNC\192.168.50.238\D$\tmp\Scripte\geöffnete Dateien anzeigen.cmd
8164  d1c   08/18 09:16:09 29346 CVSAgentlessRestoreToVM::CopyToGuest() - Failed to copy [C:\Program Files\Commvault\ContentStore\iDataAgent\JobResults\CV_JobResults\2\0\29346\ForGuestVM\Scripte\geöffnete Dateien anzeigen.cmd] to [D:\tmp\Scripte\geöffnete Dateien anzeigen.cmd]
8164  d1c   08/18 09:16:09 29346 CVSAgentlessRestoreToVM::CopyToGuest() - Successfully copied file to guest VM srcPath[C:\Program Files\Commvault\ContentStore\iDataAgent\JobResults\CV_JobResults\2\0\29346\ForGuestVM\Scripte\SoftwareDestribution.cmd] VMdestPath [D:\tmp\Scripte\SoftwareDestribution.cmd]
8164  d1c   08/18 09:16:09 29346 CVSAgentlessRestoreToVM::UpdateFileTimes() - Successfully changed file attributes [D:\tmp\Scripte\SoftwareDestribution.cmd]
8164  d1c   08/18 09:16:09 29346 CVSAgentlessRestoreToVM::CopyToGuest() - Successfully copied file to guest VM srcPath[C:\Program Files\Commvault\ContentStore\iDataAgent\JobResults\CV_JobResults\2\0\29346\ForGuestVM\Scripte\TeamViewer_START.bat] VMdestPath [D:\tmp\Scripte\TeamViewer_START.bat]
8164  d1c   08/18 09:16:09 29346 CVSAgentlessRestoreToVM::UpdateFileTimes() - Successfully changed file attributes [D:\tmp\Scripte\TeamViewer_START.bat]
8164  d1c   08/18 09:16:10 29346 CVSAgentlessRestoreToVM::CopyToGuest() - Successfully copied file to guest VM srcPath[C:\Program Files\Commvault\ContentStore\iDataAgent\JobResults\CV_JobResults\2\0\29346\ForGuestVM\Scripte\TeamViewer_STOP.bat] VMdestPath [D:\tmp\Scripte\TeamViewer_STOP.bat]
8164  d1c   08/18 09:16:10 29346 CVSAgentlessRestoreToVM::UpdateFileTimes() - Successfully changed file attributes [D:\tmp\Scripte\TeamViewer_STOP.bat]
8164  d1c   08/18 09:16:10 29346 CVSAgentlessRestoreToVM::CopyToGuest() - Successfully copied file to guest VM srcPath[C:\Program Files\Commvault\ContentStore\iDataAgent\JobResults\CV_JobResults\2\0\29346\ForGuestVM\Scripte\WSUS.cmd] VMdestPath [D:\tmp\Scripte\WSUS.cmd]
8164  d1c   08/18 09:16:10 29346 CVSAgentlessRestoreToVM::UpdateFileTimes() - Successfully changed file attributes [D:\tmp\Scripte\WSUS.cmd]

 

 

Does anyone has the same Issue if special characters or spaces are in the filename?

 

Kind Regards

Florian

icon

Best answer by Dan White 18 August 2021, 16:31

View original

6 replies

Mike Struening RETIRED
Rank
Userlevel 7
Badge +23

Hey @flokaiser , thanks for the question!

I’m not aware of any direct issues, though we all know special characters have been known to cause issues.  I’ll ask internally for some feedback.

In the meantime, do you see any failure reason in the job details or job summary report (with details)?  curious if we can find out WHY it failed.

8164  d1c   08/18 09:16:09 29346 CVSAgentlessRestoreToVM::CopyToGuest() - Failed to copy [C:\Program Files\Commvault\ContentStore\iDataAgent\JobResults\CV_JobResults\2\0\29346\ForGuestVM\Scripte\geöffnete Dateien anzeigen.cmd] to [D:\tmp\Scripte\geöffnete Dateien anzeigen.cmd]

https://www.linkedin.com/in/michael-struening
F
Rank
Userlevel 2
Badge +6

No, there are no special errors in the job.

D
Rank
Userlevel 4
Badge +8

Hello @flokaiser 

 

For Agentless Restores we use the “Copy-VMGuestFile” CMDlet through VMware. However, I don’t see any character limitations on the VMware documentation for the CMDlet but judging by the log cuts it seems clear there might be.

 

Have you attempted other files with the “ö” character? Are you able to create another file with this character and try again?

 

When you restore to a Media Agent or any server with the Restore Only agent installed, you take the “Copy-VMGuestFile” CMDlet out of the equation which is why it is working.

 

 

"If you give a man a fish, you feed him for a day. If you teach a man to fish, they will probably burn your spot"
F
Rank
Userlevel 2
Badge +6

Tried a few different Files with ‘ö’, ‘ä’ and ‘ü’ in the Filename or as Foldernames and everytime the job failed. I will use the filesystem agent for this cases now because this works without any problems.

Damian Andre
Rank
Userlevel 7
Badge +23

Tried a few different Files with ‘ö’, ‘ä’ and ‘ü’ in the Filename or as Foldernames and everytime the job failed. I will use the filesystem agent for this cases now because this works without any problems.

FS agent will give you much faster and efficient restores in either case (with the trade off of convenience of not deploying a FS agent), but I will escalate this on our side, we should not see this type of failure with either method!

Damian Andre
Rank
Userlevel 7
Badge +23

hey @flokaiser,

Engineering tested the special characters (its part of our automation testing, but they did it anyway) - they were unable to reproduce the issue, so it could be related to a specific feature release of maintenance release, system OS, file system or some other environmental anomaly. If you want to pursue this further for a fix or to identify the root cause, we’d need a support case and some logs to dig into it deeper.

 

I know that is a pain since you have a valid workaround, but more than happy to get this escalated to determine the root cause and fix if you would like to pursue it.

Reply


Terms & ConditionsCookie settings