This looks weird to me - there is no Windows running on the NAS - therefore no VSS can kick in of course.
It seems as if you would backup a NAS filesystem using the standard NW filesystem walker. The only reason why this would happen is that anyone has misconfigured your NW client as a standard filesystem but not as a NDMP client. Please verify you rap.log file for potential changes since the last good backup.
Thanks for the information. As per your Advise have checked the Rap Log file. On the date when the NAS backup happened properly From that date Couldn't able to find any changes are made to the NSR Group /Client for the NAS path.
Could you please help me , what are the parameters needs to be filles to create an New cleint [ NAS File shareBackup ] especially the Backup command/NDMP option and Save operations Application informations.
I am not sure as I do not know your environment. Also be a bit careful - if NW talks about NAS it is meant that an NMDP backup should be performed. Up to now I do not really know whether this is true. What type of filer do you want to backup?
The best to verify that is to share your client's settings - especially
Sample save set :- \\GDC-SLO-P-FSR01\MHFileShare02\Bologna
Backup command :- save -xL
Application information is -nothing
One more thing i would like highlight here is when the NAS Filer group ran ,it never failed instead says Gruop completed successfully . But if we checked the completed NAS drive details. it shows the below error, please advise ASAP.
.
7285:save: Volumes selected do not support the use of VSS. NetWorker software will save the files using the legacy backup method. No snapshot will be taken. gdc-slo-p-bkp01.marineharvest.net: \\GDC-SLO-P-FSR01\MHFileShare02\Harsum level=full, 90 KB 00:02:19 158 files completed savetime=1437663384 File \\GDC-SLO-P-FSR01\MHFILESHARE02\Harsum\Shared\New folder\Driver\Setup.exe could not be opened and was not backed up. (Invalid argument) File \\GDC-SLO-P-FSR01\MHFILESHARE02\Harsum\Shared\New folder\Driver\Setup.ini could not be opened and was not backed up. (Invalid argument) File \\GDC-SLO-P-FSR01\MHFILESHARE02\Harsum\Shared\New folder\Driver\Setup64.exe could not be opened and was not backed up. (Invalid argument) File \\GDC-SLO-P-FSR01\MHFILESHARE02\Harsum\Shared\New folder\Driver\Bmp\HEAD.bmp could not be opened and was not backed up. (Invalid argument)
Today ran the same saveset only with small addition was done in the "Save operations" on Client config as "VSS.*=off" But still no LUCK.
This is not a NDMP backup, you are trying to backup a NAS CIFS share from a Windows machine, and since you are using windows+NetWorker you cannot get away from using VSS issues. This is not a good practice for backing up NAS data, NAS data should always be backed up using NDMP.
The error here indicates that NetWorker identifies that the mount point does not support use of VSS and thus it is using legacy backup method. But there are certain files on the share that the NetWorker is not able to access and thus it is failing.
Again do not use this kind of a method to backups NAS data, configure the backups using NDMP. Refer documentation for more information on how to use NDMP. Just out of curiosity,, which NAS filer do you use ?
I looked through my 'files' and saw an issue I discovered myself about 6 months ago when backing up a CIFS share from another Windows (2012R2) host. I am pretty sure my NW version was either 8.1.1.9 or 8.2.1.2 at that time.
The reason I found was that obviously the VSS option was not properly 'translated' from the resource into the command.
How did I find out - I just started the group from the command line. Here I could see that the option "-o vss:*=off" appeared weird like .... -o "\"\vss:*=off\";\"" ...
Please use the command line to verify if a similar issue exists.
Of course manual backups will work.
I opened SR #66837032 to inform EMC but I don't know whether they have fixed it already. For us it is not so important as we do not use these type of backups.
bingo.1
2.4K Posts
1
July 23rd, 2015 15:00
This looks weird to me - there is no Windows running on the NAS - therefore no VSS can kick in of course.
It seems as if you would backup a NAS filesystem using the standard NW filesystem walker. The only reason why this would happen is that anyone has misconfigured your NW client as a standard filesystem but not as a NDMP client. Please verify you rap.log file for potential changes since the last good backup.
venkatesh_bs2
3 Posts
0
July 24th, 2015 04:00
Hello Bingo,
Thanks for the information. As per your Advise have checked the Rap Log file. On the date when the NAS backup happened properly From that date Couldn't able to find any changes are made to the NSR Group /Client for the NAS path.
Could you please help me , what are the parameters needs to be filles to create an New cleint [ NAS File shareBackup ] especially the Backup command/NDMP option and Save operations Application informations.
Thanks,
Venkatesh
bingo.1
2.4K Posts
0
July 24th, 2015 06:00
I am not sure as I do not know your environment. Also be a bit careful - if NW talks about NAS it is meant that an NMDP backup should be performed. Up to now I do not really know whether this is true. What type of filer do you want to backup?
The best to verify that is to share your client's settings - especially
the save set list
the backup command and
the application information
venkatesh_bs2
3 Posts
0
July 24th, 2015 07:00
Bingo,
Sample save set :- \\GDC-SLO-P-FSR01\MHFileShare02\Bologna
Backup command :- save -xL
Application information is -nothing
One more thing i would like highlight here is when the NAS Filer group ran ,it never failed instead says Gruop completed successfully . But if we checked the completed NAS drive details. it shows the below error, please advise ASAP.
Today ran the same saveset only with small addition was done in the "Save operations" on Client config as "VSS.*=off" But still no LUCK.
crazyrov
4 Operator
•
1.3K Posts
0
July 24th, 2015 21:00
Venkatesh,
This is not a NDMP backup, you are trying to backup a NAS CIFS share from a Windows machine, and since you are using windows+NetWorker you cannot get away from using VSS issues. This is not a good practice for backing up NAS data, NAS data should always be backed up using NDMP.
The error here indicates that NetWorker identifies that the mount point does not support use of VSS and thus it is using legacy backup method. But there are certain files on the share that the NetWorker is not able to access and thus it is failing.
Again do not use this kind of a method to backups NAS data, configure the backups using NDMP. Refer documentation for more information on how to use NDMP. Just out of curiosity,, which NAS filer do you use ?
bingo.1
2.4K Posts
0
July 24th, 2015 23:00
I looked through my 'files' and saw an issue I discovered myself about 6 months ago when backing up a CIFS share from another Windows (2012R2) host. I am pretty sure my NW version was either 8.1.1.9 or 8.2.1.2 at that time.
The reason I found was that obviously the VSS option was not properly 'translated' from the resource into the command.
How did I find out - I just started the group from the command line. Here I could see that the option "-o vss:*=off" appeared weird like .... -o "\"\vss:*=off\";\"" ...
Please use the command line to verify if a similar issue exists.
Of course manual backups will work.
I opened SR #66837032 to inform EMC but I don't know whether they have fixed it already. For us it is not so important as we do not use these type of backups.